All versions
1.0.1
Release
True Toolbelt 1.0.1last month 9
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
True Toolbelt v1.0.1 — Hotfix & Quality-of-Life Update
Bug Fixes & Grave Mod Compatibility
- Universal Gravestone Compatibility (Death Keeper, Corail, etc.):
- Implemented pre-death tool recall: active tools deployed in your hotbar holster are now safely recalled into the toolbelt component before death drops execute.
- Elevated drop event priority so the complete, unified toolbelt is placed into the drop list before grave mods intercept drops and cancel the event.
- Fixes the issue where gravestones failed to capture the toolbelt or lost stored tools upon death.
- Shift-Click Item Eviction Guard:
- Fixed a race condition where shift-clicking to equip a toolbelt into an occupied hotbar slot could overwrite and void the evacuated item. Item should not be lost now (I hope).
- Toolbelt Tooltip:
- Hovering over the active tool in the open drawer now properly displays the full vanilla item tooltip (name, enchantments, attack damage, and live durability).
New Features
- Right-Click-To-Equip:
- Right-clicking the toolbelt directly from your hand on your hotbar instantly equips it (not sure how I forgot about this).
- Slider Tool Equip:
- Dragging or clicking the inventory slider across loose tools (Pickaxe, Axe, Shovel, Hoe) in your hotbar automatically absorbs them into your belt's empty drawer slots in one fluid sweep, leaving your hotbar clean!
- Tool Adoption:
- Equipping a belt when your assigned hotbar slot already holds a matching tool now adopts that tool directly as your active holster item without displacing it.
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:ZOL8bi7N:lWchK6JN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZOL8bi7N:lWchK6JN"
}

