Connection and account
Signing in takes an internet connection. The installed apps keep running on your own network after that, but a race you want ranked needs the connection live at the green light. GhostGaugeWeb always uses the Internet.
If an installed app loses its connection mid-race — router reboot, Wi-Fi dropout, your ISP having a day — it keeps recording. The finished race stays on your device and uploads when the connection returns.
Why an account at all? Because every number on this site is re-checked before it counts, and a check has to know whose number it is. There is no anonymous leaderboard, because an anonymous leaderboard is a list of claims.
Signing in
Sign-in is through Patreon or Discord. You can connect both methods to one GhostGauge account. There's no GhostGauge password — we never see one and never store one. We keep each provider's account identifier, plus the email address and display name for your primary sign-in.
Your Patreon name stays private. The only name anyone else sees is the Race Driver name you declare yourself.
How old you have to be
You must be at least 13 to create an account.
Account access
A signed-in account can use race history, comparison, publishing, clubs and leagues. Publish all is the default for every user, including confirmed races already in your history. You can unpublish individual races in My Races. Sporting rules, identity checks and moderation still apply.
Each new club and each new league needs krasnal's explicit approval. Approval for one does not authorize creating another. Once approved, its organizer manages it under the normal permissions.
If a League owner deletes their account, the League stays intact and ownership transfers to krasnal, who appoints the next owner manually.
The installed apps can run signed out and keep local recordings. Sign in through Patreon or Discord to use your account history.
Before a time reaches a board
Every time you can see on a board has cleared all four.
- You were online when it started. At the green light the app asks our server for a ticket for that race. No ticket, no board.
- The times recompute. We drive your race again on our side, from the whole recording rather than a summary of it, and work the time out from scratch. It has to match what the app reported. That is the whole of the check — it says nothing about how you drove.
- It is published. Confirmed races are published automatically by default. Explicitly unpublished races stay unpublished, and you can pull a race back from My Races.
- You've declared a Race Driver name. A board without names on it is a spreadsheet.
Lose your connection mid-race and the ticket was already issued. The race still counts, and carries a flag so the board is honest about what happened.
Races recorded while you were offline still upload, and still feed your history, your distance, your crowns and titles. They can't rank.
Where the finish time comes from
Forza doesn't hand out a finish time, so we calculate one — it can land within +/- 1 ms of what the game's results screen shows.
The flags, in words
- Connection dropped — you lost us partway through. The time still counts, and the flag is shown beside it on the board.
- Uploaded late — this one waited in the queue and came in when you got signal back. Counts.
- No ticket — the race started while you were offline or before this device was linked. It's yours, it's in your history, it can't rank.
- Times didn't match — our replay worked out a different time from the one reported. It stays in your history and off the board.
And how we race
The driving half is the one we can't enforce with code.