Client Server Architecture

[ThoreKr]

The client and server should be separate models.

• In single player mode the client starts the server as subprocess.
• Server is always authorative and holds the state of the game, the client only displays it
• All events are sent as request to the server and are only valid when confirmed by the server (persisted in the game state)
• plain udp socket connection
• Game state is held in an object, changes are sent to the clients
• each client has an own thread, requests are handled in a queue
• server sends game status updates of the state object to the client
• client-server heartbeats synchronising the hash of the game state
  • server sends hashes of important state information for each client
  • client confirms health state
  • last few (small number/ amount of time) changes are cached an may be reapplied otherwise the whole state is sent again
• the server has an internal "tick" which triggers update for ressource calculation etc.
  • per tick amount x of ressource is produced and player state is updated
  • tick trigger is an element of the main game logic and independent of the client threads

[ThoreKr]

Dokumentation will be added to the wiki