Stats for
Nerds

The frontend is only the interface. It renders tickets, animates numbers and collects taps — nothing more. Every decision that matters happens elsewhere.

The backend is the heart of the game. It owns game state, calls the numbers, generates and validates tickets, resolves claims and determines winners. If the browser closed mid-game, the game would carry on without it.

Players never decide whether a number was called or whether a claim is valid. Actions travel inward to the engine; results travel outward over WebSocket to every connected player at once.

Every player receives three generated ticket choices before entering the game lobby. They pick one; the selection is persisted server-side and becomes the only ticket that can ever win for them.

REST APIs handle deliberate player actions — creating and joining rooms, starting games, claiming Housie. Each is a request with a definite answer.

WebSocket over STOMP handles everything that happens on its own schedule. The server broadcasts events; clients only react.

Current winning methods

1. 01Early Five
2. 02Top Line
3. 03Middle Line
4. 04Bottom Line
5. 05Full House

PostgreSQL stores everything required to keep a game alive across reconnects and restarts. Ticket matrices are stored as JSONB.