All versions
1.2
Release
TD-Rarity 1.2 -26.32 weeks ago 33
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Changes
MOD UPDATE ยป 1.2
๐ข NEW FEATURES
- [ALL] Added Panel Background in Settings: None, Blurred, Dimmed, and Blurred + Dimmed.
- [ALL] Profiles now save and restore settings, rarity definitions, and item rules together.
๐ก CHANGES
- [ALL] Older configuration formats are no longer supported.
- [ALL] Saving a profile leaves your current settings unchanged. Restore the profile to apply it.
- [ALL] The CLOSE and RESET buttons now have matching sizes in every language.
- [ALL] The restart-required notification now stays visible for 10 seconds instead of 30.
๐ PERFORMANCE
- [ALL] Settings, profiles, and item edits now save in the background, keeping the configuration menu responsive.
- [ALL] Reduced unnecessary disk writes when moving settings sliders.
- [ALL] Reduced repeated file reads while displaying profiles and item lists.
๐ด BUG FIXES
- [ALL] Fixed cases where an earlier save or profile restore could overwrite newer edits.
- [ALL] Pending saves continue after closing the configuration menu. Normal game shutdown also gives them time to finish.
- [ALL] Improved protection against data loss when saving a configuration or profile fails.
- [ALL] Invalid configuration files are rejected without changing their contents. Profile operations also protect unrelated user files from accidental overwriting or deletion.
- [1.21.11] Fixed closing the configuration menu so it returns to the previous screen.
- [1.21.11] Added safeguards for rarity rendering when no world or player is available.
- [1.21.11, 26.1, 26.2, 26.3] Fixed rarity fire effects sometimes appearing clipped or blending incorrectly around dropped items.
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:EptCpPgp:jQLYjisL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EptCpPgp:jQLYjisL"
}

