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

# Clans

Clans: creation, roles, shared bank, clan levels and bonuses.

File: `plugins/ClickEmCore/modules/clans.yml`. Module id: `clans`. Commands: `/clan`, `/clans`, `/guild`.

A clan is a **shared name and tag, a shared bank, a shared XP track** fed by every member's kills, and a **stat bonus** that grows with clan level and applies to the whole clan. Clan data is stored in `plugins/ClickEmCore/data/clans.yml` (or the database in MySQL mode). The file `clans.yml` in `modules/` holds only settings.

### Player commands

| Command                                                 | Use                                                                  |
| ------------------------------------------------------- | -------------------------------------------------------------------- |
| `/clan create <name...> <tag>`                          | Found a clan. The name may contain spaces, the tag is the last word. |
| `/clan invite <player>`, `accept`, `deny`               | Invites.                                                             |
| `/clan leave`, `kick <player>`                          | Leave or remove.                                                     |
| `/clan promote <player>`, `demote <player>`             | Roles: Member, Officer, Leader.                                      |
| `/clan transfer <player>`                               | Hand over leadership.                                                |
| `/clan motd <text>`                                     | Message of the day.                                                  |
| `/clan open`, `/clan close`                             | Whether anyone can join from the browser.                            |
| `/clan bank deposit <amount>`, `bank withdraw <amount>` | The shared bank.                                                     |
| `/clan browse`, `/clan info [clan]`                     | Look at clans.                                                       |
| `/clan disband`                                         | Leader only.                                                         |

### Settings

| Key                                                      | Default                | Meaning                                                      |
| -------------------------------------------------------- | ---------------------- | ------------------------------------------------------------ |
| `creation-cost`                                          | 25000                  | Coins to found a clan.                                       |
| `new-clans-open`                                         | true                   | Whether a new clan can be joined from the browser.           |
| `name.min-length`, `max-length`, `pattern`               | 3, 16, `[A-Za-z0-9 ]+` | Name rules.                                                  |
| `tag.min-length`, `max-length`, `pattern`                | 2, 5, `[A-Za-z0-9]+`   | Tag rules.                                                   |
| `members.base`, `members.per-level`                      | 10, 2                  | Member cap at level 1 and extra per clan level.              |
| `invite-timeout-seconds`                                 | 120                    |                                                              |
| `leveling.base-xp`, `growth`, `max-level`, `xp-per-kill` | 5000, 1.35, 25, 1      | XP needed for level 2, growth, cap, clan XP per member kill. |
| `bank.allow-withdraw-roles`                              | `[LEADER]`             | Who may withdraw. Anyone can deposit.                        |
| `levels.<n>.bonus`                                       | see below              | Stats for every member at that clan level.                   |
| `autosave-minutes`, `sync-seconds`                       | 5, 5                   | Saving and multi-server sync.                                |

```yaml
levels:
  1:
    bonus:
      currency-mult: 2
  10:
    bonus:
      currency-mult: 10
      damage-mult: 5
      luck-mult: 3
```

The **highest entry at or below** the clan's level applies (they do not add). Use normal [stat keys](/lethium-docs/configuration/stats-and-limits.md).

### Staff commands

`/ceadmin clans disband <clan>`, `/ceadmin clans bank <clan> set|add <amount>`, `/ceadmin clans level <clan> <level>`.

### Placeholders

`%clickem_clan_name%`, `_tag`, `_level`, `_bank`, `_members_count`, `_members_cap`, `_role`, `_leader`, `_motd` and more. See [Progress placeholders](/lethium-docs/placeholders/progress.md).

The clan tag can be put in chat or the tab list with PlaceholderAPI.


---

# 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://lethium.gitbook.io/lethium-docs/gameplay/clans.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.