Overview

The reservation system of Kronos ensures that all players who want to join a game will have a free slot in the session at the time of connection. This is important when a group of friends want to join a game together, or when someone with a long loading time attempts to join.

Reservations Structure

Here is a simple overview of what the reservation list look behind the scenes:

Each reservation has an owner and a number of members. The Reservation Owner is the player who requested the reservation. The Reservation Members is a list of players who the reservation was made for (including the reservation owner).

Players who join the game solo will be the owner and the only member of the reservation, while players who join as a party will have all party members in the reservation members list. In the image above for example, you can see that "Player1" and "Player2" were in a party before they joined the game. Meanwhile "Player3" joined the game solo without a party.

Reservation Classes

Reservations are implemented using Online Beacons. Here is an overview of all the different reservation classes.

Class	Description
KronosReservationListener	Beacon listening for client connections. This is essentially the server that other clients connect to. Only exists on the server.
KronosReservationHost	Beacon that handles reservations and incoming reservation client connections. Only exists on the server.
KronosReservationClient	Beacon that connects to the reservation host. It requests the reservation and awaits the response. Exists on both the server and the client.