Repository navigation
Core Rules
These hold regardless of game mode or any admin option — nothing on this page is configurable.
No one ever sees who voted for whom — not other players, not the host, not even after the game ends. The server stores each vote's target internally (it has to, to tally correctly and stop double-voting), but no API response or realtime event ever includes another player's individual choice. What everyone sees once a question is revealed is the aggregate count per person and who won — never the breakdown of who cast which vote. There's no "guess who voted for you" feature and there never will be; it's a deliberate difference from the physical game, not an oversight.
- You can't vote for yourself.
- You can change your answer on any question right up until that question (or its batch) is tallied — submitting again just overwrites your previous pick. In Deck Mode, changing your answer releases the vote-card you'd used, so you're not penalized for reconsidering.
- Abstaining is always allowed when you have no valid target left — this can never be turned off by the host, in any mode, under any setting. It only actually comes up in Deck Mode (see that page), but the rule itself is universal: forced abstention because there's no one left to vote for is never something a host can disable.
A question's card goes to whoever got the most votes on it. If nobody voted for anyone (everyone abstained), no card is awarded. A genuine tie for the top spot is resolved by whichever tie-break method the host configured — that part is configurable, just not the underlying "most votes wins" mechanic itself.
- 3 players minimum to start a game. There's no maximum enforced by the app itself.
- Anyone can join a session in its lobby up until the host starts it — once voting begins, the player list is locked for that game.
Every player shows up with a small colored icon next to their display name — in the lobby, the standings bar, vote-target buttons, tie-break prompts, and results. It's generated deterministically from that player's id for this session (same icon every time you see them during this game), purely so a row of similar-sounding names is easier to tell apart at a glance while voting. It's derived from the session-scoped player record, not your account — it doesn't persist across different games, and it doesn't add any new information beyond what your display name already shows. Doesn't interact with the anonymity guarantee above at all; it's just a visual stand-in for the name that's already fully visible.
Every game moves through the same three states regardless of mode: Lobby (host configures settings, players join) → Voting (batches of questions get answered, revealed, and tallied) → Completed (final standings, results browsable in whatever reveal style was chosen). There's no going back a stage.
Every question comes from a shared, pre-written bank (not generated per-game) — see Categories and Delegation for how categories can be filtered per session. Within one session, the same question never repeats.