Menus

Everything players do with their land happens in menus opened from /protections. Every button carries the protection's id in its action, so a screen holds no state of its own: a click is checked again against the protection as it is when the click arrives, and refused when the player lost the right to do it in the meantime.

The files

Every screen is a file under lang/<language>/menus/, in the language folder ExyliaLib is set to (en, es, pt or fr).

Each file's header comment lists the placeholders it receives. Buttons show only while their condition holds; the %…_enabled% placeholders are true or false from submodules. An action prefixed with left:, right:, shift_left: or shift_right: runs on that click only; without a prefix it runs on any click.

Menu files are read when the plugin enables and again on /exylialib reload. A file that does not parse is named in the console and left out, instead of opening as an empty screen.

The hub

/protections (or /ps, /claims) opens menus/user/main.yml, a 27-slot screen.

The list

menus/user/list.yml: every protection the player owns or belongs to, on any server, oldest first, 36 to a page. Each shows its owner, the player's role, size, location, server and member count.

The overview

menus/user/manage.yml is one protection's own screen: 45 slots, a summary at the top and one button per section. It needs membership; admins open anybody's.

Back returns to the list, except for an admin looking at somebody else's protection, who goes back to the admin screen they came from. Every button is shown to every member; one their role does not allow answers "You cannot do that in this protection."

Sections, and the section that sticks

Each section is a 36-slot screen, menus/user/manage_<section>.yml, whose Back (slot 31) returns to the overview with section <id> hub.

Opening a section remembers it for that player and that protection. Every later reopening of the protection's screen — a Back from members, roles, bans or logs, or the screen coming back after a change — lands on that section again, not on the overview. It is forgotten when the player goes back to the overview, opens another protection, or leaves the server. Opening a protection from the list always starts on the overview.

Land — manage_land.yml

People — manage_people.yml

Access — manage_access.yml

Economy — manage_economy.yml

Growth — manage_growth.yml

Defense — manage_defense.yml

Extras — manage_extras.yml

Slot 4 of every section is a summary of what it holds and has no action.

The other screens

Every list below is a 54-slot paged screen: up to 36 entries a page (fewer on the grid-shaped ones), previous and next page buttons, and Back in slot 49.

A switch in permissions.yml shows ON / OFF for flags and roles, ALLOW / DENY / ROLE for a member's overrides, and ALLOW / DENY / PROTECTION (follow the protection) for a plot's flags.

Actions

Every button runs an action written exyliaprotections:<name> <arguments>, so a restyled menu can call any of them. Placeholders such as %protection_id% fill the arguments. Up to four arguments are read.

Before running, every action is refused while its feature is off ("That feature is turned off."), when the protection no longer exists ("That protection no longer exists."), or when the requirement below does not let the player through. <id> is a protection id.

Land and the protection itself

People and access

toggle targets, as PermissionTarget spells them:

Economy and estates

Extras

Admin

Every one of these needs exyliaprotections.admin. They are described on Administration.