Using TD LeaderBoard
Mod version shipped with FlammiCraft: 1.18.0
TD LeaderBoard displays vanilla player statistics, not account balances. Install compatible client/server builds and their libraries.
Connection checks require matching payload channels and protocol 5. They do not compare release numbers or JAR contents; use the same build on both sides.
Select a ranking
- Hold TAB for the compact list or run
/tdleaderboardfor the full view. - Choose a category and sort metric; selecting a metric also enables its column.
- Select all-time, current calendar week or current calendar month.
- Enter a name fragment and use Search/Enter. To me clears the search and locates your rank.
- Open a player row for its detail snapshot. Return to the ranking and reopen it for fresh details.
With TDLibrary database storage enabled, statistics are shared by UUID and the leaderboard can show players online on other backends. New offline UUIDs require readable vanilla statistics and a name. In database mode, the importer checks TDLibrary's shared player name history when the name is missing locally. Play time includes AFK time, and mob kills include non-hostile mobs. Weeks begin Monday 00:00 UTC and months on the first day. Period tracking counts increases from the start of measurement.
Shared database and cluster
Updated TDUtilities 1.29.0 builds on clients and every backend also synchronize WATUT AFK flags. The leaderboard can render them by UUID for remote players without local TAB entries. Existing AFK display settings continue to apply; visible cross-backend icons require manual acceptance.
Requires TDLibrary 0.74.0 or newer on both sides. On every backend, enable [database] and [cluster] in config/tdlibrary-database.toml, use the same MariaDB target and set a unique id in cluster-node.toml. Update TD LeaderBoard on all backends so they publish current session data. The reference explains initialization, polling, backups and failure recovery. All-time, weekly and monthly rankings use shared database values. Shared period tracking starts with the first database observation. Local period history is retained separately.
Automated tests cover progress calculations, retries, period rotation and recovery. Live Minecraft transfers between mining and Nether backends, database outages and server restarts still require manual acceptance.
Place a world board
Both boards require two blocks of width, four of height and solid support under both base positions. They have no crafting recipe and are available in Creative Functional Blocks.
Operators or the singleplayer host right-click to choose a metric and optional title of up to 48 characters, then save with Done. Ordinary players right-click to open the full leaderboard. World boards always display their all-time metric, independent of personal screen periods.
Breaking any part removes the whole structure and returns one fresh item; the prior board settings are not stored in that drop.
Reset shared statistics
Operators with permission level 4 and the server console can reset one player or everyone, including offline players. Update every backend before using the reset commands.
Display settings and troubleshooting
Client columns and sorting use config/tdleaderboard-client.toml. Small windows may show a resize hint or vanilla TAB fallback; no fixed GUI scale is required.
Version 1.12.0 restores optional AFK icons with the current TDUtilities status renderer while retaining older supported managers. An inactive integrated module or standalone WATUT keeps the normal status symbols. Automated tests cover API resolution; visible AFK icons in TAB and the full view still require manual in-game acceptance.
For absent offline names inspect import status, the local profile cache and, in database mode, TDLibrary's shared name history. For unexpected period values inspect measurement start and UTC boundaries. For local storage, back up data/tdleaderboard_periods.dat with the world. In database mode back up the leaderboard tables together and retain each world's pending statistics outbox. See the reference for recovery and earlier preview schemas.
Player names use the latest recorded observation. An empty name history supplies no name.