> For the complete documentation index, see [llms.txt](https://gyrosstudios.gitbook.io/gyrosstudio-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gyrosstudios.gitbook.io/gyrosstudio-gitbook/gyros-studios-developments/arsenal/clans.md).
# Clans
To enhance gameplay and fun, Arsenal implemented a clan system. Every gamer can set up his own clan and add members. Creating a clan costs 1500 WELT.
Below are the main features:
• Clan Scores \
• Clan Rankings \
• Clan Description/Information \
• Clan Privacy \
• Customized Clan Menu \
• Clan Invitation \
• Membership Request \
• Members Roles (Leader, Officer, Commander, etc.…) \
• Clan Search \
• Clan Tags \
• Kick Option \
• Player Filter
Clans can organize tournaments internally. The tournament settings can be set by the organizing clan like map, game mode, max players, entry fee, prize pool, house %, etc. Clans and their members can be recognized throughout Arsenal via name tags, profile pictures, and weapon camos.
---
# 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://gyrosstudios.gitbook.io/gyrosstudio-gitbook/gyros-studios-developments/arsenal/clans.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.