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

# Group

Groups let players team up, protect each other, and coordinate pushes on the map – with built-in trade-offs so alliances don’t break the game.

#### Creating a group

* Invite a player in the same channel.
* If they accept, a group is created automatically and the inviter becomes leader.

#### Rules

* The leader sends invites and can remove members.
* Any player can leave at any time.
* If the leader leaves, leadership passes to another member.
* Each group has a hard cap on the number of players.
* Group members can’t damage each other.
* If you invite an enemy and they join, all active hostilities between you stop.

#### Shared income

* The group has one shared income pool.
* The bigger the group, the less income each member gets.\
  This keeps teamwork useful, but makes oversized “blob” alliances inefficient.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clashofcoins.com/group.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
