

Modrinth · Fabric · Client mod
Variants-CIT
Variants-CIT is a client-side mod. Install it on your computer; the server does not need it.
Alternative CIT format for large collections of variants with repeating patterns.
- Downloads
- 1.9M
- Author
- Estecka
- Loader
- Fabric
- Minecraft
- 1.21 – 26.3
- Updated
- –
Screenshots
What Variants-CIT looks like
Images: Variants-CIT on Modrinth, published by the project team.
Setup
Install Variants-CIT on your client
Client-side mods only run on your computer. More server RAM does not change their performance.
- 01
Install the loader locally
Install Fabric for your Minecraft version in your launcher.
- 02
Download the file
Download the Variants-CIT file for your loader and your exact Minecraft version, for example 26.3-pre-2.
- 03
Add it to the mods folder
Put the .jar file in your local .minecraft/mods folder and remove older duplicates.
- 04
Launch
Launch Minecraft with the loader profile. Nothing needs to change on the server.
- On the server
- Not needed
- On the client
- Required
- Loader
- Fabric
- Minecraft
- 26.3-pre-2, 26.3, 26.2 +19 more
- License
- European Union Public License 1.2
Releases
Published releases
Pick the file that matches your server’s loader and Minecraft version. The server and players need the same release.
Variants-CIT · ModrinthOriginal description by the project author
Variants-CIT
An alternative CIT format designed to handle large amounts of variants.
This mod excels in scenarios where one item has many variants all based on the same pieces of data. It yields better performances when extreme amounts of CITs are available, and uses a resource format that is less redundant, requiring only one short file to configure all possible variants of an item at once.
Assigning models on a case-by-case basis (similar to how Optifine-CIT handles it) is still possible, but does not boast the same performances.
Resource Pack Format
This is a quick showcase. Refer to The Wiki for a complete guide.
The format revolves around item variants being automatically associated to models or textures with matching names.
Instead of defining separate conditions for every variants, you define a single rule that governs all variants in a collection, (so-called modules). This module defines what item is affected, how to figure out its variants, and where the variant models are located.
Fully automatic variants-to-model association
Here's a simple module that would change the texture of enchanted books :
{
"items": "enchanted_book", // The affected item type(s)
"modelPrefix": "book_cit/", // The folder containing the possible models/textures.
"assetGen": "item_model/generated", // Auto-generate models from textures (if missing)
"type": "stored_entchantment", // How to compute the item's "variant ID"
"parameters": { // Extra options specific to the module's type
"levelSeparator": "_lvl_" // Include enchantment level in the variant ID
}
}
Here, a book with the enchantment minecraft:unbreaking at level 2 will have the variant ID minecraft:unbreaking_lvl_2, and thus use the texture stored at /assets/minecraft/textures/item/book_cit/unbreaking_lvl_2.png.
This single module will work for every possible enchantment, vanilla or modded, so long as a corresponding texture exists.
Automatic variants based on custom data
The module above has a purpose-made type for enchanted books. If no type exists for a specific use-case, you can still use more generic modules to get a variant from any component:
{
"items": "minecraft:suspicious_stew",
"modelPrefix": "item/suspicious_stew_cit/",
"assetGen": "item_model/generated",
"type": "component_data",
"parameters": {
"componentType": "suspicious_stew_effects", // The component containing the variant ID
"nbtPath": "[0].id" // The location of the variant ID in the component.
}
}
Processing data that can't be used as-is:
{
"items": "diamond_sword",
"modelPrefix": "item/named_swords/",
"assetGen": "item_model/handheld",
"type": "component_data",
"parameters":
{
"componentType": "custom_name",
"transform": [
{
"function": "regex",
// Pattern matching,..
"regex": "(?i)(.*'s )?(Great |Grand )?(?<var>.*(sword|dagger))( of doom)?",
// ... and preserve only a portion of the name.
"substitution": "$var"
// (E.g: "steev18's great Steel Sword" => "Steel Sword")
}
{
// Turns any text into a valid identifier
"function": "sanitize"
// (E.g: "Steel Sword" => "minecraft:steel_sword")
}
]
}
}
Combining multiple pieces of data from different sources:
{
"items": "minecraft:diamond_sword",
"modelPrefix": "item/trimmed_diamond_sword/",
"assetGen": "item_model/handheld",
"type": "component_format",
"parameters":
{
// How to combine various pieces of data into a variant ID
// (E.g: sentry_diamond)
"format": "${pattern}_${material}",
// Where to find those pieces of data.
"variables": {
"pattern": {
"componentType": "trim",
"nbtPath": ".pattern"
},
"material": {
"componentType": "trim",
"nbtPath": ".material",
"transform": "discard_namespace"
}
}
}
}
Case-by-case variants
For systems that don't really follow any rules, (or if you have too few variants to care about automatism), you can use a format closer to Optifine-CIT's paradigms:
{
"items": "trident",
"modelPrefix": "item/godly_tridents/",
"assetGen": "item_model/trident",
"type": "predicates",
"parameters": {
"predicates":
[
{
"variantId": "zeus_smite",
"precondition": {
"enchantments.channeling": { "greater_or_equals": 1 }
}
},
{
"variantId": "jupiter_syphon",
"precondition": {
"enchantments.riptide": { "greater_or_equals": 1 }
}
}
// etc
]
}
}
Does Variants-CIT need to be installed on the Minecraft server?
No. Modrinth marks Variants-CIT as unsupported on the server side. Install it only in your local mods folder. Your server can stay unchanged unless the project page lists an additional dependency.
Which version and loader does Variants-CIT require?
Use a file for Fabric and your exact Minecraft version. Supported versions include 26.3-pre-2, 26.3, 26.2. Files for different loaders are not interchangeable.
Variants-CIT is not working – what should I check?
First check the Minecraft version, loader version and required dependencies. Because the mod is client-side, more server RAM will not fix it.
Similar mods
Popular mods in the same category
Fabric API
by modmuss50
Lightweight and modular API providing common hooks and intercompatibility measures utilized by mods using the Fabric toolchain.
Server-ready
Cloth Config API
by shedaniel
Configuration Library for Minecraft Mods
Server-ready
YetAnotherConfigLib (YACL)
by isxander
A builder-based configuration library for Minecraft!
Server-ready
Fabric Language Kotlin
by modmuss50
This is a mod that enables usage of the Kotlin programming language for Fabric mods.
Looking for mods for your own server?
The catalog lists mods that run on Minecraft servers.
