Content generated with AI — it may contain mistakes.

Commands

Every /protections and /protectionsadmin subcommand, the permission and role right each one asks for, and what it does.

Page 14 of 253 min read

Two roots: /protections for players, also answering to /ps and /claims, and /protectionsadmin for staff, also answering to /psadmin and /padmin. Almost everything a player does happens in the menus /protections opens; the subcommands are shortcuts for what is done standing in your own land.

How the land is picked#

Every subcommand that acts on a protection acts on the one you are standing in. Outside every protection it answers "there is no protection here" and does nothing.

Four checks run before anything happens, in this order:

  1. The command permission. exyliaprotections.use for every player subcommand, exyliaprotections.admin for /protectionsadmin and the admin ones.
  2. The feature. A subcommand belonging to a feature turned off under submodules in config.yml says the feature is disabled. See Configuration.
  3. The feature node. The column Node below names the exyliaprotections.* node that subcommand asks for, held by everybody unless a server takes it away from a rank. Without it the player is told their rank does not include that feature. See Permissions.
  4. Who you are there. The column Who below says what you need on that protection: a role permission such as manage-bans (held through your role or your clan's), Owner, or Any member. The owner always passes.

exyliaprotections.admin counts as the owner and as holding every role permission on every protection, so staff can run all of these anywhere. See Permissions.

Player commands#

Every command here needs exyliaprotections.use, which everybody has by default, and runs for players only, except help. The column Permission names the feature node a rank can lose; see Permissions.

CommandWhat it doesPermission
/protectionsOpen your protections menu.exyliaprotections.use
/protections helpList the commands in chat.exyliaprotections.use
/protections home [name]Teleport to the home of your only protection, or of the one you name. With several protections and no name it opens the list.exyliaprotections.home
/protections infoSay who owns the protection you stand in, your role there, its size and how many members it has.exyliaprotections.use
/protections showDraw the border of the protection you stand in.exyliaprotections.show
/protections upgradeUpgrade the protection you stand in to its next level, after asking you to confirm.exyliaprotections.upgrade

Members and access#

CommandWhat it doesPermission
/protections add <player> [role]Add a player who has played here to the protection you stand in, with the role you name or the first role you may hand out.exyliaprotections.members.add
/protections remove <player>Remove a member from the protection you stand in.exyliaprotections.use
/protections ban <player> [duration] [reason]Ban a player from the protection you stand in, for a while or for good.exyliaprotections.ban
/protections unban <player>Lift a ban in the protection you stand in.exyliaprotections.use
/protections lockLock or unlock the protection you stand in.exyliaprotections.lock
/protections logsOpen the activity log of the protection you stand in.exyliaprotections.logs

Selling, giving and the bank#

CommandWhat it doesPermission
/protections marketOpen every protection for sale.exyliaprotections.market.buy
/protections sell <price>List the protection you stand in for sale.exyliaprotections.market.sell
/protections unsellTake the protection you stand in off the market.exyliaprotections.use
/protections transfer <player>Give the protection you stand in to another online player.exyliaprotections.transfer
CommandWhat it doesPermission
/protections bankShow the balance of the bank of the protection you stand in.exyliaprotections.use
/protections bank deposit <amount>Put money into the protection's bank.exyliaprotections.bank.deposit
/protections bank withdraw <amount>Take money out of the protection's bank.exyliaprotections.use
/protections upkeepShow the upkeep state, cost, period and debt of the protection you stand in.exyliaprotections.use
/protections upkeep payPay what the protection owes in upkeep.exyliaprotections.use

Plots and rent#

CommandWhat it doesPermission
/protections subregion createGet a selector to mark a new plot inside the protection you stand in.exyliaprotections.subregions
/protections subregion delete <plot>Delete a plot, after asking you to confirm.exyliaprotections.subregions
/protections subregion infoSay what the plot you stand in is: size, members, private or shared, rent.exyliaprotections.use
/protections rentOpen your rents and everything offered for rent.exyliaprotections.use
/protections rent offer <price> <period>Offer the plot you stand in, or the whole protection outside every plot, for rent. The period is a duration such as 7d.exyliaprotections.rent.offer
/protections rent cancelWithdraw the rent offer of the plot you stand in or of the whole protection.exyliaprotections.use

Warps#

CommandWhat it doesPermission
/protections warpsOpen the public warps.exyliaprotections.warp.visit
/protections warp <name>Visit a public warp by name.exyliaprotections.warp.visit
Role permission each command asks for

After the feature node, a subcommand asks what you are in that protection. The owner always passes.

  • ban, unban: manage-bans. add, remove: manage-members. lock: toggle-lock. logs: view-logs.
  • bank deposit: bank-deposit. bank withdraw: bank-withdraw. bank shows the balance to anybody holding one of the two.
  • subregion create and delete: manage-subregions. rent offer and rent cancel: manage-rent.
  • sell, unsell, transfer: owner only. upgrade: owner only. upkeep and show: any member.
  • A feature turned off under submodules in config.yml answers "That feature is turned off."

There is no wipe or reset subcommand: ExyliaLib's /exylialib wipe and /exylialib resetplayer cover the plugin's tables. See Administration.

Staff commands#

Everything below needs exyliaprotections.admin (operators by default). Subcommands that act on land act on the protection you stand in, and answer "there is no protection here" outside one.

CommandWhat it doesPermission
/protectionsadminOpen the admin hub: Protections, Tiers, Cleanup, Settings and Reload.exyliaprotections.admin
/protectionsadmin give <player> <tier> [amount]Give a player protection cores of a tier. The amount goes from 1 to 64.exyliaprotections.admin
/protectionsadmin list [owner]Open every protection on the network, or only one owner's.exyliaprotections.admin
/protectionsadmin hereOpen the admin screen of the protection you stand in.exyliaprotections.admin
/protectionsadmin deleteDelete the protection you stand in, after you confirm.exyliaprotections.admin
/protectionsadmin transfer <player>Hand the protection you stand in to another player, whatever their limits say.exyliaprotections.admin
/protectionsadmin level <level>Set the upgrade level of the protection you stand in.exyliaprotections.admin
/protectionsadmin lives <lives>Set the raid lives of the protection you stand in.exyliaprotections.admin
/protectionsadmin flag <flag> <allow|deny|default>Force a flag on every protection and plot, or give it back to each owner with default.exyliaprotections.admin
/protectionsadmin feature <feature> <on|off>Turn a whole feature on or off. It is written into config.yml.exyliaprotections.admin
/protectionsadmin settingsOpen the settings screens.exyliaprotections.admin
/protectionsadmin tiersOpen the tier editor.exyliaprotections.admin
/protectionsadmin replaysOpen the raid replays of the protection you stand in.exyliaprotections.admin
/protectionsadmin replays leaveStop watching a raid replay.exyliaprotections.admin
/protectionsadmin migrate <INTERNAL|WORLDGUARD>Switch between the two backends and move every region over. WORLDGUARD needs WorldGuard.exyliaprotections.admin
/protectionsadmin reloadReload config.yml, the messages and the menus.exyliaprotections.admin
/protectionsadmin import protectionstones [--dry-run]Turn ProtectionStones regions into protections. With --dry-run it only reports what it would do.exyliaprotections.admin
/protectionsadmin cleanup <days> [preview|confirm] [--include-unknown]Remove protections nobody has played in for that many days. Players get a screen; the console previews, or removes with confirm.exyliaprotections.admin
/protections admin <give|migrate|reload|import|cleanup>The older spelling of the admin subcommands; /protections admin alone opens the hub.exyliaprotections.admin
  • flag and feature write config.yml on the spot, under forced-flags and submodules, and apply at once; with the WORLDGUARD backend the mirrored regions are updated too. A value the file does not take is refused with the reason. See Configuration.
  • migrate reports the backend it ended on and how many protections it moved. See Backends.
  • import protectionstones reports how many regions were imported, already imported, overlapping and skipped, then lists the first ten problems. A dry run also warns when import.remove-source-regions is on. See Migration.
  • cleanup from the console without confirm is a preview: how many would go, how many were kept for having no record of their players, a tenant or money in the bank, and the first ten. --include-unknown also removes those without a record. Days below 1 count as 1. See Administration.

The old /protections admin#

/protections admin still answers the subcommands it had before /protectionsadmin existed, and runs the same code: /protections admin (the hub), give, migrate, reload, import protectionstones and cleanup. Every other staff subcommand is only under /protectionsadmin.

/ps and ProtectionStones

ProtectionStones also registers /ps, and only one of the two can answer to it while both are installed. /protections and /claims always reach this one. Remove ProtectionStones once its regions are imported.

Something missing on this page? Tell us on Discord