Getting started

First steps

Dress from the wardrobe, apply a skin item, take it off, and write a skin of your own.

Wear a skin from the wardrobe

Grant the command

/lp group default permission set exyliaarmorskin.wardrobe true

Open it

/wardrobe. The armour along the top is what is being dressed; the grid below it is every skin, previewed in the piece that is focused.

Dress a slot, or all four

Left click a slot to focus it, then click a skin. The full-set button on the left dresses every piece the player is allowed to wear at once.

Take it off

Click the skin that is already on, or right click the slot. Right clicking the full-set button empties the wardrobe.

Nothing was written to the armour: the choice is a row in armorskin_wardrobe and follows the player, whatever they equip.

Wear a skin from an item

Give yourself the item

/armorskinsadmin give <you> galaxy. The command tab-completes every skin id, and takes an optional amount from 1 to 64.

Drag it onto armour

Open your inventory, pick the skin item up with the cursor and click a piece of armour. The click is cancelled, the skin is applied and the item is consumed.

Put the armour on

You see the skin in your paper doll and in F5; everyone tracking you sees it on your body. The piece is still whatever it was — check with /data get entity <you> Inventory.

Take the skin off

/armorskinsadmin remover <you>, then click that same piece with the remover on the cursor. The skin comes back as a skin item and the remover is consumed.

Wear the whole set

Wear all four pieces with the same skin and its set bonus starts: inferno announces the set and surrounds you with flames until you take a piece off.

Applying needs the skin's own permission

By default a player must hold exyliaarmorskin.skin.<id> to apply a skin and to be seen wearing it — exyliaarmorskin.skin.* covers all of them, and both nodes default to op. Grant the node, or turn require-permission and hide-without-permission off in config.yml. See Permissions.

Applying only works in your own inventory

The click is only read inside the player inventory window — that includes the four armour slots. Dropping a skin item onto armour lying in a chest does nothing.

What can go wrong, and what it says

Situation	Message key
The clicked item is not armour	`not-armor`
The skin does not list that piece	`unsupported-piece`
The armour already wears a skin	`already-skinned`
The remover was used on unskinned armour	`no-skin`
The skin id on the armour is no longer in `skins.yml`	`unknown-skin`
Removing with no free inventory slot	`inventory-full` — the skin stays on the armour and the remover is not consumed
The player lacks `exyliaarmorskin.skin.<id>`	`no-permission` — nothing is written and nothing is consumed

Write your own skin

Add an entry to skins.yml. The key is the id stored on armour; everything else is what it looks like:

skins.yml

skins:
  ruby_ward:
    name: '{error}&lRUBY WARD'
    pieces: []            # empty means all four
    color: '#c0102a'
    trim-pattern: ward
    trim-material: redstone
    icon: WARD_ARMOR_TRIM_SMITHING_TEMPLATE
    animation: ''         # a preset from animations.yml, or rainbow / pulse / frames

Then /armorskinsadmin reload. The skin exists immediately, /armorskinsadmin list shows it, and anyone already wearing a piece with ruby_ward on it sees the new colour without re-equipping.

The id is what the armour stores

Renaming an entry orphans every piece already wearing it: the armour keeps the old id, which no longer resolves, so it shows its real look again. Change the name, not the key.

Skins

Every key, and the twenty skins that ship.

Effects

Sounds, titles and particles while a skin is worn.

Something missing on this page? Tell us on Discord