Content generated with AI — it may contain mistakes.

ExyliaArmorSkin/ReferenceUpdated in v1.4.1

Permissions

Every ExyliaArmorSkin permission, how to give a skin to a rank, sell half a skin, and turn the shop and crate into rank perks.

Page 11 of 213 min read

Out of the box every player can open the wardrobe, buy skins and open the crate, and only operators own skins. Use this page to give skins to ranks and to turn features into perks.

All permissions#

PermissionWho has itWhat it allows
exyliaarmorskin.wardrobeEveryoneOpen the wardrobe: /wardrobe, /wardrobe 3d, /wardrobe classic.
exyliaarmorskin.buyEveryoneBuy locked skins in the wardrobe shop.
exyliaarmorskin.crateEveryoneOpen the crate: its wardrobe button, /wardrobe crate and crate blocks.
exyliaarmorskin.crate.multi.<n>Nobody until grantedOpen up to <n> crates at once instead of crate.max-at-once (seven at most). The highest one a player holds wins.
exyliaarmorskin.adminAdmins (op)Every /armorskinsadmin subcommand.
exyliaarmorskin.skin.*Admins (op)Own every skin, on every piece.
exyliaarmorskin.skin.<id>Nobody until grantedOwn that skin on all four pieces, for example exyliaarmorskin.skin.galaxy.
exyliaarmorskin.skin.<id>.<piece>Nobody until grantedOwn that skin on one piece only: helmet, chestplate, leggings or boots.

Every player starts with exyliaarmorskin.wardrobe, exyliaarmorskin.buy and exyliaarmorskin.crate. An operator owns every skin (exyliaarmorskin.skin.*). Everybody else owns none until you grant a node, they win one from the crate or they buy one. Taking a skin off never needs a permission.

The skin node comes from the skin's id, lowercased: the skin galaxy is exyliaarmorskin.skin.galaxy. Add a skin to skins.yml and its node exists.

Give a skin to a rank#

With LuckPerms:

/lp group vip permission set exyliaarmorskin.skin.galaxy true
/lp group mvp permission set exyliaarmorskin.skin.* true

Players of that rank now own the skin. Rank changes take effect the next time the player's armour is redrawn (equip, join, respawn, /armorskinsadmin reload); /armorskinsadmin refresh <player> makes it immediate.

Sell half a skin#

Each piece has its own node, exyliaarmorskin.skin.<id>.<piece> with helmet, chestplate, leggings or boots. The whole-skin node covers all four, a piece node covers one.

/lp group vip permission set exyliaarmorskin.skin.celestial.helmet true

In the wardrobe the player is offered the skin on that piece, and dressing the full set dresses only the pieces they may wear. With the shop on, the rest of the skin is offered for sale.

Make features rank perks#

wardrobe, buy and crate are held by everybody, so a feature becomes a perk by denying it to the default group and granting it to the rank. A player whose rank lacks one is told feature-locked.

/lp group default permission set exyliaarmorskin.buy false
/lp group vip     permission set exyliaarmorskin.buy true
/lp group vip     permission set exyliaarmorskin.crate.multi.7 true

exyliaarmorskin.crate.multi.<n> lets a rank open up to <n> crates at once (the highest node a player holds wins, seven at most) instead of crate.max-at-once.

Two ways to own a skin#

WayCoversEnds
A nodeThe skin, or one piece of it.When the rank or the node goes.
An unlockThe whole skin, every piece it fits. Written by the crate, the shop or /armorskinsadmin unlocks grant.Only with unlocks revoke, or ExyliaLib's /exylialib resetplayer. It outlives any rank.

Either is enough. Both the wardrobe and the visibility check ask for both.

Why a player does not see their skin#

By default (behaviour.hide-without-permission: true in config.yml) a player who wears a skin they own neither by node nor by unlock is shown their real armour, to themselves and to everyone else. The skin id stays on the item, and the look returns the day they own it again.

Applying a skin item never asks for a permission. So to sell skins as plain items, either hand an unlock with the item, grant the node, or set hide-without-permission: false and the item itself becomes the permission.

Technical details
  • Ownership is checked in the wardrobe (wearing needs a node or unlock), and when a piece is drawn (only with hide-without-permission). Applying an item is never checked.
  • The check runs on equip, join, respawn, refresh and reload.
  • /armorskinsadmin give, unlocks grant and the API's apply() are never gated: they are the tools you use to grant skins. The API's select goes through the wardrobe and is refused for a skin the player does not own.
  • consume-skin-item: true (default) makes a skin item single use. Turn it off and one item skins any number of pieces.

Something missing on this page? Tell us on Discord