leaderboard
How many players are ranked per period and how often the cached boards refresh.
leaderboard.yml controls the vote leaderboard behind /vote top
and the top-N placeholders: how many players are ranked and how
often the ranking is rebuilt. The look of the menu itself lives in
guis/leaderboard.yml.
The leaderboard menu. The button at the top switches between Total, Monthly, Weekly and Daily.
The whole file
limit: 14
refresh-seconds: 120| Key | Type | Default | Notes |
|---|---|---|---|
limit | int | 14 | How many players are ranked for each period. |
refresh-seconds | int | 120 | Seconds between background rebuilds of the ranking. Values under 1 are treated as 1. |
The menu has room for 14 entries, so a limit above 14 only matters
for placeholders such as %tdxvoteplus_top_monthly_name_20%.
All four periods (total, monthly, weekly, daily) are always ranked. There is no key to switch one off.
How the cache works
The ranking is not computed when a player opens /vote top. The
plugin keeps the four boards in memory and rebuilds them on a
background thread every refresh-seconds, once at startup and again
on /voteplus reload.
That means:
- Opening the menu and resolving a top-N placeholder never touches the database.
- The boards are up to
refresh-secondsbehind. If you need them fresh right now, run/voteplus refresh. - The monthly, weekly and daily boards only rank players whose count belongs to the current period. A player who last voted in March is not shown on the April board with their March count.
Votes do not arrive fast enough for a short refresh to matter. 120 seconds is a fine default, and 300 is perfectly usable on a busy MySQL setup where you would rather spare the connection.