Statistics
The four counters, global and per event, and where players see them.
The counters
| Counter | What it counts |
|---|---|
| Kills | Kills made inside events |
| Deaths | Deaths inside events |
| Wins | Events won |
| Games played | Events taken part in |
They are tracked twice: globally for the player, and per event configuration, so a player's CS:GO record is separate from their Spleef record while their overall totals keep adding up.
| Table | Holds |
|---|---|
events_player_stats | The global totals. |
events_player_event_stats | One row per player per configuration. |
Where players see them
| Command | Shows |
|---|---|
/events stats | Your own statistics |
/events stats <player> | Another player's, with exyliaevents.commands.stats.others |
The stats menu is lang/<code>/menus/user/stats.yml, editable like the rest of the menus.
Reading them from code
EventsAPI exposes the global totals directly:
int kills = EventsAPI.getPlayerKills(uuid);
int deaths = EventsAPI.getPlayerDeaths(uuid);
int wins = EventsAPI.getPlayerWins(uuid);
int games = EventsAPI.getGamesPlayed(uuid);See API.
Reading them from a scoreboard or a hologram
The counters are placeholders as well: %exyliaevents_stats_kills% for the reader's own totals,
%exyliaevents_event_stats_kills_koth% for one event, and %exyliaevents_top_name_kills_1% with
%exyliaevents_top_value_kills_1% for the leaderboard, globally or per event. See
Placeholders.
The plugin ranks players through those placeholders; it does not ship a top-ten menu or a command
that prints one. The ranking placeholders sort on kills, deaths, wins or games and keep the
top ten — anything deeper means reading the tables yourself.
Player preferences
Separately from statistics, one preference is stored per player in events_player_preferences:
whether event music is on. Players toggle it with /events music, and it survives reconnects.
Something missing on this page? Tell us on Discord