# Validating leaderboard scores by replaying player input on the server: how do you handle timing checks? — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/e82915600868355a

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-11-19 17:00 ingested 2026-11-20 02:36

[original source ↗](https://www.reddit.com/r/gamedev/comments/1y0ejmr/validating_leaderboard_scores_by_replaying_player/)

## retained text



```
I'm working on a small browser game where players type commands in a fake terminal, and it has a global leaderboard. Early on I realised that if the client sends a score, someone will just edit the request.

So the client never sends a score. It sends the list of inputs with timestamps, and the server replays them through the same deterministic game logic to calculate the score itself. If the replay doesn't reach a win, the run is rejected.

That part works well. The tricky part is timing. I reject runs where inputs are impossibly close together, to stop bots that replay a perfect solution instantly. But that creates a few problems:

• Fast typists and people who queue inputs while output is still animating can look like bots

• A patient bot that adds human-like delays gets through anyway

• Clock values come from the client, so they can be faked too



What I'm doing now: a minimum gap between inputs plus a minimum average pace, with timestamps taken when the player presses Enter.

For those of you who've built replay-validated leaderboards (speedrun style, puzzle games, roguelike dailies):

1. Do you bother with timing checks at all, or just accept that determined cheaters will win and focus on stopping the lazy ones?

2. Is there a better signal than input timing for spotting automated runs?

3. Anything you wish you'd known before shipping it?

Also a side lesson for anyone on free tier backends: my database paused from inactivity, failed to restore, and silently broke the board for days before I noticed. A scheduled ping job now keeps it awake.
```



document fetched 2026-11-20 00:26 · canonical https://reddit.com/r/gamedev/comments/1y0ejmr/validating_leaderboard_scores_by_replaying_player
