a2.1.0
Compatibility
Changes
Creative Toolkit+ a2.1.0
Adds an in-game configuration screen so you don't have to hand-edit JSON.
For Minecraft 26.1.x · Fabric · alpha
What's new
In-game configuration screen
A new CtpConfigScreen lets you edit every config value live, without restarting and without touching the JSON file.
- Open it via
/ec-config— registered as a Fabric client command (no server roundtrip; opens the screen locally). - Or bind a key — the new
key.creativetoolkitplus.configkeybind ships unbound; assign it under Controls → Misc. - The screen edits a working copy (
ModConfig.copy()) and only commits to disk on Save & Apply. - Reset to Defaults swaps in
ConfigManager.defaultConfig()and rebuilds the widgets. - Cancel closes without writing.
Widget choices
- Booleans render as
Checkboxwidgets with hover tooltips so you can see what each toggle does. soundTypeuses aCycleButton<String>.opMenuMaxLeveluses anEditBox(nosetFilterin 26.1 — invalid input is just ignored by the responder, the previous valid value sticks).- Lists are read-only with a count summary; edit them in JSON.
Server-context awareness
A note painted into the screen distinguishes singleplayer / integrated-server vs dedicated-server, since on a dedicated server only client-side knobs (sounds / particles / messages) actually take effect for the connected player.
Version display
A new MOD_VERSION_DISPLAY constant on CreativeToolkitPlusMod shows the version in the screen footer without a FabricLoader lookup.
/ec help update
Help text for /ec now mentions /ec-config.
Installation
- Fabric Loader 0.19.0+ for any 26.1.x Minecraft release.
- Fabric API in your
mods/folder. - Drop
creativetoolkitplus-a2.1.0.jarinmods/. - Launch.
The first run creates config/creativetoolkitplus.json. Existing a2.0.x configs load unchanged.
Compatibility
- Minecraft:
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:dHuc3BKo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XJechTzS:dHuc3BKo"
}

