> 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/how-to/add-a-mob.md).

# Add or replace a mob

Add a new mob to an existing zone, or replace one, and all the files that must agree.

A ClickEm mob has **one id**, used in five places. If any one is missed, the mob spawns but pays nothing, is ignored, or never appears.

| File                                         | What to set                                                         |
| -------------------------------------------- | ------------------------------------------------------------------- |
| `plugins/MythicMobs/mobs/ClickEm_Zonasf.yml` | The mob: type, health, name.                                        |
| `modules/zones.yml`                          | Add the id to the zone's `allowed-mobs`. Otherwise it pays nothing. |
| `modules/spawners.yml`                       | A pad with `mob: <id>`.                                             |
| `modules/mob-rewards.yml`                    | `rewards.<id>` (Coins, Essence).                                    |
| `modules/echoes.yml`                         | `mob-elements` (optional, for the matchup).                         |

### Steps

1. **Copy** an existing mob block in `ClickEm_Zonasf.yml` and rename it. The id pattern `W<world>Z<zone>f<role>` gives it the right size and payout grouping.
2. Change `Type:` (the vanilla entity), `Health:` and the `Display:` name. **Keep** `Damage: 0`, `NoAI`, `AIGoalSelectors: clear` and the `Options` block.
3. `/mm reload`. Test with `/mm mobs spawn <id>` only for a look. Real spawning is by pads.
4. Add the id to `allowed-mobs` of its zone.
5. Add or edit a pad in `spawners.yml` with `mob: <id>`.
6. Add `rewards.<id>` in `mob-rewards.yml`.
7. `/clickem reload`, then watch `/spawners` show the pad alive.

### Replace a mob's look only

Change `Type` (or add `model{m=...}` for a BetterModel model) and keep the id. No ClickEm files change.

### Make a special boss-like mob

Add the id to `combat.boss-mobs` in `mob-rewards.yml`. It then counts for Boss Damage, never rolls affixes, and uses boss hit rules. For a full boss with arena and skills, see [World bosses](/lethium-docs/gameplay/world-bosses.md).

### Naming the mob for players

Players see the **friendly name** from `Display`. To override it use `clickem.mobs.<id>.name` in `lang/en_us.yml`.

### Size

Size comes from the role number (the `f2` in `W1Z5f2`) through `spawn-behavior.scale.role-multipliers`. To force a size use `scale.overrides` in `spawners.yml`.


---

# 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/how-to/add-a-mob.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.