Content generated with AI — it may contain mistakes.

ExyliaArmorSkin/Getting startedUpdated in v1.4.1

Your first skin

Give yourself a skin, wear it from the wardrobe or from an item, take it off, and see it working in game.

Page 3 of 214 min read

In about five minutes you will wear a skin from the wardrobe, wear another from an item, and take both off.

Before you start#

ExyliaArmorSkin and its requirements are installed: see Installation. You are an operator, so you own every skin; a normal player owns none until you give one (step 1 below).

Wear a skin from the wardrobe#

Give a player a skin

Operators own every skin. For anybody else, hand one over for good, or grant its permission:

/armorskinsadmin unlocks grant <player> galaxy
/lp group default permission set exyliaarmorskin.skin.galaxy true

Or let them win one: /armorskinsadmin keys give <player> 1, then /wardrobe crate. See Set up the crate.

Put on an armour piece

Wear any armour, for example a netherite chestplate. The skin is drawn over it.

Open the wardrobe

Run /wardrobe. The armour along the top is what you are dressing; the grid below is every skin.

Dress a piece, or all four

Left click a piece to focus it, then click a skin. The Full set row dresses every piece you are allowed to wear at once.

Take it off

Click the skin that is already on, or right click the piece. Undress all empties everything.

Wear a skin from an item#

Give yourself the item

/armorskinsadmin give <you> galaxy. The command 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 skin is applied and the item is used up.

Take it off again

/armorskinsadmin remover <you>, then click that piece with the remover on the cursor. The skin comes back as an item.

Check that it works#

  • You see the colour (and trim) on your body in third person (F5) and in your inventory. Other players see it too.
  • 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.
  • The armour itself is unchanged. Enchantments, armour points and durability stay exactly as they were.
Players are shown the skin only if they own it

Applying an item never asks for a permission, but by default a player who owns the skin neither by permission nor by unlock is shown their real armour. Grant exyliaarmorskin.skin.<id> or an unlock, or set hide-without-permission: false in config.yml. See Permissions.

Write your own skin#

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

skins.yml
yaml
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 run /armorskinsadmin reload. The skin exists at once, /armorskinsadmin list shows it, and anyone already wearing it sees the new colour.

Change the name, not the key

The key is what the armour stores. Renaming it orphans every piece already wearing it, and they show their real look again.

What the item commands say when something is wrong
SituationMessage key
The clicked item is not armournot-armor
The skin does not list that pieceunsupported-piece
The armour already wears a skinalready-skinned
The remover was used on unskinned armourno-skin
The skin id on the armour is no longer in skins.ymlunknown-skin
Removing with no free inventory slotinventory-full: the skin stays and the remover is not used up

Skin items are only read inside your own inventory window (including the armour slots). Dropping one onto armour in a chest does nothing.

Something missing on this page? Tell us on Discord