> For the complete documentation index, see [llms.txt](https://whitepaper.gmr.center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gmr.center/battle-leets/gameplay/mechanics/combat.md).
# Combat
{% hint style="warning" %}
**This whitepaper is outdated:**
We are currently in the process of updating the whitepaper to reflect our most ambitious development phase yet. Stay informed by [signing up](https://gmr.center/sign-up) or joining our [Telegram channel](https://t.me/gmrcenter).
We have kept this version online for informational purposes only.
{% endhint %}
### Win Conditions
Each combat consists of multiple rounds. Each round has a definite timer, that once it runs out, signifies the end of the round. Winning and rewarding victories is done by round, and the match ends after the last round is played. A round will end immediately if any Battle Leet health reaches zero.
Players will attack each other until one Battle Leet health reaches zero. That BattleLeet will lose the match, and rewards will be given to the winning Battle Leet. Alternatively, if the round timer reaches zero, the round winner is the Battle Leet with the highest amount of health.
### Game Space
Combat occurs in a confined, unique space. Within it, players are able to move freely, but not outside the boundaries of the field.
---
# 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.gmr.center/battle-leets/gameplay/mechanics/combat.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.