Set up the wardrobe
Let players pick a skin for each armour piece from /wardrobe, choose between items, wardrobe or both, and see it working.
The wardrobe is a menu where players pick a skin for each armour piece, or for all four at once, and wear it. You end with /wardrobe working the way you want: items only, wardrobe only, or both.
A skin item writes onto the armour. The wardrobe stores the choice against the player, so it survives death, trading and a change of gear, and the armour is never written to.
Before you start#
You have at least one skin, see Create and edit skins. Players need exyliaarmorskin.wardrobe, which everyone has by default.
Set it up#
Pick where skins come from
In config.yml, set behaviour.mode to item, wardrobe or both (the default). See the three modes below.
Reload
Run /armorskinsadmin reload.
Give a player skins
Operators own every skin. Others own a skin through its permission (exyliaarmorskin.skin.<id>), /armorskinsadmin unlocks grant <player> <skin>, the crate or the shop.
Open it
Run /wardrobe.
With menu.style: SPATIAL in config.yml, /wardrobe opens the wardrobe in the world instead: the player tries skins on their own body and saves or buys in place. /wardrobe 3d and /wardrobe classic open either one. See Set up the 3D wardrobe.
Check that it works#
/wardrobe opens a 54-slot window. The armour along the top is what the player currently looks like; the grid below is every skin. Left-click a piece, click a skin, and the skin is drawn on you. Click the worn skin again to take it off. Undress all empties everything.
The three modes#
behaviour.mode decides where a piece's skin comes from:
| Mode | Where it comes from | What it implies |
|---|---|---|
item | Only what a skin item wrote onto the armour. | The skin is traded, dropped and lost with the piece. No wardrobe, no database. |
wardrobe | Only what the player picked in /wardrobe. | It follows the player and lands on whatever they equip. Skin items do nothing. |
both | The armour's own skin, and the wardrobe for armour that carries none. | The default. |
In both the armour wins: a skinned piece is drawn with its own skin, and the wardrobe only covers bare pieces.
What the buttons do#
| Button | What it does |
|---|---|
| Undress all (slot 45) | Takes everything off. |
| Filter (slot 52) | Shows only the skins the player owns. Remembered like the tab. |
| Close (slot 49) | Closes the menu. |
| Crate (slot 53) | Opens the crate; shows the keys held and skins collected. |
| Page buttons (slots 48 and 50) | Turn the skin grid. |
| Click | On | Result |
|---|---|---|
| Left | An armour row | Focuses it: the grid now dresses that piece. |
| Right | An armour row | Clears that piece. |
| Left | The Full set row | Focuses every piece at once. |
| Right | The Full set row | Clears the whole wardrobe. |
| Any click | A skin | Wears it on the focus, or takes it off when it is already worn. |
| Any click | A skin for sale | Asks to confirm, charges the price and unlocks it. See Buying with currency. |
With the full set focused, a skin is applied to every piece the player may wear it on, so a rank that owns one piece of a skin still gets that piece rather than being refused.
Going further#
Change the look of the menu by editing lang/<language>/menus/wardrobe.yml (see Menus). Where the server's menu style is SCREEN, /wardrobe opens as a native screen (screens/wardrobe.html, with the crate and its reels) with a real body in a window that tries on the skin under the cursor. A screen that fails to load falls back to the chest menu.
Clearing a wardrobe hands out no item, because none was ever consumed. Skin items and removers belong to item and both.
Technical reference#
For people who edit the menu file.
Slots and lists of the menu
| Section | Slots | What it holds |
|---|---|---|
targets | 2,3,4,5,6 | What is being dressed: the full set, then helmet, chestplate, leggings and boots. |
skins | 10-16,19-25,28-34,37-43 | Every skin, paged with the buttons at slots 48 and 50. |
Undress all sits at slot 45 and takes everything off; Filter at 52 shows only the skins the
player owns (remembered like the tab); Close at 49; Crate at 53 opens
the crate and shows the keys the player holds and how many skins they
have collected.
Each armour row is drawn in the leather piece of its own slot, tinted with the skin worn there, so the top of the screen is what the player currently looks like. A grid row is drawn in the piece being dressed, so the skin is previewed where it is going to end up; a skin that does not fit the focused piece is drawn in a piece it does fit.
Templates of the wardrobe menu
| Section | Template | Used when |
|---|---|---|
targets | item_template | An armour slot that is not focused. |
focused_template | The armour slot being dressed. | |
set_template | The full-set row, not focused. | |
focused_set_template | The full-set row while it is focused. | |
skins | item_template | A skin the player may use and that fits. |
selected_template | The skin worn on the focused piece — or on every piece the skin fits, with the set focused. | |
unsupported_template | A skin whose pieces do not include the focused slot. | |
no_permissions_template | A skin the player does not own. | |
purchasable_template | A skin the player does not own that the shop sells, while shop.enabled is on. |
item_template is the plain state and must stay first in each list. The locked and unsupported rows
carry no action of their own: clicking one does nothing. A player owns a skin through its node or an
unlock, from the crate or the shop.
Wardrobe placeholders
These are the wardrobe's own tokens, filled in while the screen is drawn. They are not PlaceholderAPI placeholders and only work inside this file.
The targets list holds two kinds of row — the full-set row first, then one row per piece — and each
kind carries its own tokens.
| Placeholder | Where | What it draws |
|---|---|---|
%target% | targets | What the row dresses: a piece key, or set on the full-set row. |
%target_name% | targets | Its name from wardrobe: full-set, or the piece's own name. |
%dressed% | targets, full-set row | How many of the four pieces carry a skin. |
%pieces% | targets, full-set row | How many pieces there are in total — four. |
%piece% | targets, piece rows | The piece's key: helmet, chestplate, leggings or boots. |
%piece_material% | targets, piece rows | The leather material of that slot, to draw the row with. |
%skin_name% | targets, piece rows | The skin worn on that piece, or wardrobe.empty. |
%skin_color% | targets, piece rows | That skin's hex colour, or undyed leather when it has none. |
%skin_trim_pattern% | targets, piece rows | That skin's trim pattern, empty when it has no trim. |
%skin_trim_material% | targets, piece rows | That skin's trim metal, empty when it has no trim. |
%skin_id% | skins | The skin's id. |
%skin_name% | skins | Its display name. |
%skin_icon% | skins | Its icon, or the default skin item's material. |
%skin_preview% | skins | The armor piece it is previewed in — the one being dressed when the skin fits it. |
%skin_color% | skins | Its hex colour, or undyed leather when it has none. |
%skin_trim_pattern% | skins | Its trim pattern, empty when it has no trim. |
%skin_trim_material% | skins | Its trim metal, empty when it has no trim. |
%skin_pieces% | skins | The pieces it fits. |
%skin_worn% | skins | The pieces the player is wearing it on, empty when none. |
%skin_worn_name% | skins | The same, but wardrobe.empty when none. |
%price% | skins, purchasable_template | The price, written the way its currency writes it. |
%keys% | anywhere | The crate keys the player holds. |
%unlocked_count% | anywhere | How many skins they own, by unlock or permission. |
%catalogue_count% | anywhere | How many skins the server declares. |
Menu actions
| Action | What it does |
|---|---|
armorskin:wardrobe | Opens the wardrobe menu.style names, after checking exyliaarmorskin.wardrobe. |
armorskin:focus <target> | Dresses one piece, or set for all four. |
armorskin:wear <skin> | Wears a skin on the focus, or takes it off when it is already worn. |
armorskin:clear <target> | Clears one piece, or set for the whole wardrobe. |
armorskin:buy <skin> | Buys a locked skin with currency, then reopens the wardrobe on the same focus. Needs exyliaarmorskin.buy. |
armorskin:crate | Opens the crate. |
armorskin:equip <skin> | Wears a skin on every piece the player may, from outside the wardrobe: what a crate reel's winner does when clicked. |
Wording in messages.yml
The few strings one template draws for every row live under wardrobe in messages.yml:
wardrobe:
full-set: "{primary}&lFULL SET"
helmet: "{primary}&lHELMET"
chestplate: "{primary}&lCHESTPLATE"
leggings: "{primary}&lLEGGINGS"
boots: "{primary}&lBOOTS"
piece-names:
helmet: "Helmet"
chestplate: "Chestplate"
leggings: "Leggings"
boots: "Boots"
empty: "{muted}Nothing"piece-names is how a piece is written inside a sentence or a list, such as %skin_pieces%.
Where the wardrobe is stored
One row per player in armorskin_wardrobe: the uuid, and one column per piece holding a skin id.
Reads never block — a wardrobe still coming back from the database answers "no skin yet", and the
player is redrawn as soon as it lands.
The table is classified for ExyliaLib, so /exylialib resetplayer <player> ExyliaArmorSkin and
/exylialib wipe clear it along with the crate's keys and unlocks. See
ExyliaLib commands.
Clearing a wardrobe hands out no item, because none was ever consumed: a wardrobe choice is a row,
not an item. Skin items and removers belong to item and both.
Something missing on this page? Tell us on Discord