How cotovsk1/chess-game works
Chess Game is a browser-based platform for bot and real-time multiplayer chess. Players use the web UI to authenticate, start or join a game, make moves, and review results; supporting capabilities include custom FEN starts, clocks, hints, chat, friends, and ratings. The FastAPI routers own the request and WebSocket actions, with shared game logic and in-memory state behind them and SQLite for persistent records. Edges reflect sampled calls or README-described behavior; unsampled details are not inferred.
Main entry points: game.py Bot game API · database.py DB sessions · main.py FastAPI app · models.py Persistent models
Components 16
Web client
- Game UI
frontend
API and identity
- FastAPI app
backend/main.py - Accounts
backend/routers/auth.py - API schemas
backend/schemas.py
Chess gameplay
- Bot game API
backend/routers/game.py - Multiplayer sockets
backend/routers/websocket.py - Chess engine logic
backend/game_logic.py - Live game state
backend/state_manager.py
Social features
- Chat API
backend/routers/chat.py - Friend management
backend/routers/friends.py - Rating calculation
backend/utils.py
Persistence
- DB sessions
backend/database.py - Persistent models
backend/models.py - SQLite database
chess_base.db
Other components
- Player
- Stockfish
Connections 31
- Player → Game UI: uses
README.md - Game UI → FastAPI app: calls API
README.md - FastAPI app → Bot game API: registers
backend/main.py - FastAPI app → Multiplayer sockets: registers
backend/main.py - FastAPI app → Accounts: registers
backend/main.py - FastAPI app → Chat API: registers
backend/main.py - FastAPI app → Friend management: registers
backend/main.py - Bot game API → Chess engine logic: executes moves
backend/routers/game.py - Bot game API → Live game state: stores games
backend/routers/game.py - Multiplayer sockets → Live game state: uses managers
backend/routers/websocket.py - Multiplayer sockets → Chess engine logic: executes moves
backend/routers/websocket.py - Chess engine logic → Stockfish: requests moves
README.md - Accounts → DB sessions: gets sessions
backend/routers/auth.py - Accounts → Persistent models: queries players
backend/routers/auth.py - Friend management → DB sessions: gets sessions
backend/routers/friends.py - Friend management → Persistent models: manages relations
backend/routers/friends.py - Friend management → Live game state: sends notices
backend/routers/friends.py - Chat API → DB sessions: gets sessions
backend/routers/chat.py - Chat API → Persistent models: reads messages
backend/routers/chat.py - Chat API → Live game state: checks game
backend/routers/chat.py - Bot game API → DB sessions: gets sessions
backend/routers/game.py - Bot game API → Persistent models: records games
backend/routers/game.py - Bot game API → Rating calculation: updates ratings
backend/routers/game.py - Multiplayer sockets → DB sessions: opens sessions
backend/routers/websocket.py - Multiplayer sockets → Persistent models: records activity
backend/routers/websocket.py - DB sessions → SQLite database: persists data
backend/database.py - Persistent models → DB sessions: uses base
backend/models.py - Bot game API → API schemas: validates requests
backend/routers/game.py - Accounts → API schemas: shapes responses
backend/routers/auth.py - Chat API → API schemas: shapes responses
backend/routers/chat.py - Friend management → API schemas: shapes responses
backend/routers/friends.py