a2.0.0
Compatibility
Changes
Creative Toolkit+ a2.0.0
Renamed from Creative Enchant Book to Creative Toolkit+, and ships two new in-game enchanting screens (
/ec menufor vanilla rules,/ec menu-opfor unrestricted) on top of the original right-click apply.
For Minecraft 26.1.2 · Fabric · alpha
What's new
Mod renamed: Creative Enchant Book → Creative Toolkit+
This is the start of a wider creative-mode toolkit; right-click apply is just the first feature. Identifiers, packages, asset paths, and the config file all moved:
mod_id:creativeenchantbook→creativetoolkitplus- Java package:
com.creativeenchantbook→com.creativetoolkitplus - Main entrypoint:
CreativeToolkitPlusMod - Client entrypoint:
CreativeToolkitPlusClient - Mixin config:
creativetoolkitplus.mixins.json - Assets dir:
assets/creativetoolkitplus/ - Config file:
config/creativetoolkitplus.json
Heads up: your old
creativeenchantbook.jsonis not auto-migrated — copy values across by hand if you were running v1.x.
New commands
/creativetoolkitplus(long-form root) and/ec(short alias).- Subcommands:
reload,menu,menu-op.
- Subcommands:
/ec-menu— opens the vanilla-valid enchant screen./ec-menu-op— opens the unrestricted enchant screen (op only).
New in-game screen: CtpEnchantScreen
One input slot + a scrollable enchantment list with −100 / −10 / −1 / +1 / +10 / +100 / X buttons.
- Vanilla mode filters to
Enchantment#isSupportedItem(stack), respects max levels, and rejects conflicts on the server. - OP mode lists every enchantment, lets you set any level up to
opMenuMaxLevel(default 32,767), no compatibility checks.
Server-authoritative networking
A new C2S payload MenuSetEnchantPayload(syncId, enchantmentId, level) carries each click. The server validates everything and writes the result; the client just requests.
New config keys
opMenuMaxLevel(int, default32767) — cap for the OP-menu spinner.vanillaMenuRequiresOp(bool, defaultfalse) — if true,/ec-menubecomes op-only too.
What didn't change
- Right-click apply behavior from v1.0 is preserved unchanged. Drop a book on the cursor, right-click any item slot — same as before.
- All v1.x config keys (
creativeOnly,allowSurvival,allowUnsafeEnchantments,consumeBooks, etc.) are preserved.
Installation
- Fabric Loader 0.19.0+ for Minecraft 26.1.2.
- Fabric API in your
mods/folder. - (Optional) If you were running the old
Creative Enchant Bookv1.x: remove its jar. - Drop
creativetoolkitplus-a2.0.0.jarinmods/. - Launch.
Compatibility
- Minecraft:
26.1.2(this build is patch-pinned;a2.0.1widens this to26.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:KgAWYx96"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XJechTzS:KgAWYx96"
}

