Tags
Creators
Details
fab-mc-1.21.4-0.12.0-p.10
Compatibility
Changes
What's Changed
Features
Individual player configurations, closes #280 (#282) (a5199aa)
You can now control other player's looks more granularly. This requires the server to allow individual configurations (admins can access the setting within 'Other Settings' - it defaults to enabled).
To use the feature:
- Go to Armor Hider Settings
- Click the social icon next to Combat Detection / Invisibility Toggle / ...
- In the top bar, you'll find a global override configuration that can be used for application to ALL or only to players that are not using Armor Hider - depending on your preferences
- When connected to a server, each other player will be shown in the top bar and you can individually configure their looks on your client without affecting their end
Below the player selection bar, you'll find some toggle switches:
- Global other player render preference: Can be set to adjust other player's looks (as per the other configurations) or to render others as Vanilla - the server-side setting and your own client-side "disable armor hider" settings always have take precedence
- Unknown Players: You can either choose to use the global preset (which is defined below) or your own settings when an unknown player (someone not running Armor Hider) is rendered. Individual configurations for other players, if defined and enabled, take precedence over this.
- Use Global Config For Others: This defaults to OFF. This makes Armor Hider use the other player's settings if the server is running the mod and the player is using Armor Hider as well. You can set this to ON to apply your global configuration as well. An individual configuration for the other player (after selection in the top bar and enabling it) will take precedence over this.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.12.0-pre.9...HEAD
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:tElEZP5a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:tElEZP5a"
}


