Tags
Creators
Details
1.0.13
Compatibility
Changes
Changelog Added Added a Tidal Reveal Animation: when observing gray cards, the game now enters a fixed, centered reveal screen before flipping the results one by one. Added a toggle for the reveal animation, plus Space key support to skip the animation. Added Batch Observation, allowing players to select the current level and observe all remaining unobserved gray cards at once. Added /trs reload for hot-reloading configs and /trs doctor for configuration diagnostics. Added server-side config synchronization and support for the visible_level_slots level display setting. Changed Reworked the main Observation Card screen layout for consistent scaling across different resolutions, GUI scales, and window sizes. Adjusted the bottom structure of the main panel to reserve stable space for the Batch Observation action bar, while keeping card sizes from growing further. Adjusted Batch Observation rules: level-specific observation vouchers are consumed first, then the remaining cost is paid with regular observation currency. Improved the reveal flow: during Batch Observation, cards are revealed and flipped one by one in card order. Config files continue to support JSON5, while retaining compatibility with legacy JSON config files. Fixed Fixed an issue where client-side and server-side configs could become inconsistent, causing the UI rules to desync. Fixed an issue where /trs reload could partially overwrite in-memory configs when reloading failed. Configs are now validated first and applied only after passing validation. Fixed an issue where voucher colors updated after reload, but card level block colors did not update accordingly. Fixed invalid item IDs and malformed reward entries only being reported at runtime. These are now caught during config validation. Fixed cases where the initial Tidal Observation Card could be granted repeatedly. Fixed extra success messages being sent after Batch Observation completed.
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:B8SR6bz9:WKZELDH1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B8SR6bz9:WKZELDH1"
}

