Permissions
The five kinds of node, and how a category or a rarity is sold as one line.
The nodes
| Permission | Grants |
|---|---|
exyliakilleffect.command.killeffect | /killeffect and everything under it. |
exyliakilleffect.admin | Every subcommand of /killeffectsadmin. |
exyliakilleffect.effect.<id> | One effect, by its id in lowercase. |
exyliakilleffect.effect.* | Every effect. |
exyliakilleffect.category.<id> | Every effect in that category. |
exyliakilleffect.tier.<id> | Every effect of that rarity. |
An effect is granted if any of the four effect nodes applies: its own, the wildcard, its category's or its rarity's. A permission is only half of owning one — the other half is winning it out of the crate, which is written to the player's row instead.
The id is the node
There is no permission key in effects.yml. The node is derived from the key, lowercased:
GRIDDY → exyliakilleffect.effect.griddy
meme → exyliakilleffect.category.meme
legendary → exyliakilleffect.tier.legendaryCase 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 exyliakilleffect.command.killeffect true
/lp group vip permission set exyliakilleffect.category.meme true
/lp group mvp permission set exyliakilleffect.effect.griddy true
/lp group elite permission set exyliakilleffect.tier.legendary true
/lp group legend permission set exyliakilleffect.effect.* trueFive categories and four rarities are what make those nodes worth selling: "every Meme effect" or "every legendary" is one line instead of twenty.
Without exyliakilleffect.command.killeffect 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 kill. 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 weapon 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.
The node is asked for when a token is bound, never again. After that the effect belongs to the weapon: 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 weapon side is who can put one there.
Something missing on this page? Tell us on Discord