How kaloou/battlerobot-solo works
BattleRobot-solo is a console-based, networked robot-combat game. A client connects to a hosting server, both players configure robots, then alternate actions until a robot is destroyed or the connection is lost; players can request another match. The shared core supplies robot combat rules, match state, console interaction, and line-based JSON/object and byte transport. Relationships below follow the sampled programs and source references; unsampled project files are not used to infer additional features.
Main entry points: BattleRobot-solo-client/Program.cs Client loop · BattleRobot-solo-server/Program.cs Host loop · Server.cs Server session · Partie.cs Match state
Components 9
Client gameplay
- Client loop
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client connection
BattleRobot-solo/BattleRobot-solo-client/Client.cs
Shared game core
- Player transport
BattleRobot-solo/BattleRobot-solo-core/models/Joueur.cs - Console interaction
BattleRobot-solo/BattleRobot-solo-core/views/Systeme.cs - Match state
BattleRobot-solo/BattleRobot-solo-core/models/Partie.cs - Robot combat
BattleRobot-solo/BattleRobot-solo-core/models/Robot.cs
Server hosting
- Host loop
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Server session
BattleRobot-solo/BattleRobot-solo-server/Server.cs
Other components
- Player
Connections 17
- Player → Client loop: plays through
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client loop → Console interaction: gets input
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client loop → Client connection: connects via
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client loop → Player transport: exchanges messages
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client loop → Match state: updates and displays
BattleRobot-solo/BattleRobot-solo-client/Program.cs - Client connection → Player transport: opens streams
BattleRobot-solo/BattleRobot-solo-client/Client.cs - Client connection → Console interaction: configures robot
BattleRobot-solo/BattleRobot-solo-client/Client.cs - Player → Host loop: plays through
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Host loop → Server session: runs session
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Host loop → Match state: creates match
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Host loop → Robot combat: creates robot
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Host loop → Console interaction: gets input
BattleRobot-solo/BattleRobot-solo-server/Program.cs - Server session → Player transport: exchanges messages
BattleRobot-solo/BattleRobot-solo-server/Server.cs - Server session → Console interaction: gets actions
BattleRobot-solo/BattleRobot-solo-server/Server.cs - Server session → Robot combat: applies actions
BattleRobot-solo/BattleRobot-solo-server/Server.cs - Server session → Match state: sets match status
BattleRobot-solo/BattleRobot-solo-server/Server.cs - Match state → Robot combat: holds robots
BattleRobot-solo/BattleRobot-solo-core/models/Partie.cs