Commands
The wardrobe command a player types, and the seven admin subcommands.
The player command
| Command | Permission | What it does |
|---|---|---|
/wardrobe | exyliaarmorskin.wardrobe | Opens the wardrobe. Alias: /armorskins. |
That is the only command a player needs. Skin items need no command at all: they are dragged onto armour.
With behaviour.mode: item a wardrobe choice would never be read, so the command answers
wardrobe-disabled instead of opening a screen that changes nothing.
The admin command
/armorskinsadmin, alias /armorskinadmin. Everything under it needs exyliaarmorskin.admin.
| Command | What it does |
|---|---|
give <player> <skin> [1-64] | Gives the skin item for <skin>. |
remover <player> [1-64] | Gives skin removers. |
list | Lists every registered skin. |
refresh [player] | Rebuilds and re-sends what a player is shown wearing. |
wardrobe open <player> | Opens somebody's wardrobe for them. |
wardrobe clear <player> | Empties their wardrobe: every slot back to their real armour. |
reload | Re-reads this plugin's files and redraws everyone. |
give
<skin> tab-completes from the registry, and an unknown id answers unknown-skin to whoever typed
the command. [amount] is 1 to 64 and defaults to 1.
give never checks the skin's own permission: it hands the item to anybody. Whether the player can
then use it is exyliaarmorskin.skin.<id> and the two switches in
Permissions.
The item is added to the target's inventory; anything that does not fit is dropped at their feet. The
given message — with %skin% and %amount% — is sent to the target, not to the sender, so
giving from console tells the player and says nothing back.
remover
The same shape without a skin id. The given-remover message, carrying %amount%, also goes to the
target.
list
Prints list-header, then one list-entry per skin with %id%, %skin% and %pieces% filled in.
With nothing registered it prints list-empty instead. The list covers skins from skins.yml and
skins another plugin registered through the API.
refresh
| Typed by | With a player | What happens |
|---|---|---|
| A player | no | Only that player is refreshed. |
| A player | yes | Only the named player is refreshed. |
| Console | no | Everyone online is refreshed. |
| Console | yes | Only the named player is refreshed. |
Refreshing re-reads the armour the player is actually wearing, rebuilds every visual from it and re-sends both their inventory and their equipment to everyone tracking them. It is also what applies a permission you just granted or revoked, because that is checked while the visual is rebuilt. It plays no effects and touches no file — it is the answer to "another plugin changed this item behind my back".
wardrobe open and wardrobe clear
open shows the target their own wardrobe — the screen belongs to them, not to the admin who opened
it. clear empties every slot and answers wardrobe-cleared; the armour itself is untouched, since
a wardrobe was never written to it.
reload
Runs one step, configs, which:
Re-reads every file
config.yml, animations.yml, skins.yml and menus/wardrobe.yml.
Re-applies the message prefix
So %prefix% matches the rest of the ecosystem again.
Rebuilds the skins
Cached trims are dropped, animations are rebuilt from animations.yml, and the file's skins
replace the previous file's skins. Skins registered through the API are left alone.
Redraws everyone online
Every player has their visuals rebuilt and re-sent, silently — no equip effects are played.
The step reports success or failure to whoever ran it. It does not reload ExyliaLib; /exylialib reload is what does that.
Nothing is removed from anybody: the armour keeps its id, the wardrobe keeps its rows, and the visual is simply rebuilt. A player wearing an animated skin sees the new speed or colour on the next frame.
Something missing on this page? Tell us on Discord