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

# Mob affixes

Shiny mobs and the five rare affixes (Armored, Regenerating, Lucky, Enraged, Splitter).

File: `plugins/ClickEmCore/modules/mobaffixes.yml`. Module id: `mobaffixes`.

Each zone has three normal mobs. On top of that, a mob can roll a **variety** when it spawns. It never changes which mob type appears, only how tough, rewarding and visible that single mob is.

| Variety          | What it does                                                                                                               |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Shiny**        | Rare (1.5%), 3x health, pays 4x. Glows yellow. Can also carry an affix.                                                    |
| **Armored**      | 1.6x health and ignores 25% of each hit. Pays 1.9x.                                                                        |
| **Regenerating** | 1.3x health, heals 4% every 2 seconds. Pays 1.3x.                                                                          |
| **Lucky**        | 1.2x health, adds +6 percentage points to the killer's Echo and Roll Fragment chance for that kill. Pays 1.5x.             |
| **Enraged**      | 1.2x health. Pays 1.25x. Its damage boost has no visible effect because regular mobs never hit players.                    |
| **Splitter**     | 1.4x health. On death spawns 2 smaller copies (35% health, 70% size) that pay 40% each and never roll anything themselves. |

Bosses never roll Shiny or affixes.

### Settings

| Key                                                                                                  | Default           | Meaning                                                                           |
| ---------------------------------------------------------------------------------------------------- | ----------------- | --------------------------------------------------------------------------------- |
| `enabled`                                                                                            | true              | Master switch.                                                                    |
| `max-per-zone`                                                                                       | 3                 | Most of each kind alive in one zone. Shiny and each affix are counted separately. |
| `shiny.chance-percent`                                                                               | 1.5               | Chance a spawn is Shiny.                                                          |
| `shiny.hp-multiplier`, `reward-multiplier`                                                           | 3.0, 4.0          | Toughness and payout.                                                             |
| `shiny.glow-color`                                                                                   | YELLOW            | Any Bukkit colour name.                                                           |
| `shiny.name-prefix`                                                                                  | gradient "Shiny"  | MiniMessage text in front of the health bar name.                                 |
| `affix-chance-percent`                                                                               | 8.0               | Chance a spawned mob rolls one affix at all. `0` = off.                           |
| `affixes.<name>.chance-weight`                                                                       | 3 / 3 / 2 / 3 / 2 | Relative weight among affixes (not percent).                                      |
| `affixes.<name>.hp-multiplier`, `reward-multiplier`                                                  | see above         | Toughness and payout.                                                             |
| `affixes.armored.damage-reduction-percent`                                                           | 25                | Hit ignored. Capped at 95.                                                        |
| `affixes.regenerating.regen-percent-per-tick`, `regen-interval-seconds`                              | 4, 2              | Heal amount and timing.                                                           |
| `affixes.lucky.drop-chance-bonus-percent`                                                            | 6                 | Extra Echo and fragment chance. Keep modest.                                      |
| `affixes.splitter.split-count`, `split-hp-fraction`, `split-scale-fraction`, `split-reward-fraction` | 2, 0.35, 0.7, 0.4 | The copies.                                                                       |

{% hint style="info" %}
Pay is priced against how much longer the mob takes to kill. If you raise an affix's toughness, raise its `reward-multiplier` too, otherwise players will skip it.
{% endhint %}

Nameplate text for each variety (`name-prefix`) uses MiniMessage, so gradients and bold work.


---

# 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/mob-affixes.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.