ARCHITECTURE

This page will describe the architecture of the game integration process with the Genome platform using KODE.

Game

1. Master Server

   • The master server is the central control unit for the game. It coordinates the activities and status of multiple game servers and communicates with platform.

2. Game Servers

   • These servers host the actual game instances. They handle the real-time gameplay and player interactions.

Genome Platform

1. Game API

   • The Game API is the primary interface through which the platform communicates with the game's master server. Connection is carried by WebSockets. The API includes several events:

   • startGame (Game API → Master): Initiates a new match on the master server.

   • gameStarted (Master → Game API): Notifies the platform that a match has successfully started.

   • gameEnded (Master → Game API): Indicates that a match has concluded.

2. Frontend

   • The frontend of the platform is responsible for managing player interactions with platform. One of the key functions shown in the diagram is:

     • Players Linking: This feature allows players to link their nicknames or identities within the platform to their game profiles, ensuring seamless integration and recognition across both platforms.

Communication Flow

• The flow of information begins with the platform's Game API sending startGame event to the game's master to start a match.

• Once the match is initiated, the master manages the distribution of the game instances across the game servers.

• The platform's frontend manages the linkage of player nicknames, ensuring that player identities are synchronized between the platform and the game. Linkage is initiated from game client, as shown on diagram.

• Throughout the gameplay, master notifies Game API about the match states (gameStarted and gameEnded), allowing the platform to monitor and manage game sessions.