a2.0.1
Compatibility
Changes
Creative Toolkit+ a2.0.1
The same
a2.0.0jar, but the dependency widens from~26.1.2to~26.1so it loads on any 26.1.x patch release without a rebuild.
For Minecraft 26.1.x · Fabric · alpha
What's new
Wider Minecraft compatibility
The same jar now loads on any 26.1.x patch release — 26.1.0, 26.1.1, 26.1.2, 26.1.3, etc. — without rebuilding.
Compile target stays 26.1.2 (patch versions of MC are binary-compatible at the API level), so this is a metadata-only change — no behavior changes.
Folder rename
The version folder went from creativetoolkitplus-26.1.2/ → creativetoolkitplus-26.1.x/ to reflect the wider range.
New version-prefix convention adopted
Going forward, jars use a single-letter prefix:
a= alpha — incomplete, expect missing features and crashes.b= beta — feature-complete for the milestone, but unverified in real-world play.- (no prefix) = stable — graduated from beta, considered safe for production servers.
This release sits at the very top of the alpha line.
Highlights from a2.0.0
If you're new to Creative Toolkit+:
- Right-click any item with an enchanted book in Creative to apply its enchantments.
/ec menu— vanilla-styled enchanting screen with strict compatibility checks./ec menu-op— unrestricted enchanting screen (op-only); set any level on anything./ecand/creativetoolkitpluscommand roots with subcommandsreload,menu,menu-op./ec-menuand/ec-menu-opshortcuts.- All settings in
config/creativetoolkitplus.json, hot-reloadable with/ec reload.
Installation
- Fabric Loader 0.19.0+ for any 26.1.x Minecraft release.
- Fabric API in your
mods/folder. - Drop
creativetoolkitplus-a2.0.1.jarinmods/. - Launch.
If you're upgrading from a2.0.0, just swap the jar — no config changes needed.
Compatibility
- Minecraft:
26.1.x(any patch — 26.1.0 through 26.1.x) - Loader: Fabric Loader 0.19.0+
- Required: Fabric API
- Java: 25 (already required by MC 26.1)
License
MIT.
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:XJechTzS:9JQ9t9gP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XJechTzS:9JQ9t9gP"
}

