2.2.0-MC26.2
Compatibility
Changes
Ver2.2.0 -In-Game Config Update-
Until now, AcroWield could only be configured by editing the config file directly. As more features were added, the config file became cluttered, especially with the many offhand display options.
This update overhauls the config system!
Changes
You can now change AcroWield’s settings in-game: On the title screen, click [Options…] (bottom left), then [AcroWield] (bottom right). While playing, press Esc → [Options…] → [AcroWield].
Added parent and child settings:
For example, Shield Bash requires Dodge, so when Dodge is off, Shield Bash is turned off automatically. (The child setting is grayed out, and hovering over it shows why.)
Reorganized “Limit Offhand Weapon Display” and “Stow Unusable Offhand Weapon”:
Limit Offhand Weapon Display: while the main-hand item has a right-click use, the offhand weapon is not drawn in your hand and can’t attack. Stow Unusable Offhand Weapon: only decides whether the hidden weapon is shown on your back in third person.
Moved “Offhand Bare-Hand Attack” to the offhand display section:
Rewrote all setting descriptions to match the actual behavior. The config file now has an English description for every setting, with blank lines between them for readability.
Fixes
Fixed a bug where, with “Offhand Bare-Hand Attack” on and “Always Render Offhand” off, you could punch with an offhand arm that wasn’t drawn. Fixed right-click deflecting projectiles while holding something that can’t attack (a shield, a torch, etc.) in the offhand.
Notes
The settings for offhand weapon display were renamed and their meaning changed, so your old values are NOT carried over. Please check them in the settings screen. Dash speed multipliers can’t be changed in-game, for safety and because they are fine-tuned numbers. Please keep editing them in the config file.
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:kKNPTNBW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2HNn1tqB:kKNPTNBW"
}

