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

# Gameplay

In VRMARS Mobile, players take on the challenge of building and defending their very own colony on the Red Planet, Mars. With a starting point of an essential colony, players have the opportunity to grow and expand their settlements through the acquisition of new NFTs or battles against other players. The game offers a diverse range of structures each with its own unique strengths and weaknesses. 

{% hint style="success" %}
**To succeed in VRMARS, players must carefully manage their resources and make strategic decisions to gain an advantage over their opponents.** 
{% endhint %}

Players can build and defend their colonies on a simulated Mars. With a wide range of opportunities for exploration, building, and defense, VRMARS mobile offers players an engaging and enjoyable experience.


---

# 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://vrmars-3.gitbook.io/vrmars/vrmars-mobile/gameplay.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.