> For the complete documentation index, see [llms.txt](https://gainhive.gitbook.io/gainhive-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gainhive.gitbook.io/gainhive-whitepaper/gameplay/combat-system.md).
# Combat System
**Inspirations**
The combat system of the GainHive is inspired by the Civilization VI series combat system.
The key inspirations are:
● The attacker and the defender are not on the same tile. An attack always happens from a tile to a different tile.
● Combats do not immediately result in defeat. To an enemy combatant to be defeated it might require more than one attack.
### Overview
● An attacker avatar is an avatar that tries to move into an “enemy” occupied tile. If this is the case the combat starts.
● In combat there is randomness but most of the outcome will be determined by the avatar statistics.
● Attacking consumes energy. Each attack consumes 1 energy.
● Attacking has no cooldown.
---
# 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://gainhive.gitbook.io/gainhive-whitepaper/gameplay/combat-system.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.