Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 days ago
All versions
1.6.1
Beta
Hide Your Armor 1.6.12 months ago 2,161
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
NeoForge
Supported environments
Client and server
Changes
1.6.1
Fixed
- #4 Elytra is affected by chestplate opacity setting independently of Elytra visibility setting – chestplate slider was bleeding into elytra (same equipment slot). Now elytra has its own independent opacity in
EquipmentRendererMixin.java:50(cfg.elytraOpacity) - #5 Mod needed serverside but crashes when on it
- Dedicated server crash
NoClassDefFoundError: net/minecraft/client/gui/screens/Screen at HideArmorNeoForge.<init>:19– client init was loaded on servers. Now guarded via reflection inHideArmorNeoForge.java:13→HideArmorNeoForgeClient.java:1 Connection Lost: Channel hidearmor:sync missing on server side, but required on client!– made payload optional inHideArmorNeoForge.java:42(event.registrar("1").optional().playBidirectional(...))Cannot register payload hidearmor:sync as it is already registered– switched from separateplayToServer+playToClientto singleplayBidirectionalUnsupportedOperationException: Payload hidearmor:sync may not be sent to the server!on vanilla servers – addedhasChannelguard inNeoForgeClientHandler.java:57andcanSendguard inHideArmorFabricClient.java:61
- Dedicated server crash
- Black screen + spam
Entity renderers map is empty, will retry later– cape mixin targetedOrderedSubmitNodeCollector/IIIIwith 0 hits. FixedCapeRendererMixin.java:43toSubmitNodeCollector/III(verified viajavap -c CapeLayeronminecraft-merged-043a8b3edf-26.2.jar)
Transparency
- Restored gradual opacity: Elytra (per-player
cfg.elytraOpacity) and Cape (RenderTypes.entityTranslucent+ARGB.color(alpha,255,255,255)) + Trim (armorTranslucent). Skulls/blocks remain hide at 0% (binary) to avoid fragileSkullBlockRenderermixin. - Verified
BUILD SUCCESSFUL+build/universal/HideYourArmor-1.6.1-universal.jar
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:htFd9eMF:l9bZkZXZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:htFd9eMF:l9bZkZXZ"
}

