Repository navigation
Categories and Delegation
The question bank is tagged (nsfw, alcohol, criminal, dating,
plus the always-on family-friendly tags like silly, personality,
talent, and so on). In the lobby, the host can exclude any combination
of tags from that session's question pool — excluded content is opt-out,
not opt-in, so a table that doesn't touch anything just plays with
everything included by default.
nsfw specifically is reserved for genuinely adult/explicit content —
sexual history, nudity, that kind of thing. Dating and relationship
content that isn't actually adult in nature lives under dating
instead, so a group that wants to skip romance-themed prompts (for
whatever reason — age, group makeup, whatever) doesn't have to also skip
the actually-explicit stuff, and vice versa.
Bank-size warning. If the categories excluded (combined with the current game mode's question-count needs) would leave too few eligible questions, the lobby shows a warning before the host hits start — computed client-side with the same filtering logic the server uses, so it matches exactly.
What "too few" actually blocks depends on the mode. Classic Count and Deck Mode hard-refuse to start with a clear error the moment the eligible pool can't cover what the mode needs — no partial start. First to N Cards is more lenient by design (see that page's "Bank exhaustion" section): it'll happily start and run with a smaller-than-configured batch size if the pool is merely low, only refusing outright if excluding categories leaves zero eligible questions — starting with literally nothing to vote on is the one case that's never allowed, in any mode.
Two lobby decisions can be handed to the whole table instead of the host picking alone: which game mode to play, and which categories to exclude. Both work the same broad way — the host opens a vote, every player (including the host) submits a private choice, and it resolves automatically once everyone's in (or the host can force an early tally with whoever's voted so far). Settings are locked while either vote is open, and only one of the two can run at a time.
They resolve very differently, though, on purpose:
Mode vote — a normal plurality vote. Whichever mode gets the most votes wins; a genuine tie between modes is broken randomly. This is picking one option for everyone, so majority-style resolution makes sense.
Category vote — not majority-based. Each player privately submits
the set of tags they personally want excluded, and the result is the
union of everyone's picks — if even one person excludes nsfw, it's
excluded for the whole table, full stop. This is a content-comfort
filter, not a popularity contest: the goal is nobody ending up seeing a
category they specifically didn't want, not satisfying the majority at
the cost of the minority. A player who's fine with everything can submit
an empty selection and it simply won't add any exclusions on their
behalf.
Both votes stay completely anonymous the same way regular game votes do — no one sees who picked what, only the final resolved outcome.