Stats
The /le stats command provides sub-commands to consult statistics at different levels, plus a resetProgress sub-command to wipe statistics and progression.
/le stats player [playerName]â
Displays the global statistics of a player across all puzzle areas.
| Permission | None (own stats) / lasers.admin (other player) |
| Console | â Not available without playerName argument |
Argumentsâ
| Argument | Required | Description |
|---|---|---|
playerName | No | Name of the player to look up. If omitted, displays the sender's own stats. |
Examplesâ
/le stats player â own stats (in-game only)
/le stats player Steve â Steve's stats (admin only)
/le stats serverâ
Displays aggregated statistics for the entire server.
| Permission | lasers.admin |
| Console | â Available |
Exampleâ
/le stats server
/le stats area [id]â
Displays an aggregated summary for a specific puzzle area: total players, total victories, total entries, and the top holder for every area-scope ranking criterion (best time, fewest steps, most victories, etc.).
| Permission | None |
| Console | â Not available without id argument |
Argumentsâ
| Argument | Required | Description |
|---|---|---|
id | No | ID of the area. If omitted, resolves the area from the sender's current position. |
Examplesâ
/le stats area â summary for the area at your current position
/le stats area 42 â summary for the area with id 42
/le stats arearanking <criteria> [id]â
Displays the top 10 players on a specific puzzle area for a single ranking criterion. The output matches what an in-world Leaderboard component would show for the same criterion.
| Permission | None |
| Console | â Not available without id argument |
Argumentsâ
| Argument | Required | Description |
|---|---|---|
criteria | Yes | Ranking criterion to display the top 10 for. Must be an area-scope criterion (e.g. RECORD_DURATION, RECORD_NB_STEPS, NB_VICTORIES). See the Leaderboard component for the full list. |
id | No | ID of the area. If omitted, resolves the area from the sender's current position. |
Examplesâ
/le stats arearanking RECORD_DURATION â top 10 fastest in the area at your current position
/le stats arearanking NB_VICTORIES 42 â top 10 by number of wins on area 42
/le stats resetProgress <variant>â
đĄ Looking for "erase everything about me"? That is
/le progress resetbelow â the same operation asallAreasForPlayer, under the name people actually try.
Wipes statistics and progression. Unlike the read-only sub-commands above, this deletes data: per-area records and victories, global counters, obtained keys and bonuses, achievements, anything a companion plugin remembers about the player, and â when a whole player is reset â their checkpoints. Player inventories and active race participation are always preserved.
A companion plugin (the play server's, for instance) keeps its own database, which Lasers-Enigma cannot reach into. Such a plugin declares what it holds through the achievements API, and every reset then asks it to clear that too â so the reset is complete without either plugin knowing the other's schema.
Resets are recalculation-based: the global and server-wide aggregates are recomputed from the remaining data, so they stay consistent.
| Permission | lasers.admin, except allAreasForPlayer / playerForArea on yourself, which need none at all |
| Console | â Available (a player name is then required for the player-scoped variants) |
The destructive variants ask for confirmation: re-run the command with the literal
keyword confirm appended. That keyword is never tab-completed.
Variantsâ
| Variant | Scope | Confirmation |
|---|---|---|
allPlayersForArea <areaId> [confirm] | All players in one area | Required |
allAreasForPlayer <playerName> [confirm] | One player, across all areas (incl. checkpoints) | Required |
playerForArea [<playerName>] [<areaId>] | One player in one area | Not required (limited impact) |
allPlayerForAllArea [confirm] | Every player in every area (incl. checkpoints) | Required |
For playerForArea, an omitted playerName targets yourself and an omitted areaId
resolves to the area at your current position. Checkpoints are cleared only by the two
whole-player variants, because checkpoints are stored per world, not per area.
Examplesâ
/le stats resetProgress allPlayersForArea 42 confirm â wipe everyone's progress in area 42
/le stats resetProgress allAreasForPlayer Steve confirm â wipe all of Steve's progress
/le stats resetProgress playerForArea â wipe your own progress in the current area
/le stats resetProgress allPlayerForAllArea confirm â full server-wide wipe
/le progress reset [player] [confirm]â
The same thing as stats resetProgress allAreasForPlayer, with the player defaulting
to whoever types it. Erasing your own progress is the common case and should not
require finding it under stats, nor typing your own name.
| Permission | none on yourself, lasers.admin for anybody else |
| Console | â Available (a player name is then required) |
Erasing your own progress asks for no permission, deliberately: it is your own record, nobody
else's, and no other account is touched. The confirm keyword is what guards against the slip â a
permission would only have guarded against the intent, and would have left the people most likely to
want a clean slate needing to find an administrator to throw away their own data.
Run it once to be told what will go â statistics, bonuses, keys, checkpoints, and how
many achievements â then again with confirm to do it.
/le progress reset â what wiping your own progress would erase
/le progress reset confirm â erase it
/le progress reset Steve confirm â erase Steve's (admin)
The long form keeps working; nothing about it changed.
âšī¸ The area statistics menu's clear button performs the same operation as
allPlayersForAreaâ it now also clears keys and bonuses for that area, not just its statistics.
See alsoâ
- Stats concept â understanding what each field means