> For the complete documentation index, see [llms.txt](https://horizongames.gitbook.io/kronos-matchmaking/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://horizongames.gitbook.io/kronos-matchmaking/usage/reservations/overview.md).

# 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:

<figure><img src="/files/M340zXgWostoUJFZKmJ7" alt=""><figcaption></figcaption></figure>

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**](https://dev.epicgames.com/documentation/en-us/unreal-engine/using-online-beacons-in-unreal-engine). Here is an overview of all the different reservation classes.

<table><thead><tr><th width="345">Class</th><th>Description</th></tr></thead><tbody><tr><td><code>KronosReservationListener</code></td><td>Beacon listening for client connections. This is essentially the server that other clients connect to. Only exists on the server.</td></tr><tr><td><code>KronosReservationHost</code></td><td>Beacon that handles reservations and incoming reservation client connections. Only exists on the server.</td></tr><tr><td><code>KronosReservationClient</code></td><td>Beacon that connects to the reservation host. It requests the reservation and awaits the response. Exists on both the server and the client.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://horizongames.gitbook.io/kronos-matchmaking/usage/reservations/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.