> 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/party/leaving-parties.md).

# Leaving Parties

You can leave a party at any time by using the `LeaveKronosParty` node. All cleanup processes are handled automatically, such as disconnecting from the host and cleaning up the session state.

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/2AyNRvXTL3x2KQyL2Ujn" alt=""><figcaption></figcaption></figure>
{% endtab %}

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

```cpp
#include "KronosPartyManager.h"
```

```cpp
// Get the party manager.
UKronosPartyManager* PartyManager = UKronosPartyManager::Get(this);

// Begin leaving the party. The player will disconnect from the party
// immediately, but it may take a second for the session to be destroyed.
PartyManager->LeaveParty();
```

```cpp
// Optionally, a delegate can be passed in which will be executed once the
// party session was destroyed. The function should look like this:
// MyFunction(FName SessionName, bool bWasSuccessful)
FOnDestroySessionCompleteDelegate CompletionDelegate = FOnDestroySessionCompleteDelegate::CreateUObject(this, &ThisClass::MyFunction);
PartyManager->LeaveParty(CompletionDelegate);
```

{% endtab %}
{% endtabs %}


---

# 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/party/leaving-parties.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.