> For the complete documentation index, see [llms.txt](https://wiki.aero-revolution.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.aero-revolution.com/pvp-and-woe/tournament.md).

# Tournament

Organized team battles with gear restrictions.

The **Tournament** NPC (Prontera 147, 166) runs team battles: **3v3, 7v7, 12v12, and 16v16**, each in its own arena. Sign up solo or, as a party leader, queue your whole online party for Team Red or Blue. The match starts 10 seconds after both teams fill.

**Gear is restricted** — only whitelisted NPC equipment plus ammo is allowed; **no MVP cards and no rare-MVP cards** (normal cards and costumes are fine). Gear is checked at sign-up and again before the match, and equipment is locked during the fight.

Matches are 10 minutes; the team with the most players alive wins. One character per IP; leave with **`@leaveevent`**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.aero-revolution.com/pvp-and-woe/tournament.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.