Tags
Creators
Details
v1.0.0
Compatibility
Changes
Better With Hands v1.0.0
Did you know that you have a second hand? Look down. It's right there. You've had it this whole time.
For years, Steve has been living with a mysterious condition — completely ignoring his left arm. He'd hold a single pickaxe while his other hand just... hung there. Doing nothing. Watching. It's frankly a miracle he survived this long.
I cured him.
This is the initial release of Better With Hands for BTA 7.3_04 - a complete reimagining of the offhand system. This isn't a lazy port — it's what dual-wielding should have been from the start.
Features
- Dedicated offhand slot with proper inventory UI integration
- Full swing animations - your arm actually moves, torso rotates, no shortcuts
- Smart rendering - properly mirrored items in first-person and third-person
- Dynamic hand priority - automatically picks the best tool for mining, combat, or building
- HUD integration - smooth sliding offhand slot display
- Multiplayer support - everything syncs, other players see your animations
- Left-handed mode - full support for southpaws
Controls
- F - Swap items between main hand and offhand
- X - Toggle hand priority (which hand is "active")
Both keys are rebindable in Options.
Installation
- Install Babric mod loader
- Download
better_with_hands-1.0.0.jar - Place in your
mods/folder - Launch BTA 7.3_04
- Configure in Options > Better With Hands
Requirements
- BTA 7.3_04
- Babric mod loader
Practical Examples
Mining Setup: Pickaxe + Torches (mine and place light without switching)
Combat Ready: Sword + Food (fight with instant healing access)
Building: Two block types (swap with X instead of hotbar scrolling)
Dynamic Mode: Pickaxe + Axe (auto-switches between stone and trees)
Steve can finally use both hands. You're welcome.
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:iyLOebux:p4Fe7ScU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iyLOebux:p4Fe7ScU"
}

