Menus

Every screen is a file under plugins/ExyliaClans/menus/. They are written on first start, never overwritten, compiled once at enable and recompiled on reload — so opening one renders slots rather than re-reading YAML.

The thirty-seven files

main_clan and main_no_clan are two files because /clan opens a different screen depending on whether the player is in one.

What a file looks like

title: "{primary}&l%clan_name%"
size: 45
type: SIMPLE
refresh:
  mode: SMART
  interval: 20
animation: "center_out"
 
open_sounds:
  - "ENTITY_EXPERIENCE_ORB_PICKUP|1.0|1.2"
click_sounds:
  - "UI_BUTTON_CLICK|1.0|1.5"
 
filler:
  global:
    material: GRAY_STAINED_GLASS_PANE
    hide_tooltip: true
 
items:
  level:
    slot: 16
    material: EXPERIENCE_BOTTLE
    name: "{warning}&lCLAN LEVEL"
    lore:
      - " {muted}❙ {letters}Level: {warning}%clan_level%{muted}/{warning}%max_level%"
      - "{info}» Click to view all levels"
    actions:
      - "exyliaclans:open_level_menu"

The full grammar — sections, pagination, conditions, item options, click kinds — belongs to ExyliaLib's menu module and is documented in its own reference. What is specific to this plugin is the placeholders each screen supplies and the actions it can call.

Per-screen placeholders

Each screen supplies its own values on top of the global ones. What follows is the whole of it, screen by screen — a name that is not listed under a screen is not supplied there, and a name nothing answers stays on the item as raw text.

A screen that paginates supplies two kinds of value. The ones the screen holds resolve anywhere in the file — the title, the static buttons, their lore. The ones a row holds resolve only inside the paginated section, once per entry. Where a screen has both, they are listed separately.

main_no_clan

main_clan

clan_info

settings

confirm

members, members_view and mail_member_select

One class draws all three: members for your own clan, members_view for another's, and mail_member_select when picking a recipient. The screen supplies:

Each row supplies:

member_manage

banned

Each row supplies:

clan_invitations

Each row is a clan that has invited the viewer:

clan_pending_invites

Each row is a player this clan has invited:

roles

The screen supplies:

Each row is a rank, heaviest first:

role_manage

<permission> is any of the twenty-six rank permissions in lower case — %perm_invite_status%, %perm_manage_roles_mat%, %perm_view_logs_status% and so on for each name in Ranks.

assign_role

The screen supplies:

Each row is a rank lighter than the viewer's own:

bank

level

The screen supplies:

Each row is one configured level:

leaderboard

The screen supplies:

Each row of the clans section is a ranked clan:

Each row of the stat_types section is one of the seven counters:

logs

Each row is one log entry, most recent first, two hundred at most:

allies

The screen supplies:

Each row is an allied clan:

rivals

The screen supplies:

Each row is a rival clan:

browse_clans

Each row is an open clan the viewer is not already in:

mail_inbox

The screen supplies:

Each row is one mail. A read mail is drawn from the read template:

mail_view

lfc_browse

The screen supplies:

Each row is somebody else's active profile:

lfc_create

The screen supplies:

Each row is a category to answer:

lfp_browse

The screen supplies:

Each row is an active posting:

lfp_create

The screen supplies:

Each row is a category to answer:

lfp_applications

The screen supplies:

Each row is one application to this clan:

lfp_application_detail

lfp_my_applications

Each row is an application the viewer has sent:

lfc_option_select and lfp_option_select

The screen a single-select category opens. Both supply the same names. The screen supplies:

Each row is one of its options:

lfc_tier_select and lfp_tier_select

The screen a multi-answer category opens: one row per answer, each leading to its own tier list. Both supply the same names. The screen supplies:

Each row is one answer:

lfc_mode_select and lfp_mode_select

The tier list for one answer. Both supply the same names. The screen supplies:

Each row is one tier:

Any paginated screen

The menu module fills these in itself, in the title and in the page buttons:

Every global %exyliaclans_…% placeholder works in a menu too, and so does anything PlaceholderAPI provides.

Actions

Buttons call actions in the exyliaclans: namespace. Ninety-odd are registered; these are the ones worth knowing when rearranging a menu.

Opening screens

open_main_menu, open_members, open_clan_members <clanId>, open_member_manage, open_roles, open_role_manage, open_assign_role, open_banned, open_bank, open_level_menu, open_allies, open_rivals, open_clan_allies_by_id <clanId>, open_browse_clans, open_clan_info_by_id <clanId>, open_invitations, open_pending_invites, open_settings, open_leaderboard, open_clan_logs, open_mail_inbox, open_mail_view, open_lfc_browse, open_lfc_create, open_lfp_browse, open_lfp_applications, close_menu.

Acting

Every action that acts on the clan still runs the same rank-permission and module checks the command does — moving a button does not move a permission.

The leaderboard's counters

leaderboard.yml's stat_types section declares selected_template and not_selected_template with no actions key. The click is bound in code — exyliaclans:lb_select_type %stat_type% on every click kind — so the file works as written. If you rewrite that section, add the action explicitly.

Resetting a menu

Delete the file and restart. It is written back from the jar; existing files are never overwritten.