b2.3.0
Compatibility
Changes
Creative Toolkit+ b2.3.0
Waypoint manager UX overhaul — live search, real edit mode, full color picker, two-step delete, and a one-click "move waypoint here".
For Minecraft 26.1.x · Fabric · public beta
What's new
b2.2.0 shipped the waypoint system. b2.3.0 makes it a real tool.
Live search bar
A full-width search field at the top of the manager filters the list as you type — by name, color, and dimension id (case-insensitive substring). The subtitle line updates to "X of Y waypoints" whenever a filter is active.
Per-row buttons that you can actually read
The cramped icon trio (TP / • / ✖) is gone. Each row now has clear text buttons:
TP— teleport to the waypoint.Edit— opens the new edit screen for this waypoint.Delete— deletes the waypoint (the in-list button is the quick path; the edit screen has the safer two-step confirm).
Tooltips spell out the target so you can never confuse two waypoints with similar names.
Edit mode (new)
Clicking Edit swaps the screen into a single-waypoint editor without leaving the manager:
- Editable name field — same
[A-Za-z0-9_\-.]+rules as the server, so invalid names get caught client-side before any packet flies. - 4×4 color grid — 16 clickable color swatches matching
Waypoint.COLORSexactly. Selected swatch gets a white outer ring + double-inset inner border so it's unmistakable. - Read-only position read-out — shows X / Y / Z / yaw / dimension, with a wide
[Move waypoint to my current position]button that updates the waypoint in place (preserving name, color, and creation time). - Bottom action row —
Delete/Cancel/Save.Deletehas a two-step confirm: first click swaps the label to redConfirm delete?for 3 seconds; a second click within that window actually deletes.Savetranslates the diff into actions — rename if the name changed, recolor if the color changed. If neither changed,Savebehaves likeCancel.
Snapshot-aware
If the waypoint you're editing gets deleted server-side (by another client, or by you via the in-list delete), the screen automatically pops back to the list view. If it gets moved/recolored elsewhere, the editor reflects the latest state without losing your in-progress text.
Visual polish
- Same vanilla beige beveled panel as
CtpEnchantScreenfor visual consistency. - Sunken backdrops under the list and the create-form area; alternating row banding (subtle); per-row hover overlay.
- Dedicated draggable scrollbar thumb on the right edge of the list (vanilla creative-tab style).
- Distance display switches to kilometers above 1000 m (
%.1fkm), so cross-continent waypoints stay readable. - Form-field continuity across rebuilds: typing in the search/name fields no longer gets wiped by snapshot updates.
Highlights from before
If you're new, here's what was already in the mod:
- Right-click / shift-click apply — drop an enchanted book on an item to apply its enchantments.
/ec menuand/ec menu-op— vanilla-styled enchanting screens./ec sharpness 5—/ecworks as a/enchantshortcut, with self-targeting when no target is given./back [n]— teleport back to where you were, with full history and death-location tracking./heal,/feed,/enderchest,/day,/night,/noon,/midnight— small creative-mode QoL commands.- In-game config screen via
/ec config.
Installation
- Fabric Loader 0.19.0+ for any 26.1.x Minecraft release.
- Fabric API in your
mods/folder. - Drop
creativetoolkitplus-b2.3.0.jarinmods/. - Launch.
The first run creates config/creativetoolkitplus.json you can hand-edit.
Compatibility
- Minecraft:
26.1.x - Loader: Fabric Loader 0.19.0+
- Required: Fabric API
- Java: 25 (already required by MC 26.1)
Existing waypoint files from b2.2.x load unchanged — no schema change. The new move_here action is server-side only and doesn't affect on-disk format.
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:lKbPkK0p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XJechTzS:lKbPkK0p"
}

