How algis99/tron works
This is a first-draft multiplayer Tron game: a player connects, receives an initial game state, issues serialized commands, and receives state updates for rendering. The backend manages connections and a game session that parses commands and applies actions to a world; shared protocol and structures support the client/server exchange. The README mentions shooting, though it describes it as a TODO; the action/parser and client command modules indicate partial shooting support. Some runtime links are based on the SOURCE INDEX rather than sampled implementation excerpts.
Main entry points: Client.cs Client · GameSession.cs Game Session · structures Shared State Models · GameManager.cs Game Manager
Components 22
Player Client
- Client
frontend/src/Client.cs - Game Manager
frontend/src/manager/GameManager.cs - Client Game
frontend/src/game/Game.cs - Commands
frontend/src/commands/Command.cs - Command Serializer
frontend/src/serializer/CommandSerializer.cs - Renderer
frontend/src/game/Renderer.cs - Grid Drawers
frontend/src/drawers/GridDrawer.cs
Game Server
- Server
backend/src/Server.cs - Game Session
backend/src/session/GameSession.cs - Command Lexer
backend/src/parser/Lexer.cs - Command Parser
backend/src/parser/Parser.cs
Shared Runtime
- Client Connection
shared/src/protocol/ClientConnection.cs - Packet Sender
shared/src/protocol/PacketSender.cs - Packet Receiver
shared/src/protocol/PacketReceiver.cs - Shared State Models
shared/src/structures - Thread-Safe Queue
shared/src/queue/ThreadSafeQueue.cs
Game Domain
- Game Engine
backend/src/game/Game.cs - World
backend/src/game/World.cs - Player State
backend/src/game/Player.cs - Game Actions
backend/src/actions/GameAction.cs - Action Results
backend/src/results/GameActionResult.cs
Other components
- Player
Connections 28
- Player → Client: starts
- Client → Game Manager: creates
frontend/src/Client.cs - Client → Packet Receiver: receives state
frontend/src/Client.cs - Client → Packet Sender: sends commands
frontend/src/Client.cs - Client → Shared State Models: exchanges state
frontend/src/Client.cs - Game Manager → Client Game: runs and updates
frontend/src/manager/GameManager.cs - Game Manager → Command Serializer: serializes commands
frontend/src/manager/GameManager.cs - Game Manager → Thread-Safe Queue: uses queue
- Client Game → Renderer: renders
frontend/src/game/Game.cs - Client Game → Commands: creates
frontend/src/game/Game.cs - Client Game → Thread-Safe Queue: queues commands
- Renderer → Grid Drawers: delegates drawing
frontend/src/game/Renderer.cs - Renderer → Shared State Models: renders state
frontend/src/game/Renderer.cs - Server → Game Session: runs session
backend/src/Server.cs - Server → Client Connection: manages connections
backend/src/Server.cs - Server → Shared State Models: broadcasts state
backend/src/Server.cs - Game Session → Command Lexer: tokenizes commands
backend/src/session/GameSession.cs - Game Session → Command Parser: parses commands
backend/src/session/GameSession.cs - Game Session → Game Engine: submits actions
backend/src/session/GameSession.cs - Game Session → Shared State Models: returns game state
backend/src/session/GameSession.cs - Command Parser → Game Actions: creates actions
backend/src/parser/Parser.cs - Game Engine → World: updates world
backend/src/game/Game.cs - Game Engine → Game Actions: dispatches actions
backend/src/game/Game.cs - Game Engine → Action Results: produces results
backend/src/game/Game.cs - World → Player State: tracks players
backend/src/game/World.cs - World → Shared State Models: uses grid and positions
backend/src/game/World.cs - Client Connection → Packet Sender: sends packets
shared/src/protocol/ClientConnection.cs - Client Connection → Packet Receiver: receives packets
shared/src/protocol/ClientConnection.cs