Content generated with AI — it may contain mistakes.

ExyliaClans/GuidesguideUpdated in v1.4.0

Read stats, leaderboards and logs

What is counted, where it is stored, the seven rankings, and the per-clan audit trail.

Page 15 of 294 min read

See which clans lead the server, keep a per-clan record of what happened, and fix a number when it is wrong.

Before you start#

  • The leaderboard needs nothing else. The log needs the logs module on, and a member needs the VIEW_LOGS rank permission to read it: see Ranks.
  • Editing stats needs exyliaclans.admin.stats.

Steps#

Open the leaderboard

Run /clan top. Switch between the seven rankings from inside the menu.

Read a clan's log

A member with VIEW_LOGS opens /clan and clicks Clan ▸ Logs. Staff run /clanadmin logs <clan> [amount] (20 lines by default).

Fix a wrong number

Run /clanadmin clanstat <clan> KILLS SET 10 or /clanadmin playerstat <player> DEATHS ADD 1.

Check that it works#

Get a kill in game, then run /clan top and pick kills: your clan's count went up by one. /clan ▸ Clan ▸ Logs shows the last actions the clan took, newest first.

How stats are counted#

TableScopeHolds
clan_statsOne row per clankills, deaths, playtime in seconds
clan_player_statsOne row per player per clankills, deaths, playtime, and the last name seen

clan_player_stats is keyed playerUuid:clanId on purpose: leaving a clan and joining another starts a fresh row rather than carrying a record earned somewhere else. The old row stays behind — a player who rejoins their previous clan picks up where they left off.

Playtime is accumulated per session and flushed when the player quits, when they leave the clan, and when they are removed from it.

A clan that has never died reports its kill count as its KDR

Rather than infinity. A leaderboard has to sort it and a menu has to print it, so kills ÷ 0 becomes kills. The same rule applies to a player's KDR.

Rival kills#

rivals.kill-stat-multiplier multiplies the clan's recorded kill for a kill against a rival. It is rounded half up, so 2.0 records two and 1.5 records two as well. The per-player row always records exactly one. With modules.rivals: false the multiplier is never read at all.

Leaving it at 1.0 — the default — keeps the clan total and the sum of its members in step.

The leaderboard#

/clan top

Seven rankings, switched from inside the menu:

KeyRanks by
onlineMembers online right now
membersTotal members
killsClan kills
deathsClan deaths
kdrClan KDR
playtimeTotal clan playtime
balanceBank balance

Each ranking is built on demand and cached for 30 seconds, so a scoreboard asking for the top ten four times a second does not rebuild it. A clan with no clan_stats row does not appear.

The same keys are what the placeholders take:

%exyliaclans_clan_leaderboard_rank_kills%
%exyliaclans_clan_leaderboard_top_1_online%
%exyliaclans_clan_leaderboard_top_value_1_online%

The online roster#

For a clan scoreboard, clan_online_member_<n> and clan_online_ally_<n> give up to thirty slots each, sorted by rank weight — heaviest first — and then alphabetically. Every slot can also be asked for a field:

%exyliaclans_clan_online_member_1%          the name
%exyliaclans_clan_online_member_1_role%     their rank
%exyliaclans_clan_online_member_1_kdr%      their KDR in this clan
%exyliaclans_clan_online_ally_1_clan%       which allied clan they are from

The roster is rebuilt at most once a second, which is what makes thirty slots on a scoreboard cheap.

The audit trail#

By default a clan keeps its last 200 entries (logs.max-entries-per-clan).

Every clan keeps its own log. It is written for 42 kinds of event: creation, disband, rename; members joining, leaving, being kicked, banned, unbanned, promoted, demoted, assigned a rank; leadership transfers; ranks created, deleted, renamed, re-weighted, re-permissioned, made default; bank deposits and withdrawals; alliance requests sent, accepted, declined, allies removed; rivals added and removed; claims created, reclaimed and removed; homes set and removed; friendly fire and open toggled; invitations sent and cancelled; clan mail sent; every LFP posting event and accepted application; and regroup calls.

Entries past max-entries-per-clan are pruned oldest-first after each write, at most max-entries rows per write — so a clan that is a long way over the limit drains across the next few writes rather than in one query. Set it high and the table grows; set it to 0 and nothing is pruned.

Reading it:

  • /clan → Clan ▸ Logs, for a member with VIEW_LOGS.
  • /clanadmin logs <clan> [amount], defaulting to 20, for staff.

Each line is rendered from the logs.* block in messages.yml, which has a phrase per action plus two templates — one for entries with a target, one for entries without.

With modules.logs: false nothing is written at all, the menu refuses, and /clanadmin logs says so.

Admin edits#

/clanadmin playerstat <player> <KILLS|DEATHS|PLAYTIME> <SET|ADD|REMOVE> <value>
/clanadmin clanstat <clan> <KILLS|DEATHS|PLAYTIME> <SET|ADD|REMOVE> <value>

PLAYTIME is in seconds. Values are floored at zero. Both need exyliaclans.admin.stats.

Something missing on this page? Tell us on Discord