Tags
Creators
Details
All versions
1.0.3+8.0.1
Release
Better With Hands v1.0.36 days ago 116
Compatibility
Minecraft: Java Edition
b1.7.3
Platform
BTA (Babric)
Supported environments
Client and server
Required content
Unavailable version
Changes
Better With Hands 1.0.3
Multiplayer fixes, dual wielding that follows your hands, working maps and better compatibility with other mods.
Features
- New Vanilla indicator style.
- The mod follows the game's left-handed setting. The offhand, the arms and the HUD slot switch sides with it.
- Dual swords: left click hits with the sword in your left hand, right click with the one in your right hand.
- Right click with two swords still gets you into boats and minecarts.
- Dynamic Hand Priority now also picks the hand for attacks.
Fixes
- Picked up items go back into the offhand first, so torches return to it after breaking them.
- Number keys swap items with the right hotbar slot.
- The hand indicator stays in place with GUI scale override and the vertical hotbar.
- Offhand tools take durability and mining with them follows reach and spawn protection on servers.
- Dual sword attacks with the offhand work on servers.
- Right click on blocks works again while holding two swords.
- Offhand items can be eaten, thrown or used in the air.
- Maps work in the offhand: they update, sync on servers and are held in one hand when the other hand is busy.
- The offhand is kept on respawn with keepInventory.
- Other players see the offhand item with its name and data.
- The offhand updates while a chest or other container is open.
- The offhand slot is hidden on servers without the mod instead of causing errors.
- The offhand arm in third person follows the same pose as the main arm.
Requirements
- Minecraft: BTA 8.0.1
- HalpLibe: 6.2.0+8.0.1
- Fabric Loader: 0.18.4-bta.11
- Java 17
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:ImIbsWlR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iyLOebux:ImIbsWlR"
}

