0.0.0
Latest
2026-07-31 · Initial release
The first release of MCIdentityCosmetic, the standalone cosmetic add-on for MCIdentity. Every identity wears its own skin and aura, stored in the add-on's own database and opened with /cosmetic.
Added A skin and an aura per identity
- Two independent fields: a skin (a Base64 texture blob) and an aura (a system code). Either may be absent, and a blank value means the same thing as an absent one.
- Each field is written by its own statement, so changing one never clears the other — even when two changes race.
- The skin is deliberately not length-capped: a full profile-property texture is a large value, and truncating it would produce a broken skin rather than a rejected one. The aura is trimmed and capped at 255 characters.
- Every read and write is tied to the identity MCIdentity says the player is wearing, never to the player, so two identities owned by one player can look completely different.
Added Its own storage
- The cosmetic data is created and owned by this add-on, with no link to anything MCIdentity stores.
- Backends: SQLite (default, zero configuration), MySQL, PostgreSQL, MongoDB, or the shared central server, chosen in the add-on's configuration file.
- The column a write targets comes from a frozen two-entry allow-list; anything else is rejected before a statement is built.
- All database work runs off the game thread on the add-on's own worker pool, and a failed read yields an empty result rather than another identity's cosmetics.
Added Menu, commands, and developer API
- /cosmetic opens the one-row cosmetic menu for the identity you are wearing. /cosmetic info reads back what it currently wears.
- /cosmetic skin <texture|clear> and /cosmetic aura <code|clear> require mcidentitycosmetic.admin.
- A cancellable cosmetic set event, telling listeners the player, the identity, which field is changing, and the new value (none when clearing).
- A published developer library in three modules, matching the core plugin's shape.
Note Requirements
- One universal jar for SpigotMC, PaperMC, and Folia; the server type is detected at startup.
- MCIdentity 4.0.0 or newer is a hard dependency — that is the release where the core stopped shipping a cosmetic system of its own. An older core logs a warning at startup.
- Every profession may wear cosmetics, the base player profession included. The profession restriction that applies to runes was never a cosmetic rule.
- Skins and auras from MCIdentity 3.x are not migrated. The core drops its own table on upgrade and this add-on starts empty.