TDX LeaderboardsConfiguration
monthly
Reset schedule — monthly, weekly, or biweekly with configurable day and hour.
The monthly block decides when a leaderboard period ends and the next
one begins. Despite the name, it supports weekly and biweekly cycles too.
Quick example
monthly:
reset-period: monthly # monthly | weekly | biweekly
reset-day: 1 # 1st of month, or day of week if weekly
reset-hour: 0 # 0..23, server-local time
announce: true # broadcast a chat message at the moment of resetThat's it. The plugin computes the next reset on every start and on every
/lbadmin reload.
Reference
| Key | Type | Default | Notes |
|---|---|---|---|
reset-period | string | monthly | One of monthly, weekly, biweekly. |
reset-day | int | 1 | Day of month (1–28 safe, 29+ skipped on short months) or day of week. |
reset-hour | int | 0 | Hour of day in server local time, 0–23. |
announce | boolean | true | Broadcast a server-wide message when the period rolls over. |
How "weekly" interprets reset-day
When reset-period: weekly, reset-day is day of week, with Monday as
1 and Sunday as 7 (ISO-8601). So reset-day: 1, reset-hour: 6 resets
every Monday at 06:00 server time.
What happens at reset
In order, on the configured tick:
- The current period's leaderboards are frozen.
- Every player's position on every board is computed.
- Rewards from the
rewardsblock fire (per board, per position). - The frozen period is archived to the
historytable for later lookup. - Counters are zeroed for the new period (only for
DELTAboards;CURRENTandACCUMULATEboards are unaffected). - The optional Discord webhook posts a recap embed.
You can manually trigger this with /lbadmin reset. It's safe to run
outside the scheduled time, but it counts as the real reset for that
period — there's no "test mode."