Panel setup
Assign one channel
/leaderboards set channel:#leaderboardsLuminox creates the index, publishes every enabled ranking in order and repeats the index at the end. Reusing the command updates the configured destination without deleting leaderboard data.
Available boards
What the leaderboard suite tracks
| Board | Measures | Window |
|---|---|---|
| Top Level | Character level and recent position movement. | Current snapshot |
| Loyalty Points | Account Loyalty Level and total points. | Permanent balance |
| GuildBank Contributions | Confirmed account contribution. | Stored total |
| Level Gains | Verified character level gains. | Last 30 / 365 days |
| Deaths | Verified character deaths. | Last 30 / 365 days |
| Hours Played | Observed online time from existing online snapshots. | Last 30 / 365 days |
Display
Compact lines, clickable names and safe pagination
- Every entry starts with its numeric position.
- Registered characters link to the associated Discord account; other characters link to Tibia.com.
- Vocation and level remain outside the link for consistent formatting.
- Long rankings continue in as many messages as required instead of being truncated.
- Continuation messages include Go to top; the channel also contains an index at both ends.
- Top Level shows position movement instead of repeating the level already visible in the character block.
Time windows
Monthly and yearly mean rolling periods
Monthly boards use the last 30 days and yearly boards use the last 365 days. Entries naturally leave the ranking when they move outside the active window.
Hours played reuses online-session observations already collected by Luminox. It does not create an extra Tibia request for each ranking entry.
Data ownership
Use the correct identity for each metric
Refresh
Automatic updates at the selected plan speed
Leaderboard presentation follows the cached-panel policy: five minutes on Free, three on Core, two on Growth and one on Scale or Founder. Each source metric still follows its own eligible collection schedule. Use /install refresh after changing panel configuration; use /update-all only when a Community administrator intentionally wants a registered-character refresh.