> For the complete documentation index, see [llms.txt](https://robohero.gitbook.io/robohero-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robohero.gitbook.io/robohero-wiki/command-center/gameplay/turns-system.md).

# Turns System

{% hint style="info" %}
RoboHero is turn-based strategic game. Players' turns follow one after the other.
{% endhint %}

### Player Turn

During a player's turn, they have full control over their robot and drone, allowing them to perform various actions without the restrictions of separate phases. All available actions can be executed in any order, providing flexibility in gameplay strategy.

{% hint style="info" %}
**During a turn, players can:**

* **Move the drone** and position it strategically on the battlefield.
* **Move the robot** across the hexagonal grid to gain a tactical advantage.
* **Use support or defensive skills** to protect or enhance their robot and drone.
* **Acquire buildings** on the map
* **Use offensive skills** to attack opponents or drones.
* **Engage the opponent** in direct combat from the current position.
  {% endhint %}

Each action during the turn consumes energy, and players must manage their energy levels carefully to maximize their effectiveness in battle.

[← Back to Gameplay](/robohero-wiki/command-center/gameplay.md)


---

# 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://robohero.gitbook.io/robohero-wiki/command-center/gameplay/turns-system.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.