Placeholders
The counters, statistics and leaderboards the plugin answers through PlaceholderAPI.
Every placeholder below is written in full, and clicking one copies it.
Counters
| Placeholder | Description |
|---|---|
%exyliaevents_total_players% | Everyone inside active events, players and spectators together. |
%exyliaevents_total_participants% | Only the players, without spectators. |
%exyliaevents_total_spectators% | Only the spectators. |
%exyliaevents_active% | How many events are active, not counting disabled ones. |
%exyliaevents_waiting% | How many are joinable right now — waiting or counting down. |
%exyliaevents_in_progress% | How many are actually playing. |
%exyliaevents_waiting% and %exyliaevents_in_progress% do not overlap: an event counting down is
joinable, and one that is playing is not.
One event's state
%exyliaevents_status_bol_<eventId>%Returns true when that event exists and is not disabled, false otherwise. The id goes on the end,
and an id containing underscores is read whole rather than being cut at the first one.
%exyliaevents_status_bol_lms1%The reader's team
%exyliaevents_team_color%
%rel_exyliaevents_team_color%The colour code of the team the player who reads it belongs to — &c, &9, &a or &e — in a team
event. Empty for a player who is not in one, which is what lets it be dropped straight into a chat or
tab format without a fallback.
The relational form answers for the other player — the one whose name tag or tab entry is being drawn — rather than the reader, so a nametag or tab plugin can colour every name by its owner's team.
The reader's statistics
The four counters of the player who reads them, added up across every event.
| Placeholder | Description |
|---|---|
%exyliaevents_stats_kills% | All-time kills. |
%exyliaevents_stats_deaths% | All-time deaths. |
%exyliaevents_stats_wins% | All-time wins. |
%exyliaevents_stats_games% | All-time games played. |
%exyliaevents_stats_kdr% | Kills over deaths, two decimals — 1.75. |
%exyliaevents_stats_winrate% | Wins over games played, one decimal and a percent sign — 42.0%. |
The same counters for a single event configuration:
%exyliaevents_event_stats_<stat>_<eventId>%<stat> is kills, deaths, wins, games, kdr or winrate, and the id is everything after
it, so an id with underscores in it is read whole:
%exyliaevents_event_stats_kills_koth%
%exyliaevents_event_stats_winrate_block_party%Both forms need a player to read them, and both are the reader's own — there is no placeholder for another player's statistics.
Leaderboards
The top ten of a counter, one placeholder per position, for holograms and boards.
%exyliaevents_top_name_<stat>_<position>%
%exyliaevents_top_value_<stat>_<position>%<stat> is kills, deaths, wins or games — kdr and winrate are worked out per player
rather than stored, so nothing can be sorted on them. <position> is 1 to 10.
%exyliaevents_top_name_kills_1% Steve
%exyliaevents_top_value_kills_1% 482One event's board instead of every event at once, with the id last:
%exyliaevents_event_top_name_<stat>_<position>_<eventId>%
%exyliaevents_event_top_value_<stat>_<position>_<eventId>%%exyliaevents_event_top_name_wins_3_koth%A board is read at most once a minute and kept in memory in between, so a hologram that refreshes
every second costs nothing extra. While the first read is still in flight the placeholder reads -,
and a position nobody has reached yet reads ---. A statistic placeholder whose row has not been
read yet reads - the same way.
Using them in the plugin's own files
The sidebars in scoreboards.yml and the boss bars in messages.yml are rendered with the tokens the
running event fills in, not with these. Each event type fills the ones its own screens need, so
%time% is on every one of them and %round% only where there are rounds. These placeholders are
for reading the plugin's state from outside: a hub scoreboard, a tab list, another plugin's menu.
Something missing on this page? Tell us on Discord