Tags
Creators
Details
fab-mc-1.21.9-10-0.10.14-p.2
Compatibility
Changes
What's Changed
I've had this PR open for a while and decided to put out another pre-release in case there are any regressions. If none appear, I'll create a non-beta release out of this in a few days.
Features
-
This release removes equipment render states eagerly when a piece of armor should be fully hidden in game versions that support it (after 1.21.4). This should improve compatibility to other mods that correctly read their render changes from the render state.
-
Slot modifications (think, the piece of information that gets injected into MC's rendering per slot) are now cached instead of being recalculated on each render pass - and only recalculated when the configuration changes for the player. While computationally cheap previously, this makes the mod more efficient.
-
I've merged duplicated mixin classes within the same files, where the mixins would do basically the same. Previously, code was duplicated between e.g. game version 1.21.4 and 1.21.11. Now, only the imports and mixin methods between versions change, but the code that Armor Hider users is more homogeneous throughout game versions. This should make it easier to pin down issues.
Fixes
Elytra Flight Detection
I had another look at the render changes to Elytras while the player is in flight. Transparency or hiding the Elytra should now be correctly suppressed (i.e. Elytra always shows) when a player is in flight.
26.1 and later icon issue
The icons Armor Hider uses on the GUI should now correctly work on 26.1 and later instead of displaying checkerboard / missing texture sprites.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.10.14-pre.1...v0.10.14-pre.2
Optional dependencies
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:VNevUPjg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:VNevUPjg"
}


