lila
|
7f56ad89e6
|
feat(api): add WebSocket handlers and game state management
- handleLobbyJoin: validates DB membership and waiting status,
registers connection, tags ws.lobbyId, broadcasts lobby:state
- handleLobbyLeave: host leave deletes lobby, non-host leave
removes player and broadcasts updated state
- handleLobbyStart: validates host + connected players >= 2,
generates questions, initializes LobbyGameData, broadcasts
first game:question, starts 15s round timer
- handleGameAnswer: stores answer, resolves round when all
players answered or timer fires
- resolveRound: evaluates answers, updates scores, broadcasts
game:answer_result, advances to next question or ends game
- endGame: persists final scores via finishGame transaction,
determines winnerIds handling ties, broadcasts game:finished
- gameState.ts: shared lobbyGameStore singleton and timers Map
- LobbyGameData extended with code field to avoid mid-game
DB lookups by ID
|
2026-04-17 15:50:08 +02:00 |
|
lila
|
745c5c4e3a
|
feat(api): add WebSocket foundation and multiplayer game store
- Add ws/ directory: server setup, auth, router, connections map
- WebSocket auth rejects upgrade with 401 if no Better Auth session
- Router parses WsClientMessageSchema, dispatches to handlers,
two-layer error handling (AppError -> WsErrorSchema, unknown -> 500)
- connections.ts: in-memory Map<lobbyId, Map<userId, WebSocket>>
with addConnection, removeConnection, broadcastToLobby
- LobbyGameStore interface + InMemoryLobbyGameStore implementation
following existing GameSessionStore pattern
- multiplayerGameService: generateMultiplayerQuestions() decoupled
from single-player flow, hardcoded defaults en->it nouns easy 3 rounds
- handleLobbyJoin and handleLobbyLeave implemented
- WsErrorSchema added to shared schemas
- server.ts switched to createServer + setupWebSocket
|
2026-04-17 09:36:16 +02:00 |
|