Tags
Creators
Details
fab-mc-1.21.11-0.10.0-p.3
Compatibility
Changes
What's Changed
Fixes
1.21.4 Settings screen
The 1.21.4 settings screen has been fixed - it was previously missing sliders for chestplate, leggings and boots.
Duplicated logging on server events
There should now be no more duplicated log lines on server side events (configs received, server wide settings changed, ...)
Permission adjustments
The overall logic remains unchanged, but the server will now send permission packets (which tell the Armor Hider client-side instances what they're allowed to do server-wide) are now sent more often to make sure the client always has the most recent state. In addition, as a precursor to future changes, Armor Hider does now not only evaluate a true/false but a permission level.
Mixins failing on multiple versions
On <= 1.21.4 versions, failing mixin injectors which would prevent client startup have been fixed.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.10.0-pre.2...HEAD
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:GgG2my3y:3qWobJEA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:3qWobJEA"
}

