1.2.0
Compatibility
Changes
Reveal 1.2.0
New Features
-
Added a collapsible Reveal Codex button to the bottom of the inventory screen.
- Click to open the codex.
- Shift-click to open the Reveal screen directly.
-
Added Journal, Share, and Reveal shortcuts to the codex.
-
Added a Research Journal that records reveals, shared pages, and pages received from other players.
-
Added progress sharing.
- Export your discovered entries as a Codex Page.
- Other players can use the page to unlock entries they have not discovered yet.
- The page is consumed after use.
-
Added new unlock conditions:
- Defeat a specified entity.
- Enter a specified biome.
- Complete a specified advancement.
-
Unlock conditions can now target either an entire chapter or an individual entry.
-
Material-based unlocks can now optionally keep or consume the required items.
-
Unlock hints can be shown on chapters, individual entries, or hidden entirely.
-
Added item, entity, biome, and advancement selectors to the visual editor.
-
Added a default Miscellaneous chapter with three new entries.
Improvements
- JEI now indicates whether unlock materials are consumed.
- Improved Tag-based ingredient names and unlock-condition tooltips.
- Individual entry requirements are now displayed on the corresponding entry.
- Reduced overlapping tooltips and raw technical IDs appearing in the UI.
- New-entry indicators now use a star icon and disappear after returning to the chapter list.
- Renamed Recipes to Unlock Methods throughout the editor.
Removed / Changed
- Removed the editor's Fill from Held Item action.
- Removed the restriction that unlocks could only target entire chapters.
- Removed the requirement for reveal materials to always be consumed.
- Unlocking is no longer limited to material-based recipes.
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:63VFuO84"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ClXXk7qd:63VFuO84"
}

