Content generated with AI — it may contain mistakes.

ExyliaProtections/GuidesUpdated in v1.1.0

People and access

Add friends to a protection, give them roles, set flags, ban and lock, and see who did what.

Page 5 of 2518 min read

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.

Before you start#

You need a protection, see Creating protections. Open its screen by right-clicking its core, or with /protections → My protections and the protection. Colours and texts of the screens are explained in Menus and Messages and languages.

Add a friend#

Open People

On the protection's screen click People, then Members.

Add the player

Click Add player and type their name in chat. They must have played on the network before.

Pick a role

Choose member (build, open chests and doors, use animals) or trusted (the same, plus add members and set the home). To make a role of your own see Roles.

Standing inside the protection you can instead run /protections add <player> [role].

Check that it works#

Ask the friend to break a block inside: it works. Ask somebody who is not a member: they get "This land is protected." Then open Access → Flags and switch a flag to see the land change, for example pvp.

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.

ClickWhat it does
Add playerAsks for a name. The player must have played on the network before. Then asks which role they get.
Add clanAsks for a clan tag, then the role. Needs a clan plugin; without one, "There is no clan plugin on this server."
Left-click a member or clanChanges their role.
Shift + left-click a memberOpens their overrides. Clans have none.
Right-click a member or clanRemoves them, with their overrides, after a confirmation. A tenant cannot be removed while they rent.

The same from chat, standing in the protection:

/protections add <player> [role]
/protections remove <player>

Without a role, add gives the default member role when you may hand it out, otherwise the first role you may. remove takes the name the member was added under.

All of it needs manage-members. Adding players also needs exyliaprotections.members.add, and adding a clan exyliaprotections.members.clan; removing never needs a node. See Permissions. 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.

ClickWhat it does
Create roleAsks for a name and opens the new, empty role.
Left-click a roleOpens its permission switches.
Right-click a roleRenames it. Everybody holding it keeps it under the new name.
Shift + right-click a roleDeletes it after a confirmation. Everybody holding it — members, clans and plot members — stops being a member.

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.

Default roles in config.yml

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

yaml
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 and turning perks on are the owner's alone.

Role permissions#

Every role permission
PermissionWhat it allowsOffered while
breakBreak blocks, trample farmland (while crop-trample is on), damage minecarts and boats, break blocks with a projectilealways
placePlace blocks, edit signs, place boats, minecarts and armour stands, use spawn eggs, bone meal, flint and steel and fire charges, light fires, use clickable blocks that hold no inventory (crafting tables, anvils, beds…), let a portal formalways
containersOpen anything with an inventory (chests, barrels, furnaces, shulkers, hoppers…), lecterns and taking their book, jukeboxes, chiseled bookshelvesalways
doorsDoors, trapdoors and fence gatesalways
redstoneButtons, levers, repeaters, comparators, daylight detectors, note blocks, pressure plates and tripwires; arrows and thrown items on them count as the shooteralways
bucketsFill and empty bucketsalways
animalsHurt, feed, interact with and shear animals and other non-hostile mobs, pull them with a fishing rodalways
rideMount horses, boats and minecartsalways
decorationsPlace, break and use item frames, paintings and armour standsalways
tradeTrade with villagers and wandering tradersalways
leashLeash and unleash mobsalways
manage-membersAdd and remove members and clans, choose their role, set overridesalways
manage-rolesCreate, rename, delete and edit rolesalways
edit-flagsChange the flagsalways
renameRename the protection, edit its greeting and farewellalways
set-homeMove the home to where they stand, inside the protectionalways
manage-coreHide, show and move the corealways
manage-bansBan and unban playerssubmodules.bans
toggle-lockLock and unlocksubmodules.lock
view-logsRead the audit logsubmodules.logs
bank-deposit, bank-withdrawUse the banksubmodules.bank
manage-subregionsCreate, edit and delete plotssubmodules.subregions
manage-rentOffer the land and its plots for rentsubmodules.rent
manage-warpPublish and edit the public warpsubmodules.warps
edit-environmentChange the time and weather insidesubmodules.environment

"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.

FlagWhile it is off
pvpPlayers cannot hurt each other, with weapons, projectiles, harmful potions or clouds, or pull each other with a rod, when either of them stands in land with it off. With raids on, raids.siege-pvp lets enemies and defenders fight during a siege
mob-spawningNo natural spawns: natural, jockeys, patrols, reinforcements, village invasions, raids, traps. Spawners, eggs and breeding still work
explosionsExplosions break no blocks and no hanging decorations
fire-spreadFire does not spread or burn blocks, and nothing but flint and steel lights it
liquid-flowWater and lava do not flow
crop-growthCrops and plants do not grow
leaf-decayLeaves do not decay
visitor-entryNon-members cannot walk in: the protection is locked
mob-damageHostile mobs, and what they shoot, do not hurt players
fall-damagePlayers take no fall damage
hungerPlayers' food level does not drop; eating still fills it
mob-griefingEndermen, ravagers, withers, the dragon, zombies breaking doors and silverfish change no blocks
block-spreadGrass, mycelium, vines, mushrooms and sculk do not spread
snow-iceSnow does not fall or melt, ice does not form or melt. Snow golem trails and frost walker are left alone
crop-trampleNobody tramples farmland, players or mobs, members included. While on, a player still needs break
item-dropVisitors cannot drop items (and are told the land is protected)
item-pickupVisitors cannot pick items up
ender-pearlVisitors cannot land inside with an ender pearl or chorus fruit

The last ten were added in 1.0.2. item-drop, item-pickup and ender-pearl only bind visitors: the owner, members, the plot's own members and players with the bypass are never held back. An existing protection reads the new vanilla-like flags (mob-damage, fall-damage, hunger, block-spread, snow-ice, item-drop, item-pickup, ender-pearl) as on, so it behaves as it did before they existed; mob-griefing and crop-trample start off, which keeps mob griefing and trampling stopped as before.

Flags the server forces#

forced-flags in config.yml sets a flag to ALLOW or DENY for every protection and every plot, whatever their owners chose, for instance pvp: DENY everywhere. It is set by staff with /protectionsadmin flag <flag> <allow|deny|default> or from the admin hub; see Administration.

A forced flag shows its forced state on the flags screens with "» set by the server", and clicking it answers "<flag> is set by the server in every protection." The owner's own choice is kept and applies again once the flag is no longer forced. With visitor-entry forced, the Lock button and /protections lock are refused the same way.

Rules that hold whatever the flags say

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.
  • A double chest reaching across a border, and the chest of a cart, boat or pack animal, only opens for a player who may open containers wherever each part of it is. A door, bed or tall plant across a border only breaks for a player who may break both halves.
  • Redstone power from outside a border never reaches doors, lamps or wire inside it.
  • Trees, huge mushrooms, azaleas, moss and anything that spreads (sculk, vines, grass) never change a block across a border from where they grew.
  • Explosions nobody set off (a bed or respawn anchor blown up outside, TNT lit by redstone, a dispensed TNT minecart) break nothing in land whose explosions flag is off. A wind charge only flips doors, levers and buttons a player could use there.

"A border" here is the border with somebody else's land: one owner's protections count as one, so water, pistons and redstone cross freely between them.

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.

While protections are loading

Until every protection has been read from the database, worlds where land can be protected refuse building and interacting, and explosions, fire spread, liquid flow, mob griefing and trampling there, so a slow database never leaves land open. Only a player with the bypass acts during that time.

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, clan members of an added clan and tenants, and, while online, anybody with the admin permission or the bypass. A member added by name who rents nothing is not refused: whoever also holds manage-members is asked whether to remove them as a member and go on, and on yes they are removed and banned in one step.

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, and while it can lose lives its enemies walk in too, with raids.attackers-ignore-lock on (the default). See Raids. 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.

Turning the lock feature off does not stop locking

submodules.lock: false hides the lock button and refuses /protections lock, but visitor-entry stays on the flags screen. Anybody with edit-flags can still lock the land from there.

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:

ClickWhat it does
Left-clickAsks for the greeting.
Right-clickAsks for the farewell.
Shift + right-clickClears both, back to the defaults.

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.

Greeting and farewell settings
config.yml keyDefaultWhat it does
enter-leave.enter-soundBLOCK_AMETHYST_BLOCK_CHIME|0.6|1.4Played walking in
enter-leave.leave-soundemptyPlayed walking out
enter-leave.message-max-length64Longest greeting or farewell
enter-leave.cooldown-millis1500Crossing a border again within it shows nothing, so walking along one stays quiet
enter-leave.show-to-memberstrueOff shows them to visitors only

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.

Logged actions and log settings
ActionWhat is logged
breakA block broken, with its type
placeA block placed, with its type
containerA container opened: chest, barrel, shulker, furnace, blast furnace, smoker, hopper, dispenser, dropper, brewing stand
memberA member or clan added, removed or given another role, and override changes
roleA role created, renamed, deleted, or one of its permissions toggled
flagA flag toggled
banA ban or unban
lockLocked or unlocked
coreThe core hidden, shown or moved. Picking up and deleting are recorded too, but the log of a protection that no longer exists cannot be opened
settingsRenamed, home moved, greeting or farewell changed
raidA life lost, the protection raided, a life bought back, lives set or a raid cleared by an admin
bankDeposits and withdrawals
upkeepUpkeep paid by a member
marketListed, unlisted, bought, given away (by the owner or an admin)
subregionPlots and their members, overrides and flags
rentOffered, offer cancelled, rented, renewed, tenant evicted
upgradeUpgraded, or level set by an admin
warpPublished, unpublished, moved, renamed, described, icon changed
mergeThe protection grown by a new core placed against it ("grown by a new core")

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.

KeyDefaultWhat it does
logs.retention-days14Days an entry is kept. 0 keeps them forever. Old entries are purged every six hours.
logs.flush-seconds10Seconds between two writes of the queued entries.
logs.skip-actions[]Actions not logged. Everything else is, including actions added in later versions.
logs.owner-blocksfalseWhether the owner's own break, place and container are logged.
logs.menu-rows500How many of the newest entries the log screen reads.
The filters search the newest entries only

The log screen reads the newest logs.menu-rows entries and filters those. An older entry of a player is not found by filtering for them. The player filter matches the exact name.

Bypass and admins#

PermissionWhat it does
exyliaprotections.adminOpens every protection's screens, enters every protection, cannot be banned while online, and counts as the owner in every menu and command. It does not let anybody break, place or use anything inside.
exyliaprotections.bypassBuilds, opens and enters anywhere, ignoring every protection, even while protections are still loading.

The bypass only counts when the permission is set for the player, by a permissions plugin. Its plugin.yml default is false, so operators do not bypass: they can test their own land like any player. Grant exyliaprotections.bypass to staff who must build anywhere. The old exyliasurvivalcore.protections.* names are no longer declared.

Something missing on this page? Tell us on Discord