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

# Game Mechanics

**Real-world map:** The game's map is based on the real world, featuring actual cities and their respective populations, adding depth and authenticity to the gameplay. 

**Territory NFTs:** Players pick hexagons on the map, which they can mint as unique territory NFTs, representing their control over specific areas. 

**Scarce territories:** High populated cities have limited available territories due to their surface area, increasing the value and competition for these sought-after locations. 

**Raw materials & Crafting:** Territories generate resources that players use to craft items and enhance their vampire characters, facilitating growth and development. 

**Clans and alliances:** Players can join Clans, working together to send their vampires on hunts and organizing high-stakes tournaments for collective rewards. 

**Rank growth:** As players participate in battles and engage in gameplay, they earn Rank Points, allowing them to grow their ranks and achieve higher levels of power and influence in the game world.


---

# 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.vampirewars.io/the-game/game-mechanics.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.