Tags
Creators
Details
fab-mc-26.1-rc.1-2-0.12.0-p.1
Compatibility
Changes
What's Changed
This release is deliberately a beta. I will keep 0.12.0 in beta until in a few weeks (aiming at a proper release end of third week of July or within last week of July) when initial issues with it have been ironed out. Please be aware that this beta can carry problems (even though I really did my best to add more tests and quite thoroughly tested the release) - so if you encounter any, please report them via GitHub or Discord and either wait for a fix or downgrade to 0.11.x while waiting. As usual, I'll try to address anything that comes up as timely as I can!
With 0.12.0 roughly 50% of the mod has been rewritten, introducing an API (for making it easier for other modders to put compatibilities together) and putting in a homogeneous architecture how Armor Hider resolves items it interferes with, sets up scopes (now with individual scopes per item AH interacts with and not only one global 'we're changing this player's items' scope) and tears them down as well as having version-independent render changes (that operate per piece as well). In addition, I have changed up most of the mixins Armor Hider relies on to make them easier to read and maintain.
This is - in my opinion - a huge step forward to make future additions more straightforward to add (also with fewer regressions) and the mod more maintainable.
My expectation with 0.12.0-pre.1 is actually: Literally zero behavioral changes! I explicitly held back on adding in new fixes or features so regressions are easier to spot and resolve. Yet, some legacy Minecraft versions (e.g. 1.20.x) might benefit from this release as core mod functionality should now be similar throughout all game versions and loaders.
Any recently reported problems (see GitHub issues) will be taken care of based on this release.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.11.9-pre.1...v0.12.0-pre.1
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:1UIEWNbg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:1UIEWNbg"
}


