monthly
The reset schedule. Monthly, weekly or biweekly periods, when each one ends, and what happens at the reset.
The monthly block decides how long a leaderboard period lasts. Despite
the name, it supports weekly and biweekly periods too.
Quick example
monthly:
enabled: true
reset-period: monthly # monthly | weekly | biweekly
broadcast-reset: true # tell everyone online when a period resets
archive-history: true # keep past periods for /leaderboard historyWhen a period ends
The reset follows the calendar, in your server's timezone:
reset-period | Resets at |
|---|---|
monthly | Midnight on the 1st of each month. |
weekly | Midnight every Monday. |
biweekly | Midnight every second Monday (the start of an odd ISO week). |
The plugin checks every five minutes and once on startup, so a reset fires within five minutes of the boundary. If the server was offline when a period ended, the reset runs on the next start instead. Nothing is lost, because the final standings are read from storage.
reset-day and reset-hour are still in config.yml, but they have done
nothing since v1.9.8. The reset happens at the calendar boundary above,
not at a day and hour you pick. From v1.9.19 the countdown in the GUI and
the %tdxleaderboards_reset_time% placeholder count down to that same
moment. Before that they used the two unused settings, so anything but the
defaults showed the wrong time.
Reference
| Key | Type | Default | Notes |
|---|---|---|---|
enabled | boolean | true | Turns the automatic reset on. With false no period is ever closed out on its own. |
reset-period | string | monthly | One of monthly, weekly, biweekly. |
broadcast-reset | boolean | true | Sends the reset messages to everyone online. |
archive-history | boolean | true | Saves each period's final standings so they can be browsed later. |
reset-day | integer | 1 | Not used. See the warning above. |
reset-hour | integer | 0 | Not used. See the warning above. |
What happens at a reset
In this order:
- The final standings of the period that ended are read from storage.
- Rewards from the
rewardsblock are paid. A winner who is offline gets their commands the next time they join. - The standings are archived, if
archive-historyis on. - The Discord webhook posts the results, if it is set up.
- The ended period's data is cleared. Every board starts the new period from zero.
- Players who are online get a fresh starting point on
DELTAboards. Everybody else gets theirs the next time they join.
Rewards and the archive are each marked as done for that period, so a reset that runs twice never pays or archives a second time.
/lbadmin reset confirm is not this. It wipes the current period and
starts it again from zero, with no rewards and no archive. To close out
a past period that was missed, use /lbadmin archive <period> confirm.
See Commands.
A biweekly period is numbered from the ISO week, so a year with 53 weeks ends on a period that is only one week long. 2026 is one of those years: the last period runs from 28 December 2026 to 3 January 2027.