Tags
Creators
Details
1211.14.0
Compatibility
Changes
RarityCore V14 Update
Configuration Consolidation
All configuration related to rarity visuals is now consolidated into a single file, RarityStyle.json. Settings previously scattered across client.json and RarityClientConfig.json have been merged into it. More importantly, we've added even more granular configuration options!
The most notable change is the update to tooltips: rarity tier numbers, stars, and similar elements are now packed as placeholders, and all string content supports language keys. You have full freedom to rearrange their order and modify the content easily. For example, you can now swap the positions of stars and the rarity name! Or add some emoji decorations to tooltips based on the tier? Go wild!
Unlimited, Minimal Definition
The upper limit on rarity tiers has been completely removed. You can now configure styles for any tier equally, and we no longer define fixed names for tiers 1–7.
Think of it this way: RarityCore v14 has shifted
from "I built a rarity system with 7 tiers, and rarities inside and outside this range need different handling and configuration"
to "I preset 7 rarities for the system, but all tiers are handled and configured the same way — change them however you like."
API Upgrades
This version includes a lot of developer-facing updates, offering a more advanced API, but migration is usually not required.
- Translation key changes: Rarity translation keys in language files have been changed from names like
rarity.core.commonto numeric keysrarity.core.1throughrarity.core.7. If you use a custom resource pack, please update accordingly. - Named constants removed:
RARITY_COMMONthroughRARITY_UNIQUEhave been removed in favor of numeric tiers;MIN_RARITYandMAX_RARITYare retained. - Query enhancements: Support for retrieving tooltip content, translation keys, star configurations, border styles, etc., on a per‑tier basis.
- Event system: Three types of events — config reload, style change, and registry change.
- Query items by rarity: Support for scanning registries by tier to get a list of items.
- Rarity style modification: Now supports easier ways to modify and lock rarity styles.
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:EtlqmUU6:gr5vJF1a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EtlqmUU6:gr5vJF1a"
}

