> 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/matchmaking/leaving-matches.md).

# Leaving Matches

You can leave a match at any time by using the `LeaveKronosMatch` node. The player will disconnect from the game and the session will be cleaned up automatically. If called on the hosting player, all clients will be gracefully disconnected before closing the game.

There is no hard requirement on where you need to call this from. Most games will probably have this hooked to the `OnClicked` event of a widget button.

{% tabs %}
{% tab title="Blueprint" %}

<figure><img src="/files/X1BYhLJvF4TOyNA9924B" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="C++" %}

```cpp
#include "KronosOnlineSession.h"
```

```cpp
UKronosOnlineSession* OnlineSession = UKronosOnlineSession::Get(this);
OnlineSession->LeaveGameSession();
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
The `OnComplete` event is called when the leave has been requested so at that time the player is still in the match (disconnecting in the next frame).
{% endhint %}


---

# 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/matchmaking/leaving-matches.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.