Commands

One root, /protections, also answering to /ps and /claims. Almost everything a player does happens in the menus it 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.

Three checks run before anything happens, in this order:

1. The command permission. exyliaprotections.use for every player subcommand, exyliaprotections.admin for 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. 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.

Arguments

• <price> and <amount> are read the way players type money: 500, 2.5k, 1m.
• <period> is a duration: 30m, 12h, 1d, 1w. A bare number is seconds.
• [duration] of a ban is a duration as above, or permanent (also perm, forever). Leaving it out bans for good. Anything after it is the reason, spaces included, cut to bans.reason-max-length characters.
• <player> for ban and transfer suggests the players online.

When subregions is off, rent offer and rent cancel always act on the whole protection. Whether a whole protection may be rented at all is rent.whole-protection. See Economy for sales, transfers, banks, upkeep and rent, and Land tools for plots, levels and merging.

Staff commands

Everything below needs exyliaprotections.admin (operators by default).

Every one but the bare /protections admin also runs from the console.

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