> For the complete documentation index, see [llms.txt](https://whitepaper.legendofarcadia.io/legend-of-arcadia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.legendofarcadia.io/legend-of-arcadia/gameplay/stands.md).
# Stands
In Legend of Arcadia, the concept of heroes' levels does not exist. Instead, the level of a hero is represented by the level of their stand (inspired by the display stands used for toy figures). This means that any hero placed on a stand will be assigned the level of that stand. The XP that players gain from gameplay is used to level up the stand.
Each player has five stands in the game. As their stands level up, the combat effectiveness of the heroes also increases, enabling them to challenge more powerful players in the Arena and progress towards more difficult chapters in the Adventure and Labyrinth modes.
Notably, players no longer need to focus on growing one or more of their heroes, as in traditional games. Instead, the emphasis is on leveling up the five stands, providing players with greater freedom and space for strategic thinking in the game.
---
# 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://whitepaper.legendofarcadia.io/legend-of-arcadia/gameplay/stands.md?ask=&goal=
```
`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.