Tags
Creators
Details
ppr-0.12.15
Compatibility
Changes
What's Changed
Features
26.3 Snapshot 8
The 26.3 specifics have been updated to support 26.3 snapshot 8 in preparation for the eventual RCs and release by @zannagh in https://github.com/zannagh/armor-hider/pull/329
Fixes
Glint on semi-translucent armor
Previously, enchantment glint was hidden by Armor Hider as soon as it interfered with the rendering of the armor piece. Now, enchantment glint is properly visible even when opacities between 5 and 95% are used. Please be aware that older game versions (1.20.x/1.21.x) do not have a separate glint render pass, so the rendered glint gets added into the render buffer by armor hider, which gives is a look that does not exactly match vanilla.
Translucent bodies on 26.2 with Shaders
When using Iris shaders with 26.2 a previous fix that made armor pieces invisible infront of water bodies or other translucent blocks has introduced a regression that caused player models (torso, legs, ...) to go translucent at certain viewing angles. This has now been resolved. The rendering artifact is still present with opacities between 5 and 95% which will be addressed in a follow up release.
Other
Armor Hider now does not publish intermediate snapshots or release candidate versions any longer for versions that have been surpassed by an actual game release. Hence, e.g. 26.2-rc.1 or 26.2-snap.7-11 mod versions will no longer be updated, as 26.2 already has a full release. This does not affect, for example, 26.3 snapshot 8 which at this point in time does not have an actual 26.3 release.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.12.14...v0.12.15
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:e4wbD3LD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:e4wbD3LD"
}

