> For the complete documentation index, see [llms.txt](https://partyicons.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partyicons.gitbook.io/wiki/gameplay/party-heist.md).

# Party Heist

Party Heist is a fast-paced, surprise-filled multiplayer looting and extraction mode. Players compete in teams of four, working together to loot, fight, and extract. Each match lasts approximately 12–20 minutes.

### Primary Objective

Defeat NPCs and enemy players on the battlefield, collect valuable resources, and MOST IMPORTANTLY successfully extract to secure your Loot.

### Key Challenge

Players must strike a balance between risk and reward by selecting the right equipment and strategy to outlast others in high-risk scenarios.

Players can determine their total equipment value based on the selected session tier. Both NPC difficulty and Loot value vary by battlefield. Below are the two available modes for Party Heist:

#### Mask Mode

The EKKO AI fights on behalf of the player.

#### Marauder Mode

Players personally control their heroes in battle.


---

# 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://partyicons.gitbook.io/wiki/gameplay/party-heist.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.