A small server/client side mod to alter transparency of armor items (relayed to other players via server).
This mod is heavily inspired by Show Me Your Skin! (https://github.com/enjarai/show-me-your-skin).
The settings are accessible via "Skin Customization" in game:
Your locally set preferences (on your client) will get sent to the server on change or join and vice versa and player joining a server will retrieve the config library from the server in order to apply the player preferences to other clients.
- Helmet: Opacity slider (0-100%) for head slot
- Affect Skulls: When enabled, helmet opacity changes also affect skulls (non-armor head items like skeleton or creeper skulls)
- Chestplate: Opacity slider (0-100%) for chest slot
- Affect Elytra: When enabled, chestplate opacity also affects elytra
- Leggings: Opacity slider (0-100%) for legs slot
- Boots: Opacity slider (0-100%) for boot slot
- Combat Detection: Enables detection of combat to show your armor when you are in combat
- Apply your settings to unknown players: Whether to use your own opacity settings or the default settings (armor shown normally, as without the mod) when a player's settings cannot be determined — for example when using the mod only client-side on an unmodded server (see Preferences Matrix below)
- Disable Armor Hider features: Globally disable Armor Hider on your client. If the server is forcing Armor Hider off, this setting is ignored as armor will be shown regardless
- Disable Armor Hider for other players: Disable Armor Hider rendering for other players' armors only. If the server is forcing Armor Hider off or the global disable is set, this setting is ignored
These settings require operator permissions and apply server-wide, overriding individual player preferences.
- Armor in combat (server): Forces combat detection server-wide — when enabled, armor is always shown for any player in combat, overriding each player's individual combat detection setting
- Force Armor Hider off for all players: Forces Armor Hider to be disabled for all players on the server, overriding all individual settings
Your locally set preferences get sent to the server on change or join. Players joining a server will retrieve the preference library from the server in order to apply other players' preferences on their client.
The following matrix shows how preferences are resolved depending on where the mod is installed:
| Mod on Server | Mod on Client | Behavior |
|---|---|---|
| Yes | Yes | Full functionality. Your preferences are synced to the server and relayed to other players. You see other players' actual configured armor opacity. |
| Yes | No | No effect. The server stores preferences but the vanilla client cannot render transparency changes. |
| No | Yes | Client-side only. Other players' preferences cannot be determined. Depending on the "Apply your settings to unknown players" setting: ON — your own opacity settings are applied to all players; OFF — default settings are used (armor rendered normally, as without the mod). |
| No | No | No effect. The mod is not present. |
Settings
Main Menu Settings
Ingame Settings (Admin)
Combat Detection
Enabled Combat Detection
Disabled Combat Detection
Join the Discord server for support, discussion, and feature requests.
Feel free to create an issue on the GitHub repository or reach out on Discord to make me aware of problems or ideas that could make this mod better.
All Minecraft versions are built from the main branch using Stonecutter for
multi-version support. GitVersion handles semantic versioning automatically.
Release flow:
- Prereleases are created automatically on every push to
mainthat includes code changes (commits prefixed withci:,docs:,build:, orchore:are skipped) - Releases are created manually via GitHub Releases with version validation
- All versions are published to Modrinth with the format
fabric-[MC_VERSION]-[MOD_VERSION]
Version format:
- Releases:
0.7.2 - Prereleases:
0.7.3-pre.1,0.7.3-pre.2, etc.
