Game On, No Matter What
Game On, No Matter What
By default, a game that hasn’t hit quorum by the start of the last hour is cancelled automatically. Game on, no matter what is the host’s opt-out from that rule.
With it turned on, the game happens no matter how many players are in — even if only the host shows up.
Who controls it
Only the host. No one else can flip this setting.
When it can be turned on or off
The host can toggle this any time before the last hour starts — that’s up to 1 hour before kick-off.
Once the last hour has begun, the setting is locked. Whatever it was at that moment is what the game runs with.
A special case: creating a game inside the last hour
If you create a brand new game whose kick-off is already inside the next hour, Furbol automatically turns on game on, no matter what — and you can’t turn it off. The reasoning: by the time you’re setting up a game one hour out, there’s no time for a proper quorum to form, and the normal auto-cancel rule would just kill the game on arrival.
What it changes at the start of the last hour
Two things differ from a normal game:
- The game is not cancelled if it hasn’t hit quorum. It stays alive.
- Unconfirmed players are still released. The “if you haven’t confirmed, you’re released” rule from the last hour still applies — game-on mode doesn’t freeze your roster, it only guarantees the game itself happens.
A nuance for game-on mode
Once a game is past the start of the last hour in game-on mode, Furbol doesn’t re-cancel it if the number of confirmed players drops again. The roster can shrink during the last hour without killing the game a second time.
The one thing that still cancels it: a totally empty roster at the end
Game-on guarantees the game happens when someone is there. But if a game-on game reaches its finish time with zero players on the roster — not even the host booked into it — Furbol quietly cancels it after the fact. You won’t see it sitting as a played-but-empty ghost in anyone’s history. In practice this only happens to games hosts forgot to self-book and no one else joined, so the effect is invisible cleanup rather than a user-facing event.