Content generated with AI — it may contain mistakes.

ExyliaShields/ReferenceUpdated in v1.5.0

Permissions

Every ExyliaShields permission, and how to turn slots, layers, colours and features into rank perks.

Page 10 of 202 min read

Players can use ExyliaShields without any setup: they open /shields, get one slot, and can design with whatever patterns and colours they have unlocked. Only staff get /shieldsadmin. Use this page to sell more.

All permissions#

PermissionWho has itWhat it allows
exyliashields.command.shieldsEveryoneOpen `/shields` and the 3D menus, and design, buy and wear shields.
exyliashields.browserEveryoneBrowse and import the community's designs.
exyliashields.crateEveryoneOpen the shield crate: its button, `/shields crate` and a bound crate block.
exyliashields.useEveryoneKeep a design on the shield while `force_system` is on in `config.yml`.
exyliashields.adminAdmins (op)Open `/shieldsadmin` and every admin command.
exyliashields.pattern.*Admins (op)Use every pattern.
exyliashields.pattern.<id>Admins (op)Use one pattern. The id is the key in `shields.yml`, for example `exyliashields.pattern.creeper`. Not declared in plugin.yml: it works as soon as you grant it.
exyliashields.color.*Admins (op)Use every colour.
exyliashields.color.<id>Admins (op)Use one colour, for example `exyliashields.color.red`. Not declared in plugin.yml.
exyliashields.max_slots.<n>Nobody until grantedShield slots a player has. The highest number held wins; one slot without any.
exyliashields.layers.<n>Nobody until grantedLayers a design may hold. The highest number held wins; `max_layers` from `shields.yml` without any.
exyliashields.crate.multi.<n>Nobody until grantedCrates opened in one go. The highest number held wins; `crate.max-at-once` without any; seven at most.

For the three numbered nodes (max_slots, layers, crate.multi) the highest number a player holds wins, so a rank upgrade never has to revoke the lower one. A pattern or colour a player won from the crate or bought from the shop is theirs without the node, and it stays after a rank runs out.

Make a feature a rank perk#

Players hold every player permission by default. To make one a perk, deny it to the default group and grant it to the rank. With LuckPerms:

/lp group default permission set exyliashields.browser false
/lp group vip permission set exyliashields.browser true
/lp group vip permission set exyliashields.max_slots.5 true
/lp group vip permission set exyliashields.layers.8 true
/lp group vip permission set exyliashields.crate.multi.7 true
/lp group vip permission set exyliashields.color.* true
/lp group mvp permission set exyliashields.pattern.* true

A player refused by a feature node sees "Your rank does not include this." (no_access in messages.yml). Resetting or deleting a design and removing a layer never need a node, so a lapsed rank never traps a player with a design they cannot take off.

exyliashields.use strips designs

With force_system: true (the default) a player without exyliashields.use has their design removed whenever they equip a shield. That is how an expired rank stops showing a design it no longer owns. Everybody holds the node by default, so deny it only to a group that should not keep designs, or set force_system: false in config.yml.

Something missing on this page? Tell us on Discord