Content generated with AI — it may contain mistakes.

Reference

Permissions

The kinds of node, how a category is sold as one line, and the effects a crate hands over instead.

The nodes

PermissionGrants
exyliarrows.command.arrows/arrows and everything under it.
exyliarrows.adminEvery subcommand of /arrowsadmin.
exyliarrows.effect.<id>One effect, by its id in lowercase.
exyliarrows.effect.*Every effect.
exyliarrows.category.<id>Every effect in that category.
exyliarrows.tier.<id>Every effect of that rarity.

An effect is owned if any of the four effect nodes applies: its own, the wildcard, its category's, or its rarity's — or if the player won it from the crate.

The id is the node

There is no permission key in effects.yml. The node is derived from the key, lowercased:

EMBER_TRAIL  →  exyliarrows.effect.ember_trail
ember        →  exyliarrows.category.ember
legendary    →  exyliarrows.tier.legendary

Case is not part of it, so recapitalising a key changes nothing. Renaming one changes everything: it is a different node, and everybody who had the old one loses the effect.

Selling it

/lp group default permission set exyliarrows.command.arrows true
/lp group vip     permission set exyliarrows.category.ember true
/lp group mvp     permission set exyliarrows.effect.ember_trail true
/lp group elite   permission set exyliarrows.tier.legendary true
/lp group legend  permission set exyliarrows.effect.* true

Six categories of twenty is what makes a category node worth selling: "every Ember effect" is one line instead of twenty.

Give the menu away

Without exyliarrows.command.arrows the catalogue cannot be opened at all. A player who cannot see what is for sale cannot want it.

What the node is checked for

Wearing

Choosing an effect in the menu without its node is refused with no-permission. Governed by behaviour.require-permission.

Playing what the menu chose

The choice is re-checked at the moment of the shot. One that no longer holds is taken off there and then, rather than left sitting in the menu until the next relog.

Binding a token

Dropping a token onto a bow without the effect's node is refused, and nothing is consumed.

Being drawn

behaviour.hide-without-permission decides whether a locked effect is hidden in the menu or shown locked. Either way it can be previewed, and on the favourites tab it is always shown.

What the crate hands over is not a node

An effect won from the crate is written onto the player's own row, so it survives the rank they never had and validate never takes it off. Rarity nodes and the crate are two ways of selling the same shelf: one is rented with a rank, the other is kept. See Rarities and the crate.

A bound bow is not re-checked

The node is asked for when a token is bound, never again. After that the effect belongs to the bow: it plays for whoever is holding it, including a player who never owned the node — which is the point of an effect you can trade. What permissions govern on the bow side is who can put one there.

Something missing on this page? Tell us on Discord