Administration

What only staff do: find any protection on the network and put it right, edit tiers without touching the file, and clear out land nobody plays in. Every menu and command on this page needs exyliaprotections.admin, which operators have by default.

Admin subcommands

There is no reload subcommand. The tier editor writes config.yml itself and applies it at once; any other change to config.yml or the messages needs a restart. /exylialib reload recompiles the menu files.

The admin menu

/protections admin lists every protection on the network, sorted by owner and then by name. Left-click one to open its admin screen; right-click teleports to it.

Five filters narrow the list. Left-click a filter to set it and right-click to clear it; right-click the Protection admin button in the middle to clear them all.

A protection's state is the most urgent thing about it, in that order: raidable, abandoned, for sale, for rent (it, or one of its plots, has a rent offer), normal. Each admin's filters are their own, and kept until they log out.

The row of a protection shows its owner, tier, size, world, server, core location, members and state. The Tier editor and Inactive cleanup buttons open the sections below.

The admin screen of a protection

The top of the screen shows the owner, tier and level, state, size, members, bank, location, server, when its owner or a member last played, and how long ago it was made.

Set level. A higher level grows the land the way an upgrade does, by the difference in radius-bonus, and is refused when the grown land would overlap another protection of that server and world. A lower level keeps the land as it is; only the level and what it unlocks change. Nothing is charged.

Transfer. The player is found by name, online or not, and the protection is theirs, whatever their limits or the tier's permission say. Everything else follows the rules of a sale: members stay or go as market.keep-members says, rents end with each tenant paid back from the bank, and offers are withdrawn. See Economy. It is not refused while the protection is raidable, abandoned or rented.

Lives. Setting the lives asks for a number from 1 to the protection's maximum, ends any raid and cooldown, and starts the regrowth clock from now. Clearing the raid gives every life back, with no raid and no cooldown. See Raids.

Upkeep. Only for an abandoned protection: nothing is owed any more, the next period starts now, and the owner counts as seen, so the next check does not abandon it again at once. It is refused while the bank is busy. See Economy.

Force delete. Deletes it even while it is raided, abandoned, rented or for sale. Tenants are paid back from the bank first and the rest of the bank goes to the owner, as with any deleted protection. The core block is removed and not given back.

Every change made here is written to the protection's log as done by an admin, and from the console as done by the console.

The tier editor

Tier editor lists every tier with its size, height, shop price, limit and how many protections on the network use it. New tier asks for an id, up to 32 of a-z, 0-9, - and _, and opens it with the fields of a new tier: an AMETHYST_BLOCK core named PROTECTION CORE, no lore, radius 10, FULL height, y-radius 10, not sold in the shop, no permission, no limit and no flags on.

Each change rewrites config.yml on the spot and applies at once, on this server. Other servers reading the same file pick it up on their next restart. A tier's lives and upkeep cost are kept in their own sections; a tier never given them uses raids.default-lives and upkeep.default-cost. What every key means is on Creating protections.

Delete tier is refused while any protection on the network uses the tier, and for the tier selection.tier names. After a dangerous confirmation the tier goes, with its lives and upkeep entries. Its core items stop working: placing one is refused.

Inactive cleanup

Removes protections whose owner and members all stopped playing.

From the menu. Inactive cleanup asks how many days, 1 to 3650, offering cleanup.default-days first, and opens the preview: every protection that would go, oldest first, with how long ago its players were last seen. Clicking one opens its admin screen.

From the command. /protections admin cleanup <days> prints how many would go, how many were kept for having a never-seen player, a tenant or money in the bank, and the first ten with their world and server. Adding confirm runs it at once, with no further question. Days below 1 count as 1.

A protection is removed when:

1. Its owner and every player member were last seen more than that many days ago. Clan members do not count: a clan is added whole.
2. Nobody in it is unknown, never seen, unless --include-unknown, or the menu's Never seen players switch, is on.
3. Nobody rents in it right now, with cleanup.skip-with-tenants.
4. Its bank holds nothing, with cleanup.skip-with-bank.

"Last seen" is a player's last join or quit on any server of the network, and now while they are online on this server. The plan is made again when the removal starts, and each protection is judged once more just before it goes, so an owner who came back since the preview keeps their land. Removal runs batch-size protections a tick and tells whoever started it how many it removed. Each one is logged as removed by the inactivity cleanup, its bank goes to the owner, and its core block is removed.

A cleanup still running when the server stops is cancelled; what it had not removed yet stays.

All keys

cleanup:
  default-days: 30
  skip-with-tenants: true
  skip-with-bank: false
  batch-size: 20