> 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/configuration/stats-and-limits.md).

# Stats and stat limits

The stat system that every module feeds, the keys you use in any yml file, and the hard limits.

Almost every module in ClickEm (pets, gear, upgrades, skills, artifacts, boosts, rebirth, VIP ranks, killstreaks, Echoes, cosmetics, clans and more) gives the player **stats**. The plugin adds them all up into one "stat stack" that combat, payouts, drops and placeholders read from.

Learning the stat keys once lets you edit any of those modules, because they all use the same names.

### The stat keys

Wherever a yml file has a `bonus:`, `stats:`, `stats-per-level:` or similar block, the keys below are valid.

| Key                   | Meaning                                                                             |
| --------------------- | ----------------------------------------------------------------------------------- |
| `damage-mult`         | **Power.** Percent more damage.                                                     |
| `currency-mult`       | Percent more Coins from kills.                                                      |
| `essence-mult`        | Percent more Artifact Essence from drops.                                           |
| `luck-mult`           | Percent better drop chances (Echoes, tickets, fragments, Essence).                  |
| `xp-mult`             | Percent more XP.                                                                    |
| `crit-chance-mult`    | Percent chance to critically hit.                                                   |
| `crit-dmg-mult`       | Percent extra damage on a critical hit.                                             |
| `attack-speed-mult`   | Percent faster auto-attack.                                                         |
| `boss-damage-mult`    | Percent more damage against bosses.                                                 |
| `defense-mult`        | Percent less damage taken from bosses.                                              |
| `max-health-mult`     | Percent more max health.                                                            |
| `health-regen-mult`   | Percent faster health regeneration.                                                 |
| `movement-speed-mult` | Percent faster movement.                                                            |
| `lifesteal-mult`      | Percent of damage dealt returned as health.                                         |
| `vault-mult`          | Percent more of each reward mirrored into Vault (only if you use the Vault mirror). |

There is also a family of **flat** keys. They are plain numbers added on top, not percentages:

`power-flat`, `attack-speed-flat`, `boss-damage-flat`, `health-flat`, `hp-regen-flat`, `defense-flat`, `movement-speed-flat`, `lifesteal-flat`.

Flat stats mostly come from Echo substats and from admin grants. They have no flat version of crit, luck, currency or XP, because those are rates.

{% hint style="info" %}
Damage dealt is `(base damage + power-flat) x damage multiplier`. Base damage is `combat.base-damage` in `modules/mob-rewards.yml`.
{% endhint %}

### How stats combine

Since the Economy v2 rebalance:

* **Power, Coins, Essence and Boss Damage multiply.** Each module counts as one factor. Pets at +300% and gear at +200% give 4 x 3 = 12x, not +500%.
* **Every other stat adds up.** Crit chance from three sources simply sums.

This is what keeps pets and gear growing alongside the mobs' health. When you add a new bonus to a module, remember that on the four multiplying stats a new source is multiplicative and therefore strong.

### Hard limits

`config.yml` has a `limit-stats` section. It is a ceiling on the **total** of each stat after every source is added. Anything above it is ignored: nothing is lost or refunded, the stat just stops rising.

```yaml
limit-stats:
  currency: -1
  damage: -1
  crit-chance: 75
  movement-speed: 50
  movement-speed-flat: 5
```

* `-1` means unlimited.
* Percent stats are in percent (`100` = +100%).
* `crit-chance` is capped because past 100% every hit already crits.
* `movement-speed` and `movement-speed-flat` are capped so players cannot outrun the arena.
* Changes apply live to combat, placeholders, achievements and leaderboards after `/clickem reload`.

### Checking a player's stats

| Where                                          | What you see                                                        |
| ---------------------------------------------- | ------------------------------------------------------------------- |
| `/profile`                                     | Stats button (beacon) with the full total.                          |
| `%clickem_stat_damage%` and friends            | The raw percent. See [Placeholders](/lethium-docs/placeholders.md). |
| `%clickem_stat_damage_multiplier%`             | The same stat as `1 + percent/100`.                                 |
| `/ceadmin stats give <player> <amount> <stat>` | Adds an admin bonus to test with.                                   |


---

# 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/configuration/stats-and-limits.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.
