1.3.0
Compatibility
Changes
Version 1.3.0 Changelog
This update introduces the Research Station and automatic inventory-based unlocking, alongside improvements to the revelation interface, journal navigation, and editor usability. Several UI and interaction issues have also been fixed.
New Features
- Added support for NeoForge 1.21.1 and Forge 1.20.1.
- Added the Research Station, which opens the revelation interface when right-clicked. Portable revelation can now be disabled through the configuration.
- Added automatic inventory-based unlocking, supporting individual items, item tags, and unlocking individual entries or entire chapters.
- Added unlock notifications in the top-right corner.
- Added search, chapter filtering, and unlock-status filtering to the journal. Right-clicking the search field now clears its contents.
Improvements
- Redesigned the revelation interface with a magnifying glass graphic and dedicated interaction buttons.
- Standardized editor button styles and improved search performance in the item, entity, and biome selectors.
- Compasses, clocks, and name tags in the default Miscellaneous category are now unlocked automatically when obtained.
Bug Fixes
- Fixed incorrect highlighting of chapter titles.
- Fixed mismatches between selector visuals and clickable areas.
- Fixed edited content being lost after resizing the window.
- Fixed layout issues at smaller window sizes.
- Fixed unintended list selections caused by right-clicking.
- Fixed accidental page switching when scrolling horizontally.
- Fixed search filters resetting after returning to the journal directory.
- Fixed page navigation ignoring active filters.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ClXXk7qd:eygLYgcm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ClXXk7qd:eygLYgcm"
}

