Reference

Permissions

Every node the plugin declares, the per-feature and per-crate nodes that turn features into rank perks, and the multi-open limit per rank.

Permission	Default	What it gates
`exyliacrates.use`	everyone	`/crates` and its subcommands, a click on the crate list, and Your openings on a contents screen.
`exyliacrates.admin`	operators	`/cratesadmin` and every subcommand, every staff screen and button, the crate wand, the Server history button and the Settings screen.
`exyliacrates.open.remote`	everyone	Opening a crate away from its block: `/crates open` and the crate item on the contents screen. Also needs `exyliacrates.use`.
`exyliacrates.preview`	everyone	Looking inside a crate: left-clicking its block, the crate list and `/crates preview`.
`exyliacrates.history`	everyone	Reading your own history: `/crates history` and Your openings.
`exyliacrates.multiopen`	everyone	Opening several at once: sneak + right-click on the block, shift-click on the contents screen, `/crates open <crate> true`.
`exyliacrates.crate.*`	everyone	Opening every crate, unless `exyliacrates.crate.<id>` is set for one.
`exyliacrates.crate.<id>`	not declared	Opening one crate, by its id in lower case. When set, it wins over `crate.*`.
`exyliacrates.multiopen.<n>`	not declared	Most openings one multi-open pays for. See below.

A player without a feature's node is told "Your rank does not include that feature." (feature-locked in messages.yml).

Features as rank perks

Every player node above is held by everybody by default, so nothing changes until you take one away. To make a feature a rank perk, deny it to the default group and grant it to the rank:

lp group default permission set exyliacrates.multiopen false
lp group vip permission set exyliacrates.multiopen true

Opening a crate by right-clicking its block needs only the crate's own node (and exyliacrates.multiopen when sneaking); it does not need exyliacrates.use. Opening it from anywhere else needs exyliacrates.use and exyliacrates.open.remote as well, so denying open.remote keeps every crate to its block while players keep /crates, previews and their history.

One crate at a time

exyliacrates.crate.<id> decides for one crate, at the block and away from it alike. When it is not set for a player, exyliacrates.crate.* decides, and everybody holds that.

Lock one crate: deny exyliacrates.crate.vip to the default group, grant it to the rank.
Open only some: deny exyliacrates.crate.*, then grant exyliacrates.crate.<id> for each crate allowed.

Previews are not gated per crate: a player can still look inside a crate they may not open.

Multi-open limit per rank

exyliacrates.multiopen.<n> sets how many openings one multi-open pays for. The highest number a player holds wins and replaces settings.max-multi-open (10) for them, so a node lower than the setting lowers their limit. Without any such node, the setting applies. Multi-open itself still needs exyliacrates.multiopen.

lp group vip permission set exyliacrates.multiopen.25 true

Limiting who can win what

Per-reward permissions and conditions, set in the reward editor, take a reward out of the draw for players who lack them. The contents screen shows those rewards as Locked and works the odds out over what is left. See Rewards and rarities.

ExyliaSurvivalCore nodes

exyliasurvivalcore.crates.use and exyliasurvivalcore.crates.admin, which gated the crates of ExyliaSurvivalCore, are not checked by this plugin. Grant exyliacrates.use and exyliacrates.admin instead.

Something missing on this page? Tell us on Discord