Tags
Creators
Details
1211.13.0
Compatibility
Changes
RarityCore Ver.13
New: Rarity Visual Customization
You can now customize colors, textures, and visual toggles individually for each rarity tier!
The configuration file is located at config/raritycore/RarityClientConfig.json. It supports separate settings for tiers 1–7:
- Color — RGB format (e.g.,
#FFCC00), used for tooltips, item names, and the programmed border. - Texture — Custom border texture path.
- Individual Toggles — Each tier has independent controls for tooltips, border rendering, and name coloring.
The master switch in
client.jsonstill takes precedence — if it's off, per-tier settings will not apply.
New: Tag-Based Mass Rarity Assignment
Don't want to assign rarity item by item? The new config/raritycore/TagRarity.json lets you use Minecraft's tag system to assign rarity in bulk.
New: In-Game NBT Tag Rarity Control
With enableNbtRarityControl enabled in server.json, items can control their own rarity appearance directly via NBT tags.
This tag has the highest priority, overriding all other rarity configurations. Perfect for custom content or cross-mod integration.
New: Iron's Spellbooks Integration
Spell scrolls now automatically gain rarity based on the level of the spell stored within them. The higher the spell level, the higher the rarity!
Refactor: Full Overhaul of Edit Mode
Edit Mode is no longer just a simple "click an item to change its rarity". Ver.13 introduces two new modes:
Normal Mode (default) — Works as before: click an item to write to FinalRarity.json. rarity=0 means "no rarity".
FullMatch Mode — Click an item to automatically generate an NBT-matching configuration! It uses all current NBT tags of the item as matching conditions, making it possible to distinguish items with the same name but different data (e.g., different potion types, different enchantments).
Numerous new commands have been added, and there's even a GUI panel!
Improvement: Enhanced Export Command
Added /raritycore export rarity <tier> to export all items of a specific rarity tier.
New: KubeJS Support
Do you have KubeJS installed? You can now control rarity using JavaScript: Check the wiki for detailed usage!
Optimizations
Many areas have been optimized — overall, it's smoother than before!
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:mHYT3CaB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EtlqmUU6:mHYT3CaB"
}

