Links
Tags
Creators
Details
Licensed MIT
Created 4 years ago
Updated 2 years ago
All versions
1.1.0
Beta
v.1.1.04 years ago 161
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
New features:
- Added a slot to the inventory where the offhand item can be placed. This is configurable! If experiencing compatibility issues, try disabling this feature.
- Et Futurum's totem of undying now works in the offhand.
- Added JinRyuu's mods compatibility for rendering an emtpy offhand.
- If using an axe in the mainhand and a log is highlighted, the mainhand action takes precedence. Same for shovels & dirt.
- Updated ingame mod info, rendering an empty offhand is now configurable from the mod menu.
Bug fixes:
- Fixed items not breaking in the offhand.
- Fixed offhand item being moved back into the main inventory on login when empty offhand use is disabled.
- Fixed items moving around in the hotbar when moving an item into the offhand while InventoryTweaks is installed.
- Fixed offhand items vanishing on pickup in survival mode if the player's inventory is full.
- Fixed some items vanishing on offhand use.
- Fixed not being able to attack with an empty offhand
- Fixed being able to break blocks behind an entity being attacked with the offhand.
Visual Fixes:
- Fixed offhand and sometimes even mainhand clipping through blocks when using Optifine.
- Fixed right hand's lighting being disabled.
- First person offhand is now rendered directly after the mainhand renders.
- The offhand item no longer shows up on the first main hotbar slot while in creative mode's survival inventory GUI.
- Fixed inventory GUI darkening when eating or drinking with the offhand.
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:Dwz9syqF:JOtwq9Kd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Dwz9syqF:JOtwq9Kd"
}

