1.8.1-MC26.2
Compatibility
Changes
AcroWield ver 1.8.1 Changelog
Fixes regarding the rendering of the off-hand arm:
The scenarios in which the off-hand arm is rendered have been restricted to more appropriate situations. Additionally, the off-hand arm rendering system has been revised to reduce the risk of rendering issues caused by items from other mods.
Addition of new config options:
To provide more precise control over off-hand rendering in cases where the "Fixes regarding the rendering of the off-hand arm" mentioned above are not enough, the following four options have been added to the config file:
alwaysRenderOffhand A global toggle for off-hand rendering. Setting this to "true" makes the left arm visible. Setting it to "false" reverts to vanilla behavior (the arm is not rendered if the off-hand is empty).
offhandRenderBlacklist Hides the item model held in the off-hand while keeping the arm visible. If for some reason you want to hide the off-hand item but keep the arm displayed, please add the item ID here.
offhandFullHideBlacklist Completely hides both the arm and the item. When an item ID listed here is held in the off-hand, both the item model and your arm will be completely hidden (unlike the aforementioned "render blacklist," which leaves the arm visible).
mainHandItemsHideOffhand Hides the off-hand arm based on the state of your main hand (right hand). When an item ID listed here is held in the main hand, the off-hand (left arm) is forced to hide. If issues such as the off-hand appearing unnaturally while using gun mods are not resolved by the rendering adjustments mentioned above, please add the item ID here. Support for "TACZ-Refabricated" is included by default.
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:2HNn1tqB:JDJnVrbE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2HNn1tqB:JDJnVrbE"
}

