How abishek2429/codexcape works
CodeXcape is a centrally authoritative, two-player technical escape-room game: players log in separately, cooperate through six puzzle levels, and earn clue fragments toward a server-verified final passkey. The browser provides player and organizer interfaces; the Express backend owns sessions, progression, scoring, hints, security, and live updates, persisting state in PostgreSQL. Organizers manage events and teams and monitor results. The README documents the major capabilities; some detailed service-to-route wiring is unsampled, so those links are omitted or marked unverified.
Main entry points: playerRoutes.js HTTP API routes · repositories Repositories · PlayerGamePage.tsx Player game UI · questionAnswerService.js Game progression
Components 23
Player experience
- Player game UI
frontend/src/pages/player/PlayerGamePage.tsx - Player login
frontend/src/services/playerAuthService.ts - Game API clients
frontend/src/services - Live sync client
frontend/src/hooks/useGameWebSocket.ts
Game engine
- Player sessions
backend/services/playerSessionService.js - Game progression
backend/services/questionAnswerService.js - Game state
backend/services/gameStateService.js - Scoring
backend/services/scoringService.js - Hints and riddles
backend/services/hintService.js - Story sequences
backend/services/cinematicStoryService.js - Final passkey
backend/services/finalPasskeyService.js - Anti-cheat
backend/services/antiCheatService.js
Organizer operations
- Organizer console
frontend/src/pages/admin/AdminDashboardPage.tsx - Admin routes
backend/routes/adminRoutes.js - Event and team controls
backend/services/admin/adminDashboardService.js - Rankings and results
backend/services/admin/leaderboardService.js
Backend platform
- HTTP API routes
backend/routes/playerRoutes.js - WebSocket updates
backend/services/webSocketService.js - Database pool
backend/config/db.js
Persistent data
- Repositories
backend/repositories - PostgreSQL
Other components
- Two players
- Organizers
Connections 27
- Two players → Player game UI: play through
README.md - Player game UI → Player login: authenticates with
- Player game UI → Game API clients: requests game data
- Game API clients → HTTP API routes: calls
- HTTP API routes → Player sessions: routes sessions to
backend/routes/playerRoutes.js - Player sessions → Repositories: reads and updates
backend/services/playerSessionService.js - HTTP API routes → Game progression: routes answers to
backend/routes/playerRoutes.js - Game progression → Scoring: uses scoring
backend/services/questionAnswerService.js - Game progression → Game state: uses game state
backend/services/questionAnswerService.js - Game progression → Repositories: reads and updates
backend/services/questionAnswerService.js - HTTP API routes → Hints and riddles: routes hint requests
backend/routes/playerRoutes.js - HTTP API routes → Story sequences: routes story requests
backend/routes/playerRoutes.js - HTTP API routes → Final passkey: routes passkey requests
backend/routes/playerRoutes.js - HTTP API routes → Anti-cheat: routes security events
backend/routes/playerRoutes.js - Player game UI → Live sync client: subscribes to updates
- Live sync client → WebSocket updates: syncs over WebSocket
frontend/src/hooks/useGameWebSocket.ts - Player sessions → WebSocket updates: notifies event start
backend/services/playerSessionService.js - Organizers → Organizer console: manage events
README.md - Organizer console → Admin routes: uses admin API
- Admin routes → Event and team controls: routes event controls
backend/routes/adminRoutes.js - Event and team controls → Repositories: reads and updates
backend/services/admin/adminDashboardService.js - Event and team controls → WebSocket updates: publishes live status
backend/services/admin/adminDashboardService.js - Admin routes → Rankings and results: routes results
- Rankings and results → Repositories: reads ranking data
backend/services/admin/leaderboardService.js - Rankings and results → WebSocket updates: notifies rank changes
backend/services/admin/leaderboardService.js - Repositories → Database pool: queries through
backend/repositories/teamRepository.js - Database pool → PostgreSQL: reads and writes
backend/config/db.js