> For the complete documentation index, see [llms.txt](https://docs.warlands.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warlands.io/whitepaper/gameplay/playability/phase-1.md).

# Phase 1

<figure><img src="/files/FKmzvbZBKX2wUfA2jF4W" alt=""><figcaption><p>This is not final output</p></figcaption></figure>

### Pre Battle Phase

* The game starts with two teams of 5 players each on a waiting island. This island serves as a place where players wait for the actual game to start and for all 10 players to join<br>

* The waiting island could have some basic items and resources for players to gather and prepare for the game.

* During this phase, players can strategize with their team and discuss their plan of attack for the upcoming match. They can also communicate with their team to discuss who will be responsible for unlocking which zones and how they will defend them.


---

# 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://docs.warlands.io/whitepaper/gameplay/playability/phase-1.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.
