Game Mode First to N Cards

Game mode: First to N Cards

Rules

• No fixed number of questions — the game ends the moment someone collects enough card wins (default 6, host-configurable).
• Questions are drawn and voted on in batches (default 5 at a time, host-configurable), not one at a time and not all at once.
• After each batch is fully revealed, the game checks whether anyone's hit the target; if not, another batch starts.
• If the bank runs out of eligible questions before anyone reaches the target, the game ends anyway — whoever has the most cards at that point wins.

See Core Rules for what applies no matter the mode.

---

In depth

This is the "stop when someone's actually won" mode, closer to how the original tabletop game plays out in practice — except pure round-by-round (one question, whole table votes, repeat) would defeat the point of letting people answer at their own pace. Batching is the compromise: you still move through several questions before waiting on anyone, but the game can still end dynamically instead of running a fixed count.

Batches, not rounds. batchSize (default 5) questions get drawn and opened for voting together, exactly like a Classic Count game would — you answer them at your own pace, and results become available once everyone's answered the whole batch. Only after a batch fully resolves does the game check the win condition and decide whether to draw another one.

Target. targetCards (default 6) — first player to accumulate that many question wins ends the game immediately, even mid-batch-checking (the check happens right after each batch reveals, so the game can't run past the moment someone qualifies).

Bank exhaustion. If the remaining pool of eligible questions (after category filters and excluding ones already used this session) runs dry before anyone hits the target, the game ends anyway rather than stalling forever — whoever has the most cards at that point is declared the winner. This is a deliberate fallback, not a bug: a game shouldn't be able to get stuck because the question pool was too small for the target you set.

Co-winners. Because the win check only happens between batches (not after every single question), it's possible for a batch to push more than one player past the target at the same moment — there's no way to say who "actually" got there first within the same batch. When that happens, everyone who ends the batch with the highest card count among those who cleared the target is declared a joint winner, rather than the app guessing at an ordering it can't actually know.

Good fit for: groups who want a real "winner" instead of just a fixed number of rounds, especially with a bigger question bank where running out isn't a practical concern.