> For the complete documentation index, see [llms.txt](https://captain-tsubasa-rivals.gitbook.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captain-tsubasa-rivals.gitbook.io/en/how-to-play-arena/game-flow.md).
# Game Flow
1. **Area Selection**
* Before the start of the turn, the area in which the situation is to be fought will be displayed.
* If it is near an opponent's territory, "FW AREA" will be displayed and the ability of your FW and the opponent's DF will be increased.
2. **Command Input**
* Select the players and commands you want to use in battle.
* Up to two players, including support players, can be selected each turn.
3. **Winning or losing a turn**
* A battle will begin with the player you selected vs. the opponent.
* The player with the higher RP (RivalsPoint) wins.
Repeat turns 1-3 for up to 5 turns.
The winner of the match is determined by the number of wins and losses per turn.
---
# 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://captain-tsubasa-rivals.gitbook.io/en/how-to-play-arena/game-flow.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.