Fastest Times: Race Against the Clock

The Fastest Times leaderboard is built for speed. It tracks completion times in MM:SS.ms format and ranks players from fastest to slowest. Whether you're running speedrun competitions, racing events, or timed challenges, this board type handles time formatting and comparison natively.

How It Works

Scores are submitted as time values (e.g., 1:30.50 for one minute, thirty seconds, and fifty hundredths). The board keeps each player's fastest time — if a new submission is quicker than their current record, it replaces it. Slower attempts are ignored.

Rankings go from fastest (lowest time) at the top to slowest at the bottom. This is the opposite of typical score-based boards, and the bot handles the sorting automatically.

Setting It Up

1. Use the /create command and select Time as the scoreboard type.
2. Name your scoreboard — e.g., "Mario Kart Speedruns" or "Obstacle Course Times".
3. The sort order is automatically set to ascending (fastest time on top). This is handled for you.
4. Set visible ranks as desired.

When submitting times, use the format MM:SS.ms. For example:

• 1:30.00 — one minute and thirty seconds
• 0:45.32 — forty-five seconds and thirty-two hundredths
• 12:05.99 — twelve minutes, five seconds, and ninety-nine hundredths

What It's Good For

• Speedrun competitions — The obvious choice. Track best completion times for any game, level, or category. The time format keeps things consistent and easy to read.
• Racing events — Lap times, race completions, time trials — anything where you're competing against the clock.
• Timed challenges — "Complete this puzzle as fast as possible" or "speedrun this quiz" style events where the clock is the opponent.
• Real-world activities — Running times, cycling laps, cooking challenges, escape rooms — any timed activity your community participates in.

Tips and Best Practices

• Define timing rules clearly. Specify when the timer starts and stops. For speedruns, state whether it's real-time or in-game time. Ambiguity here leads to disputes.
• Require proof for competitive boards. Use a validation channel to require video or screenshot evidence of claimed times, especially for competitive events.
• Use categories. If your game has multiple speedrun categories (Any%, 100%, Glitchless), create a separate board for each rather than mixing them.
• Celebrate improvements. A player shaving 2 seconds off their PB is a big deal in speedrunning culture. Acknowledge these milestones.
• Double-check the format. The most common mistake is submitting times in the wrong format. Remind players to use MM:SS.ms to avoid rejected submissions.

When to Choose Something Else

If your competition is score-based rather than time-based, use High Score instead. If you need cumulative tracking (total time played, for example), a Classic board would work better.