Read leaderboards and player stats
The profile, the records per drill, the session and duel history, and the leaderboards built on top.
Every player has a profile, a best for each drill, a history of runs and duels, and a place on the leaderboards. This page shows where to read them and how to reset someone.
Before you start#
Players need exyliaaimtrainer.profile, exyliaaimtrainer.leaderboard and exyliaaimtrainer.history, all granted to everyone by default, see Permissions. Results are stored in the database, so nothing needs setting up.
Steps#
Open a profile
Run /aim profile (or /aim stats), or click Profile in /aim. /aim profile <player> opens somebody else's, offline players included.
Read the bests
Click Records to see your best of every drill. Left click a row to play that drill, right click it to open its leaderboard. Aim opens your session history and Duels your duel history.
Open a leaderboard
Run /aim leaderboard (or /aim top), or click Leaderboards in /aim, and pick a board. Inside, Sort by changes the category (left and right click) and Edition swaps between Java and Bedrock.
Check that it works#
Finish a drill, then open /aim profile: the sessions count and rating have moved, and the drill is in Records. Your name appears on that drill's board once you hold a rating there.
Going further#
Show a leaderboard outside the menus#
Placeholders such as %exyliaaimtrainer_top_gridshot_rating_1% and %exyliaaimtrainer_top_gridshot_rating_1_value% show the first place of a board. See Placeholders.
Why is somebody missing from a board?#
Only a run that finished and did something is stored; leaving mid-run stores nothing. The accuracy board needs at least 20 shots (leaderboard.accuracy-min-shots). Duels never set records. Boards are cached 300 seconds (leaderboard.cache-seconds), so a new rating can take a while to show.
Reset a player#
Open /aimtraineradmin, click Players, then click the player (left click if they are free, right click if busy) and confirm. You need exylialib.admin.wipe. This deletes their profile and every record, so they leave every board.
How long history is kept#
history.entries rows are shown (20) and rows older than history.retention-days (30) are deleted. 0 keeps everything.
Technical details
Four tables hold what a player has done. Each answers a different question, and none is rebuilt from another, which is what makes the two history tables safe to prune.
| Table | One row per | Answers |
|---|---|---|
aim_profiles | Player | Lifetime numbers, the duel record, the overall rating per edition and the player's settings |
aim_records | Player, drill and edition | The bests, which is what a drill's leaderboard ranks |
aim_sessions | Finished solo run | The session history a player scrolls through |
aim_matches | Participant per duel | The duel history |
The fifth table, aim_arenas, holds the arenas and is covered on Arenas.
Java and Bedrock#
Java and Bedrock players are ranked apart: touch and controller aim, with aim assist, is not the same contest as a mouse. A session reads its player's edition once, when it starts, and its result lands on that edition's records and boards and in that edition's profile totals. A player who plays on both keeps two sets of bests and two overall ratings. Settings and the duel record are the player's, whatever they play on.
Rows written before editions existed are labelled Java once, on the first start of the new version.
The profile#
The row is loaded when the player joins, written on every change and again when they quit. A player whose row is still loading plays with the default settings.
| Field | Moved by |
|---|---|
| Sessions | Every stored solo run. Duels do not count here. |
| Total hits, total shots, accuracy | Solo runs and duels, per edition. A shot is a hit or a miss; an expired target is neither. Accuracy is stored as a percentage so the overall board can sort on it. |
| Total time trained | Solo runs and duels. |
| Fastest flick, fastest reaction | The lowest non-zero time, from solo runs and duels alike. |
| Overall rating | Solo runs only, per edition: the sum of the player's best rating in every drill configured now. It is recomputed from the records as runs land, on join and after a reset, so a drill removed from config.yml stops counting and a lost write never leaves it wrong for good. |
| Matches, wins, losses, win rate | A decided duel. |
| Rounds, round wins, round losses | A decided duel, from the final series score. |
| Current streak, best streak | Duel win streak: up by one on a win, back to zero on a loss. |
| Size, distance, colour, style, the five toggles | The settings screen. |
| Last drill, last best-of | The last picks made in a menu, so the pickers open where the player left them. |
The profile row also carries a freeze column. It is always written as true and nothing reads it;
it stays so an existing table needs no migration.
/aim profile, or /aim stats, opens the profile screen, showing the rating, accuracy, hits and shots
of the edition the player is on: rating, accuracy, sessions and duels on the head; hits, shots, fastest flick and reaction and time trained; duels played, wins, losses, win rate
and rounds; the current and best duel streak; and three buttons: Aim (the session history), Duels (the duel history) and Records. /aim profile <player> opens someone else's, read from the
database when they are offline. The name has to be one ExyliaLib's player cache knows; otherwise the
command answers player-not-found.
Records#
One row per player, drill and edition, keyed uuid:drill on Java and uuid:drill:bedrock on Bedrock. A
run is merged into its row when it ran its course and did anything: a hit, a miss, an expired
target, a false start or a single tracked tick.
A run cut short stores nothing. Leaving mid-run, quitting, being taken back by ExyliaPracticeCore, pressing Play again or changing drill mid-run all drop the run: a few hundred milliseconds with one lucky hit would extrapolate to a record no full run can reach.
| Field | Merge rule |
|---|---|
sessions | Plus one |
bestRating | The higher. The rating is the score times the difficulty; see Scoring. |
ratingSize, ratingDistance | The size and distance multipliers the player had set, only when the rating was beaten |
bestScore | The higher |
bestAccuracy | The higher, counting only a run with at least leaderboard.accuracy-min-shots shots |
bestStreak | The higher. A streak is hits in a row; a miss, an expired target or a false start ends it. |
mostHits | The higher |
bestCombo | The higher. Only a COMBO drill builds one. |
bestReactionMillis | The lower non-zero single reaction. Only a REACTION drill sets one. |
bestFlickMillis | The lower non-zero time between two hits |
bestOnTarget | The higher percentage of the run spent on target. Only a TRACK drill sets one. |
totalHits, totalShots, totalTimeMillis | Added up |
When the rating beats the old best, the profile's overall rating is recomputed, the result screen and chat call it a personal best, and the cached boards are dropped so the player sees themselves on the board they just climbed.
A duel moves the profile — the duel record, the lifetime hits, shots, time and fastest times — and
writes two history rows. It never touches aim_records, so it cannot put anybody on a drill's board or
raise their overall rating.
The Records screen, reached from the profile, lists every row the player holds on the edition they
are on, in the order the
drills appear in config.yml; a row for a drill no longer in the file goes last. Each row shows the
best rating and the size and distance it was set at, the other bests, and the drill's lifetime
sessions, accuracy and time.
Leaderboards#
There is one board per drill, sorted by one of seven categories, and one overall board, each twice: once for Java and once for Bedrock.
| Category | Sorts by | Default name |
|---|---|---|
rating | bestRating, highest first | Rating |
score | bestScore, highest first | Best score |
accuracy | bestAccuracy, highest first | Accuracy |
streak | bestStreak, highest first | Best streak |
hits | mostHits, highest first | Most hits |
reaction | bestReactionMillis, lowest first | Fastest reaction |
combo | bestCombo, highest first | Best combo |
Names and icons live in messages.yml under menu.categories.
A player appears once per drill board, since the records are one row per player, drill and edition. A zero
never takes a place: an unset reaction, a combo in a drill that has none, an accuracy from runs below
the shot floor. So the reaction board of a flick drill and the combo board of anything but a fight
stay empty.
Only rating compares two players who set their targets up differently: it carries the difficulty
of the size and distance each played at. The other categories are raw bests. Every row shows the size
and distance its rating was set at, whichever category the board is sorted by.
The overall board
Everybody by the sum of their best rating in every drill, read from aim_profiles. The Bedrock overall
board lists only players who have played on Bedrock. It sorts by
rating or by accuracy (lifetime accuracy) and nothing else: the category row on that board offers
those two, and asking for another category shows the rating board.
Opening a board
/aim leaderboard, or /aim top, opens the board picker: the overall board first, then every drill
in config order. /aim leaderboard <drill> opens that drill's board sorted by rating, and
/aim leaderboard <drill> <category> by that category; overall works as the drill. An unknown drill
opens the picker instead of an empty board, and an unknown category falls back to rating. Inside, the
the Sort by button cycles the category (left click forward, right click back) and re-sorts the open board in place, and the top three rows wear medals. A board opens on
the viewer's own edition; the edition button swaps the open board to the other one, keeping its category.
The same boards are readable through PlaceholderAPI, as
%exyliaaimtrainer_top_<drill>_<category>_<n>% and its _value for Java, and
%exyliaaimtrainer_top_bedrock_<drill>_<category>_<n>% for Bedrock. See
Placeholders.
The cache
leaderboard:
entries: 10
cache-seconds: 300
accuracy-min-shots: 20| Key | Default | What it does |
|---|---|---|
entries | 10 | Rows per board. |
cache-seconds | 300 | How long a board is kept before the database is asked again. Anything below 5 is treated as 5. Read when the plugin starts: a reload does not change it. |
accuracy-min-shots | 20 | Shots a run needs before its accuracy may become a best. Ten out of ten is not a record. |
Every board keeps two copies: a fresh one, which expires after cache-seconds, and the last one ever
read. A menu waits for a fresh read; a placeholder shows the last copy while the fresh read runs in the
background, so a hologram never blinks back to Loading… once it has shown a board.
The fresh copies are dropped when a run beats a rating, and when a player is reset. A run that improves
only another best — accuracy, hits, a streak — does not drop them: that board catches up within
cache-seconds.
History#
Two lists, each reached from the other: Sessions (/aim sessions) and Duel history
(/aim history). Both show the newest rows first.
A session row is one stored solo run: the drill and its kind, the score, rating and difficulty, hits, misses, accuracy, precision, best streak and combo, the average flick and reaction, time on target, the duration, the average ping and the date. A run that set a personal best is drawn with a star.
A duel writes two rows to aim_matches, one per participant, so "my duels" is a one-column query.
Each carries the opponent, whether the player won, the drill, the best-of, the rounds for and against,
the points for and against, the hits, the accuracy, the duration and when it ended. Only a duel that
has a winner writes them; a cancelled duel writes nothing.
history:
entries: 20
retention-days: 30
prune-interval-minutes: 60| Key | Default | What it does |
|---|---|---|
entries | 20 | Rows shown, in each of the two lists. |
retention-days | 30 | Session and duel rows older than this are deleted. 0 keeps everything. |
prune-interval-minutes | 60 | How often the prune runs. Read when the plugin starts. The first duel sweep runs a minute after start, the first session sweep ninety seconds after. |
A sweep looks at the oldest 500 rows of its table and deletes the ones past the cutoff, so a backlog drains over several sweeps rather than one long transaction.
Resetting a player#
From /aimtraineradmin → Players.
Resetting a player goes through ExyliaLib's player reset, narrowed to this plugin. It asks first, then kicks the player and locks them out while it runs (the staff member needs exylialib.admin.wipe). It deletes the player's progress rows: the profile (lifetime numbers, duel record, overall rating and the player's settings) and every drill record, so they leave every board. Session and duel history rows are removed only when the staff member adds history to the reset; otherwise they stay until retention removes them. The leaderboard cache is dropped either way.
Something missing on this page? Tell us on Discord