Permissions
The nodes the plugin declares, the per-feature nodes that turn a feature into a rank perk, what admin and bypass really let through, skipping the teleport countdown, and the per-player limits.
Plugin nodes#
| Permission | Who has it | What it allows |
|---|---|---|
exyliaprotections.use | Everyone | Own protections and open /protections. |
exyliaprotections.select | Everyone | Protect land by selecting two corners. |
exyliaprotections.admin | Admins (op) | Manage every protection, tier and cleanup, and run /protectionsadmin. |
exyliaprotections.bypass | Nobody until granted | Build, open and enter any protection. Operators do not get it unless you grant it. |
exyliaprotections.bypass.warmup | Admins (op) | Teleport home, to warps and to plots at once, with no countdown or cooldown. |
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.
Feature nodes#
Every player feature has a node of its own, held by everybody by default. To make one a rank perk, deny it to
the default group and grant it to the rank. A player without the node is told "Your rank does not include
that feature." (feature-locked in the messages file). The feature must still be on under submodules, and
the role permission on that protection still applies.
| Permission | Who has it | What it allows |
|---|---|---|
exyliaprotections.home | Everyone | Teleport to a protection's home. |
exyliaprotections.sethome | Everyone | Move a protection's home to where the player stands. |
exyliaprotections.rename | Everyone | Rename a protection. |
exyliaprotections.greeting | Everyone | Set a protection's enter and leave messages. |
exyliaprotections.hide | Everyone | Hide a protection's core. |
exyliaprotections.move | Everyone | Move a protection's core. |
exyliaprotections.show | Everyone | Draw a protection's border. |
exyliaprotections.members.add | Everyone | Add players to a protection. Removing them never needs this. |
exyliaprotections.members.clan | Everyone | Add a whole clan to a protection. |
exyliaprotections.roles | Everyone | Create, edit and delete a protection's roles. |
exyliaprotections.flags | Everyone | Change a protection's flags. |
exyliaprotections.lock | Everyone | Lock and unlock a protection. |
exyliaprotections.ban | Everyone | Ban players from a protection. |
exyliaprotections.logs | Everyone | Read a protection's logs. |
exyliaprotections.bank.deposit | Everyone | Put money into a protection's bank. Taking it out never needs this. |
exyliaprotections.market.buy | Everyone | Browse and buy protections on the market. |
exyliaprotections.market.sell | Everyone | List a protection for sale. Taking it off sale never needs this. |
exyliaprotections.transfer | Everyone | Give a protection to another player. |
exyliaprotections.rent.take | Everyone | Rent somebody else's land. |
exyliaprotections.rent.offer | Everyone | Offer land for rent. Withdrawing an offer or renewing a rent never needs this. |
exyliaprotections.subregions | Everyone | Create and manage plots inside a protection. |
exyliaprotections.upgrade | Everyone | Upgrade a protection to its next level. |
exyliaprotections.warp.visit | Everyone | Browse, visit and rate public warps. |
exyliaprotections.warp.manage | Everyone | Open, move and edit a protection's public warp. |
exyliaprotections.perks | Everyone | Turn a protection's unlocked perks on and off. |
exyliaprotections.environment | Everyone | Change a protection's time and weather. |
Taking land back never needs one of these: deleting a protection, paying upkeep, renewing a rent, withdrawing from the bank, taking a protection off sale, withdrawing a rent offer, removing members and unbanning keep working after a rank runs out.
exyliaprotections.lock is checked by /protections lock only. The Lock button in the Access section asks
for the toggle-lock role permission and not for this node.
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, 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.
The node only counts when it is set on the player, and since 1.0.2 it defaults to nobody: operators are bound by protections like anybody else, so they can test their own land. Grant it to whoever must bypass:
/lp user Notch permission set exyliaprotections.bypass trueexyliaprotections.bypass defaulted to op, and a default counts as set, so every operator bypassed every
protection out of the box.
Per-player limits#
| Permission | Who has it | What it allows |
|---|---|---|
exyliaprotections.limit.<n> | Nobody until granted | The most protections the player may own in total. The highest number held wins; without one, settings.default-limit in config.yml applies. |
exyliaprotections.limit.<tier>.<n> | Nobody until granted | The most protections of one tier. The highest number held wins; 0 means none. Without one, the tier's own limit applies. |
exyliaprotections.select.area.<n> | Nobody until granted | The largest area, in blocks, the player may protect by selection. Without one, selection.max-area applies. |
For each prefix the highest number a player holds wins, and replaces the config.yml value, lower or higher.
exyliaprotections.limit.0 is a limit like any other: that player may own none. A node whose end is not a
number is ignored. These nodes are not declared in plugin.yml; grant them by name.
settings.world-limits still caps how many a player may own per world, with no node of its own. See
Creating protections.
Permissions named in config.yml#
| Where | What it gates | Default |
|---|---|---|
tiers.<id>.permission | Placing a core of that tier, protecting land by selection when it is selection.tier (since 1.0.2), 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#
Since 1.0.2 the old exyliasurvivalcore.protections* nodes, and the exyliasurvivalcore.protections.limit.<n>
limits, are no longer declared or read. Grant the exyliaprotections.* names instead.
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 trueLetting the VIP rank own up to three large protections and select up to 40,000 blocks:
/lp group vip permission set exyliaprotections.limit.large.3 true
/lp group vip permission set exyliaprotections.select.area.40000 trueMaking moving the home a VIP perk:
/lp group default permission set exyliaprotections.sethome false
/lp group vip permission set exyliaprotections.sethome trueKeeping new players off selections on a server that turned selection.enabled on:
/lp group default permission set exyliaprotections.select falseHanding the admin menu to moderators who are not operators, without letting them build anywhere:
/lp group moderator permission set exyliaprotections.admin trueSomething missing on this page? Tell us on Discord