Reference

Permissions

The four nodes the plugin declares, what admin and bypass really let through, how many protections a player may own, and the ExyliaSurvivalCore names that still work.

Plugin nodes

Permission	Default	What it gates
`exyliaprotections.use`	everyone	`/protections` and every subcommand outside `admin`, and with them the menus they open.
`exyliaprotections.select`	everyone	Protecting land by selecting two corners, when `selection.enabled` is on. Without it the hub hides the option.
`exyliaprotections.admin`	operators	The `admin` subcommands, the admin menu and every action in it. On every protection it also counts as the owner and as holding every role permission.
`exyliaprotections.bypass`	operators	Building, using and entering anything inside any protection.

exyliaprotections.use gates commands only. Placing a core a player already holds needs nothing but the tier's own permission, when the tier names one.

What admin lets through

exyliaprotections.admin is a management node, not a building one:

Every subcommand and menu button that asks for Owner or a role permission passes: selling, transferring, upgrading, merging, banking, editing members, roles and flags of anybody's protection.
Entering is always allowed, whatever the protection's lock or bans say.
A player holding it cannot be banned from a protection, and may edit their own entry in a member list.
It does not let the player break, place or open anything in someone else's land. That is exyliaprotections.bypass.

What bypass lets through

A player who bypasses passes every check inside a protection: blocks, containers, doors, entities, entry, locks and bans. They also act in worlds whose protections have not finished loading after a restart, where everybody else is told to wait.

Operators bypass every protection

The code only honours exyliaprotections.bypass when the node is set on the player, so that holding every permission is not enough. But the node defaults to op, and a default counts as set: every operator bypasses protections out of the box. To keep an operator bound by protections, set the node to false on them:

/lp user Notch permission set exyliaprotections.bypass false

How many protections a player may own

Permission	What it sets
`exyliaprotections.limit.<n>`	The player may own `n` protections.
`exyliasurvivalcore.protections.limit.<n>`	The same, under its ExyliaSurvivalCore name. Still read.

The highest number among both prefixes wins. A player with none of them — or whose highest is 0 — gets settings.default-limit from config.yml (3). A node whose end is not a number is ignored.

Two more limits stack on top, from config.yml: tiers.<id>.limit caps how many of one tier a player may own, and settings.world-limits caps how many they may own per world. See Creating protections.

Permissions named in config.yml

Where	What it gates	Default
`tiers.<id>.permission`	Placing a core of that tier, buying it from the shop and buying a protection of that tier on the market or receiving it by transfer.	Empty: anybody.
`upgrades.tiers.<tier>.levels.<n>.permission`	Upgrading to that level.	Empty: anybody.

They can be any node, such as rank.vip.

ExyliaSurvivalCore names

What staff were granted while protections lived in ExyliaSurvivalCore keeps working. ExyliaProtections declares the old nodes too, each with its new node as a child:

Old node	Default	Grants
`exyliasurvivalcore.protections`	nobody	`exyliaprotections.use`
`exyliasurvivalcore.protections.select`	nobody	`exyliaprotections.select`
`exyliasurvivalcore.protections.admin`	operators	`exyliaprotections.admin`
`exyliasurvivalcore.protections.bypass`	operators	`exyliaprotections.bypass`

New setups should grant the exyliaprotections.* names.

Role permissions are not these

What a member may do inside one protection — break, containers, manage-members, bank-withdraw and the rest — is a role permission, set per protection from its menu. They are not server permissions and no permissions plugin grants them. See People and access.

Examples

Letting the VIP rank own six protections:

/lp group vip permission set exyliaprotections.limit.6 true

Turning selection off for new players while keeping cores:

/lp group default permission set exyliaprotections.select false

Handing the admin menu to moderators who are not operators, without letting them build anywhere:

/lp group moderator permission set exyliaprotections.admin true

Something missing on this page? Tell us on Discord