Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 2 months ago
All versions
1.2.2-fork.5+26.1
Beta
v1.2.2-fork.5+26.14 months ago 320
Compatibility
Minecraft: Java Edition
26.1
Platform
Fabric
Supported environments
Client-side
Changes
1.2.2-fork.5+26.1
Fixed
- Ported CIT Resewn Continuation to Minecraft 26.1/Fabric.
- Restored Barely Default elytra CIT loading on 26.1.
- Fixed worn/damaged elytra variant priority so low-durability textures resolve correctly.
- Restored item model material-prefix fallback for names such as
Diamond ClaymoreandGolden Cutlass. - Kept the defaults module bundled inside the main jar; install only the main jar.
1.2.2-fork.5+1.21.11
Fixed
- Restored legacy
nbt.Damage=...condition support for Minecraft 1.21.11. - Added support for item subtexture overrides such as
texture.layer1=.... - Added ISO-8859-1/Latin-1 fallback parsing for
.propertiesfiles that are not valid UTF-8. - Fixed armor CIT loading when packs contain invalid legacy item ids.
- Added a turtle shell armor compatibility alias for legacy
texture.turtle_layer_1=...rules on modernturtle_scuteequipment assets. - Preserved sorted elytra CIT selection order so worn elytra variants respect weight/path priority.
- Updated the Fabric API dependency id from
fabrictofabric-api.
1.2.2-fork.3+1.21.11
- Fixed item CITs that use both
modelandtexture. - The resolved
texturevalue now replaceslayer0in the custom model. - Legacy
nbt.display.Namerules now also check the modern item name component. - Legacy name compatibility messages now log as warnings instead of errors.
1.2.2-fork.1+1.21.11
- Forked the abandoned CIT Resewn project into CIT Resewn Continuation
- Ported the project to Minecraft 1.21.11
- Updated the item model pipeline for the 1.21.11 client asset system
- Restored model-based item CITs
- Restored common texture-only item CITs
- Restored armor CIT support on the modern equipment renderer
- Restored elytra CIT support
- Added a first-pass enchantment glint implementation for 1.21.11
- Added a smoke-test resource pack and release packaging for the fork
Earlier Upstream Changes
- Fixed enchantment glints not working
- Switched legacy Stonecutter out in favor of the newer Stonecutter
- Fixed 1.19.4 port
- Fixed 1.20.1 port
- Fixed 1.20.4 port
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:8auYYPlH:QLOQXGtn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8auYYPlH:QLOQXGtn"
}

