> 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/clans.md).

# Clans

### Overview

**Players can organize in Clans.** Being part of a Clan means:

* Players in the same clan don't engage in combats when hunting. This means that when coordinating hunts, going in packs increases the chance of winning battles and loot more rewards.
* Spillage from hunting on clan's territory is split between the player hunting and the territory owner.
* Players can perform spells and buffs on clan members' territory. Spells casted on a territory change the territory properties and create advantages/disadvantages for the vampires hunting on it. 

### Level Requirements

Players can create a clan starting with level 5 and they can join an already created clan starting with level 3.

### Token Emission

Each time a player spends BLOOD in the game (territory purchase or craft), $DARX is minted and sent to their clan's treasury. 

Each Clan manages their own treasury and decide how the assets in the treasury are distributed to their members. 

<mark style="color:red;">**More about Clans, soon..**</mark>


---

# 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/clans.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.