Placeholders
Every placeholder the plugin answers, in both the PlaceholderAPI and the in-plugin form, and the values the menu and message files are filled with.
Every placeholder below is written in full, and clicking one copies it.
How the name is written
The plugin registers its placeholders through ExyliaLib as the group crate. Inside an Exylia plugin's own
files — menus, messages.yml, another Exylia plugin's scoreboard — the registered name stands on its own:
%crate_keys_vote%Through PlaceholderAPI, for any other plugin, the plugin's name goes in front of it:
%exyliacrates_crate_keys_vote%This page writes the PlaceholderAPI form throughout; drop exyliacrates_ for the in-plugin one. Nothing has
to be downloaded from the eCloud.
<crate> and <key> are ids. Ids may contain underscores — %exyliacrates_crate_keys_daily_reward% reads
the crate daily_reward.
All of them answer for the player reading them.
The placeholders
| Placeholder | Description |
|---|---|
%exyliacrates_crate_keys_<crate>% | Keys the reader can spend on that crate: key items carried plus balance, of the first key the crate's cost lists. 0 for a crate that takes no key; no value for an unknown crate. |
%exyliacrates_crate_key_<key>% | The same for one key, by the key's id. No value for an unknown key. |
%exyliacrates_crate_keys_total% | Every key the reader holds, items and balance, added up. |
%exyliacrates_crate_pity_<crate>% | Openings left before the crate's guarantee, 0 when the next one is guaranteed. No value when the crate has no guarantee or does not exist. |
In Exylia files a placeholder with no value can be given a fallback with ExyliaLib's | form:
%crate_pity_vote|-%.
The key counts are what the hologram over every crate is written with, so a scoreboard and the hologram never disagree. They read the reader's balance as this server holds it; until it has loaded after they join, only the key items they carry are counted.
%exyliacrates_crate_keys_total% always means the total. A crate whose id is total cannot be read through
crate_keys; read it through its key with crate_key_<key>.
Values in the plugin's own files
These are filled in by the plugin itself and only work in the file named.
messages.yml
| Line | Values |
|---|---|
hologram-lines | %crate% the crate's name, %keys% the reader's own count of its key |
opened, opened-many | %crate%, %reward%, %count% |
opened-line, opened-line-many | %reward%, %amount% |
broadcast | %player%, %reward%, %crate%, %tier% |
keys-received, keys-while-away, keys-removed, keys-changed | %amount%, %crate%, %key% |
keys-given, keys-taken, keys-set | %player%, %amount%, %crate% (the key's id) |
keys-given-all | %amount%, %crate%, %key%, %count% |
missing-keys | %crate%, %amount%, %key% |
missing-money | %crate%, %amount% written in its currency |
reveal-self, reveal-other | %tier%, %reward%, %player%, %crate% |
reveal-count | %amount% |
pick-title, pick-subtitle | %seconds% |
speed-up-hint | %speed% |
key-lore | %crate% the crates the key opens, %key% its name |
wand-name / wand-lore | %id% / %crate% |
rewards-claimed | %amount% |
Menus
| File | Values |
|---|---|
menus/user/preview.yml | %crate_id%, %crate_name%, %crate_icon%, %crate_keys%, %crate_pity%; per reward %reward_name%, %reward_icon%, %reward_chance%, %reward_tier%, %reward_color% |
menus/user/crates.yml | %keys_total%; per crate %crate_id%, %crate_name%, %crate_icon%, %crate_keys% |
menus/user/history.yml | %history_title%; per row %opening_player%, %opening_crate%, %opening_reward%, %opening_icon%, %opening_tier%, %opening_color%, %opening_ago%; %back% on the back button |
Each file lists its own values in the comment at its top.
Animation phases and celebrations
%reward%, %tier%, %tier_color%, %player%, %crate% and %amount%, plus {item:reward} for the
prize's icon. See Animations.
Something missing on this page? Tell us on Discord