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

# Legion

<figure><img src="/files/3CyhFg9bC0fPkzQUlVAb" alt="" width="563"><figcaption></figcaption></figure>

## **Assemble your team and become the strongest of the arena!**

Legion is a turn-based tactical PvP RPG where you can assemble and level-up a team of warriors to compete against other players to become the strongest of the arena!

<figure><img src="/files/3sZD4ATuK8brnmqatFRR" alt=""><figcaption></figcaption></figure>

## 🔥 Highlights

> **Turn-based** PvP experience where you control up to 6 heroes capable of moving, attacking, casting spells and using items!
>
> Make your team **stronger** by leveling-up your heroes, providing them with better equipment and teaching them powerful spells!
>
> **Four game modes**: practice, casual, against a friend, or ranked with 5 seasonal leagues to climb the ranks of!
>
> **Impress** the audience of the arena by performing spectacular action for even better rewards!


---

# 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://guide.play-legion.io/legion.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.
