People and access

Who may do what inside a protection is decided by its roles. Members and clans are given a role, anybody else is a visitor, and single members can be given overrides on top of their role. How the land itself behaves for everybody — PvP, fire, mobs — is a set of flags.

All of it is edited from the protection's screen: People holds members, roles and bans, Access holds flags, the lock and the greeting. See Menus.

How a player's rights are decided

For anything a player does inside a protection, the first rule that answers wins:

1. A player with exyliaprotections.bypass set for them may do everything.
2. While the protection is raidable, its enemies may do what raids.raidable-permissions lists; while it is abandoned, so may everybody who is neither its owner nor a member.
3. The owner may do everything.
4. Inside a plot: a plot member's own override, then their role in the plot. A private plot refuses everybody else who lacks manage-subregions.
5. A personal override for that player, allow or deny.
6. The player's own role.
7. The role given to their clan.
8. The visitor role.

A player who is both a member and in a clan that was added uses their own role; the clan's role only counts for players without one. A tenant whose rent ran out counts as a visitor from that moment.

Members and clans

People → Members lists every member with their role and how many overrides they have, then every clan added.

All of it needs manage-members. The role prompt only offers roles whose every permission the player holds themselves: nobody but the owner hands out a permission they do not have. visitor is never offered. With level upgrades on, each level caps how many members and clans together a protection holds (upgrades.base-max-members, 8, before any upgrade).

A clan's role applies to every member of the clan, including players who join it later.

Roles

People → Roles lists every role with how many permissions it grants and how many members and clans hold it, visitor last. It needs manage-roles.

A role name is up to 16 of a-z, 0-9, - and _, cannot be owner and cannot repeat another role. visitor cannot be renamed or deleted.

New protections start with the roles section of config.yml:

roles:
  member:
    permissions: [break, place, containers, doors, redstone, buckets, animals, ride,
                  decorations, trade, leash, bank-deposit]
  trusted:
    permissions: [break, place, containers, doors, redstone, buckets, animals, ride,
                  decorations, trade, leash, manage-members, set-home, bank-deposit]
  visitor:
    permissions: []

Flag keys written into a role are ignored. Each protection keeps its own copy of its roles: editing this section changes new protections only.

Rules that protect the protection

• Toggling a role's permission needs manage-roles and holding that permission yourself.
• Nobody but the owner edits the role they hold themselves, or their own overrides, role or membership: "Only the owner can change your own access."
• The visitor role holds everybody who is not a member, so it can only be given the land permissions (break to leash below). Management permissions are refused for it, and never granted by it even if written into the file by hand.
• Opening the protection's screen and teleporting home need membership. Deleting, picking up the core, selling, giving away, upgrading, merging and turning perks on are the owner's alone.

Role permissions

"Offered while" is when the permission appears on role and override screens. A permission whose feature is off is hidden, not removed: it comes back as it was when the feature is turned on. Hostile mobs are never protected, and players attacking players are decided by the pvp flag, not by a permission.

Overrides

An override sets one permission for one member, ignoring their role. Each click on a permission in a member's override screen moves it through role (follow the role) → allow → deny → back to role. The members list shows how many overrides each member has.

Overrides need manage-members, and changing one needs holding that permission yourself. They exist for players only, not for clans, and go when the member is removed. Plot members have overrides of their own inside their plot, set from the plot's screen.

Flags

A flag is the land's own switch. It applies to everybody inside, members or not. Access → Flags toggles them; it needs edit-flags.

Some rules hold whatever the flags say:

• Liquids never flow into a protection from outside it.
• Pistons never move a block into, out of or across a protection other than their own.
• Hoppers and hopper minecarts outside a protection never pull from a container inside it, and dispensers outside never fire into it.
• Falling blocks never land in a protection other than the one they fell from, and projectiles nobody shot (from a dispenser outside, for instance) change no block inside.
• Mobs never trample farmland inside a protection.

A player lighting a fire needs place. settings.deny-message-cooldown-millis (1500) is how long a player waits between two "This land is protected." messages.

Bans

With submodules.bans, a player with manage-bans bans somebody from the protection. A banned player is pushed just past the nearest border and cannot come back: walking, riding, ender pearls, chorus fruit, commands, plugin teleports, spectating and portals into it are all stopped. Logging in or respawning inside pushes them out again.

People → Bans lists the bans still running with their reason, who banned and the time left; right-click one to lift it. Ban player asks two questions, then shows a summary before anything is written: the player's name, then "How long, and why?". The answer is a duration followed by an optional reason: 7d griefing, 2h, 30m spam, or permanent (also perm or forever) for a ban that never ends.

The same from chat, standing in the protection:

/protections ban <player> [duration] [reason]
/protections unban <player>

With no duration at all the ban is permanent; a reason needs a duration before it. A reason is plain text of up to bans.reason-max-length (64) characters: colours and placeholders are removed.

These players cannot be banned: the owner, members (clan members included) and tenants — "is a member. Remove them first." — and, while online, anybody with the admin permission or the bypass.

A ban holds even while the protection is open to visitors. A raid or an abandonment opens the land to everybody, whatever its bans and lock say. Turning submodules.bans off stops enforcing bans but keeps them; they apply again when it is turned back on.

Lock

With submodules.lock, a player with toggle-lock locks the protection so only the owner, members, tenants and plot members may enter. Locking is turning the visitor-entry flag off, from Access → Lock or /protections lock standing inside. Visitors already inside are pushed out.

Greetings and farewells

With submodules.enter-leave, walking into a protection shows a title and walking out shows an action bar. A player with rename sets the protection's own lines from Access → Greeting & farewell:

Both are plain text, cut to enter-leave.message-max-length (64) characters. Without one of its own a protection uses enter-default ("Owned by %owner%") and leave-default ("« You left %name%") from messages.yml.

The titles themselves are the enter-leave section of messages.yml: enter-title (%name% over %message%), enter-actionbar (empty), leave-title (empty) and leave-actionbar (%message%). Placeholders: %name%, %owner% and %message%, which is the greeting or farewell. Stepping straight from one protection into another only greets. Stepping into a plot shows enter-subregion in the action bar. With ExyliaSurvivalCore installed, players can mute all of it with its protection-messages setting.

Audit log

With submodules.logs, every protection keeps a history. A player with view-logs opens it from Defense → Logs or /protections logs standing inside. Left-click Filter by action cycles through the actions, right-click clears it; left-click Filter by player asks for a name, right-click clears it.

break, place and container record only what actually happened; everything else is a change made through a screen or a command. Each entry keeps who, what (up to 128 characters), where, on which server and when.

Bypass and admins

The bypass only counts when the permission is set for the player, by a permissions plugin or by plugin.yml's default. That default gives both permissions to operators, so operators bypass every protection. To make an operator play by the rules, set exyliaprotections.bypass to false for them in your permissions plugin. The old names exyliasurvivalcore.protections.admin and exyliasurvivalcore.protections.bypass grant the same.