> 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-zone.md).

# Add a zone

Step by step: add a new fighting zone with its region, mobs, pads, rewards and text.

A zone is the sum of **six small pieces** that must agree on names. Do them in order and test at the end.

| # | Piece            | File                            |
| - | ---------------- | ------------------------------- |
| 1 | The area         | A WorldGuard region             |
| 2 | The mobs         | MythicMobs `ClickEm_Zonasf.yml` |
| 3 | The zone rules   | `modules/zones.yml`             |
| 4 | Where mobs stand | `modules/spawners.yml`          |
| 5 | What mobs pay    | `modules/mob-rewards.yml`       |
| 6 | Names and text   | `lang/en_us.yml`                |

Use an existing zone as a template. Below the example zone is **`w1_zona25`**, World 1, three mobs `W1Z25f1` to `f3`.

{% stepper %}
{% step %}

#### 1. Make the region

Build the arena. Select it with the WorldGuard wand and run:

```
/rg define zona25
```

The region name is what `zones.yml` will reference. Add flags only if the defaults from `__global__` are wrong for it (see [Worlds and regions](/lethium-docs/server-setup/worlds-and-regions.md)).
{% endstep %}

{% step %}

#### 2. Create the three mobs

In `plugins/MythicMobs/mobs/ClickEm_Zonasf.yml` copy a full block of three mobs from another zone and rename them `W1Z25f1`, `W1Z25f2`, `W1Z25f3`. Set `Type`, `Health` and `Display`:

```yaml
W1Z25f1:
  Type: RABBIT
  Health: 50000
  Damage: 0
  Display: '&fMoss Whelp &7- &8(&c<caster.hp{r=1}>&7/&c<caster.mhp>&8) &4❤'
```

Keep `Damage: 0`, `NoAI: true` and the option block unchanged. Run `/mm reload`.
{% endstep %}

{% step %}

#### 3. Add the zone entry

In `modules/zones.yml`, add the block **in progression order** (the order of the list matters):

```yaml
  w1_zona25:
    world: World1
    regions: [zona25]
    display-name: "clickem.zones.w1_zona25.name"
    requirements:
      min-currency: 300000
      min-rebirth: 0
      min-level: 36
      required-zone: "w1_zona24"
      required-permission: ""
      required-achievement: ""
    allowed-mobs: [W1Z25f1, W1Z25f2, W1Z25f3]
    hologram:
      title: "clickem.zones.w1_zona25.hologram"
      x: 2300.5
      y: 131
      z: 553.5
      scale: 4
```

{% hint style="info" %}
The shipped game treats each world as 24 zones plus a boss. Adding a 25th normal zone changes the climb: `rebirth.yml` world tiers, the gear `zones` list, artifact and upgrade zone gates and `farm-window` all assume the existing ladder. Test the progression after adding.
{% endhint %}
{% endstep %}

{% step %}

#### 4. Place the spawn pads

In `modules/spawners.yml` under `spawn-points:` add one entry per pad. Stand on the pad and use `F3` to read the coordinates (add `0.5` to x and z to centre the mob):

```yaml
  w1_z25_p1:
    zone: w1_zona25
    world: World1
    x: 2310.5
    y: 126.0
    z: 540.5
    mob: W1Z25f1
    level: 1
    respawn-seconds: 5
    max-population: 1
```

Use `f1`, `f2` and `f3` across the pads. Check them with `/spawners`.
{% endstep %}

{% step %}

#### 5. Set the payouts

In `modules/mob-rewards.yml` under `rewards:` add each mob:

```yaml
  W1Z25f1:
    currency: 5000
  W1Z25f2:
    currency: 7000
  W1Z25f3:
    currency: 11000
    essence: 15
```

If you use a wildcard such as `"W1Z*"`, remember first match wins. For **Essence** drops add a `mob-essence` entry in `artifacts.yml`. For the **element** add `"W1Z25f*": EARTH` to `mob-elements` in `echoes.yml`.
{% endstep %}

{% step %}

#### 6. Write the text

In `lang/en_us.yml` add `clickem.zones.w1_zona25.name` and `clickem.zones.w1_zona25.hologram` (copy another zone's keys). Optional flavour names for the mobs go in `clickem.mobs.<id>.name`.
{% endstep %}

{% step %}

#### 7. Reload and test

```
/mm reload
/clickem reload
/ceadmin zones grant <you> w1_zona25
/navigation tp World1 w1_zona25
```

Check: mobs appear and respawn, killing pays, the landmark hologram shows, a player who has not unlocked it is held back by the border, and the `/zones` purchase works.
{% endstep %}
{% endstepper %}

### Also consider

* **Eggs:** new zone eggs use `required-zone` in `eggs.yml`.
* **Gear, Upgrades, Artifacts, Skills, Abilities:** they gate on zone ids. A new zone does not change those gates unless you edit them.
* **Copy to the other worlds:** every world has the same layout. Repeat with `W2`..`W5` names and world names.
* **Placeholders and HUD:** nothing to change. They read the zone list.


---

# 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-zone.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.