Tags
Creators
Details
Licensed MIT
Published 2 weeks ago
Updated 2 days ago
All versions
0.1.0-1.21.11-(Fabric)
Release
0.1.0-1.21.11-(Fabric)2 days ago 10
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Changes
0.1.0-1.21.11-(Fabric)
CutClean Reborn — Minecraft 1.21.11 (Fabric)
This release brings clearer in-game configuration and the full CutClean Reborn ruleset to Fabric on Minecraft 1.21.11.
Added
- Fabric support — customize mob and ore drops, Timber, automatic enchantments, Clean Stacks, sugar cane and equipment rules on this Minecraft version.
Improved
- Timber settings are grouped into tools, leaves and apples, and breaking controls.
- Stuff Rules makes armor limits, enchantment caps and the unique mace easier to find and configure.
- Better Sugar Cane separates player breaks from support loss, each with its own chance and quantity.
- Press Escape to return to the previous menu or cancel unfinished input.
- Configuration menus use concise English labels.
- Updated the CCR logo.
Fixed
- Clean Stacks converts only drops from blocks you break, including Timber. Enabling it does not change stored items, command-given items, unrelated pickups or crafting results.
Compatibility / servers
- Requires Java 21, Fabric Loader 0.19.5 or newer, and Fabric API.
- Install in
mods/for singleplayer or on a Fabric server. Players can join a dedicated CCR server without installing CCR on their client. - Server operators and singleplayer world owners can use
/ccr config.
Before updating
- Existing configuration paths remain compatible.
- Close your world or stop your server before replacing the previous CCR JAR.
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:2GUh56dK:c24JSApW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2GUh56dK:c24JSApW"
}

