> 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/server-setup/worlds-and-regions.md).

# Worlds and regions

The five worlds, their WorldGuard regions and flags, Multiverse, VoidGen, FastAsyncWorldEdit and MobDisabler.

### The worlds

{% hint style="success" %}
**Quick start**

* Builders: `/rg bypass` and the permission `clickem.zones.bypass`.
* New world: add it to MobDisabler's `DisabledWorlds`.
* Never rename the `zonaN` and `boss` regions.
  {% endhint %}

| World                                    | Generator                       | Purpose                                                                    |
| ---------------------------------------- | ------------------------------- | -------------------------------------------------------------------------- |
| `World1`                                 | VoidGen (empty void, all built) | Zones 1 to 24, World 1 boss, **the hub**: spawn, crates, market, AFK, NPCs |
| `World2` to `World5`                     | Copies of World 1's build       | Zones 1 to 24 of each world and their boss                                 |
| `world`, `world_nether`, `world_the_end` | Vanilla                         | The default server world. Not used for play.                               |

**Every world uses the same arena layout.** It was built once and reused, so the coordinates of every zone, pad, boss arena, spawn, crate and AFK spot are identical in all five worlds. Only the world name and the mobs change. This is why `/afk`, `/crates`, `/market` and `/hubzones` can use one set of coordinates.

World names are case-sensitive and must be exactly `World1` to `World5`. Zones, spawn pads, eggs and Echo terminals refer to them.

### Multiverse-Core

File: `plugins/Multiverse-Core/worlds.yml`. Multiverse loads the worlds at startup. Each is `gamemode: survival`, `difficulty: easy`, pvp on.

| Job                   | Command                                      |
| --------------------- | -------------------------------------------- |
| List worlds           | `/mv list`                                   |
| Import a world folder | `/mv import World6 normal`                   |
| Teleport              | `/mv tp World2`                              |
| Remove                | `/mv unload World6` then `/mv remove World6` |

Players do not use Multiverse. They move between worlds through **AdvancedPortals** (see [Portals](/lethium-docs/server-setup/portals-npcs-holograms.md)) and `/navigation`.

#### Adding a world

1. Stop the server. Copy an existing world folder (for example `World5`) to a new name.
2. Start the server and run `/mv import <name> normal`.
3. Add its zones to `zones.yml`, spawn pads to `spawners.yml`, regions copied in WorldGuard, and a MythicMobs set. See [Add a zone](/lethium-docs/how-to/add-a-zone.md).

ClickEm currently supports worlds numbered 1 to 5 in `rebirth.yml` `world-tiers` and the `/spawnN` commands.

### VoidGen

The empty-world generator. `World1` uses it, so there is no terrain outside the builds. Nothing to configure.

### WorldGuard

Files: `plugins/WorldGuard/config.yml`, and per world `plugins/WorldGuard/worlds/<World>/regions.yml`, `config.yml`, `blacklist.txt`.

WorldGuard protects the hub and defines the **regions** that ClickEm uses for zones and boss arenas.

#### Regions in every world

| Region                  | What it is                                                                                       |
| ----------------------- | ------------------------------------------------------------------------------------------------ |
| `zona1` to `zona24`     | One per zone. ClickEm's zones reference these by name (`regions: [zona1]`).                      |
| `zona25`, `zona26`      | Extra regions around the boss end of the corridor.                                               |
| `zona1tp` to `zona24tp` | Small helper regions at each zone gate (high priority, no flags).                                |
| `zones`                 | One large region around the entire zone corridor.                                                |
| `boss`                  | The boss arena. The name **must contain `boss`** so the boss roams and only hurts players there. |
| `spawn`                 | The hub. `use`, `chest-access` and `pvp` denied.                                                 |
| `afk`                   | The AFK pool area. ClickEm's idle-earnings uses this name.                                       |
| `training`              | The tutorial and training dummy area (Zone 1).                                                   |
| `fish`, `obby`, `t1`    | Small extras (a fishing pond, a parkour, and a pickup-denied patch).                             |
| `__global__`            | The default flags for the whole world.                                                           |

#### Global flags (`__global__`)

```
block-break: deny          block-place: deny
interact: deny             use: deny
chest-access: deny         use-anvil: deny
pvp: deny                  item-drop: deny
item-pickup: deny          fall-damage: deny
mob-spawning: allow        mob-damage: allow
damage-animals: allow      weather-lock: clear
time-lock: 1000            ice-melt / snow-melt: deny
```

This makes every world **fixed daytime, clear weather, no building, no PVP, no item drops or pickups and no fall damage**. Mobs may spawn and be hurt (ClickEm's pads rely on it).

The `zones` region also sets `invincible: deny` and `mob-damage: allow`, so players can be hurt inside the zone corridor (by bosses only).

#### Common jobs

{% tabs %}
{% tab title="Let staff build" %}
Give them `worldguard.region.bypass.*` or run `/rg bypass` (toggle). They also need `clickem.zones.bypass` to walk through zone borders.
{% endtab %}

{% tab title="See or edit a region" %}
The WorldGuard **wand is a piece of leather** in this setup (`wand: minecraft:leather` in `config.yml`). Select two corners with it (or use `//pos1` and `//pos2` from FAWE), then `/rg define <name>`, `/rg info <name>`, `/rg flag <name> <flag> <value>`, `/rg redefine <name>`.
{% endtab %}

{% tab title="Allow something in one place" %}
`/rg flag <region> block-break allow`. Use a higher `/rg setpriority <region> 10` if it should beat the world default.
{% endtab %}

{% tab title="Copy regions to a new world" %}
Copy `worlds/World1/regions.yml` to `worlds/<NewWorld>/regions.yml` while the server is stopped.
{% endtab %}

{% tab title="Stop flight in a boss arena" %}
Nothing to do. `/fly` already switches off inside any region whose id contains `boss` (`fly.blocked-region-contains` in `vip-perks.yml`).
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
Regions hold the boss arena and the zone borders. **Do not rename or delete `zonaN` and `boss` regions** without changing `zones.yml` (`regions:`) and `spawners.yml` (`roam-region:`) to match.
{% endhint %}

### FastAsyncWorldEdit

Used to build and to `/clickem zones deploy`, which pastes zone arena templates. Schematics live in `plugins/FastAsyncWorldEdit/schematics/`. It is a soft dependency: without it, ClickEm works but cannot paste templates. Most staff commands are the standard `//pos1`, `//pos2`, `//copy`, `//paste`, `//schem save|load`, `//undo`.

### MobDisabler

File: `plugins/MobDisabler/config.yml`.

```yaml
DisabledWorlds:
  - World1
  - World2
  - World3
  - World4
  - World5
  - World6
```

It **stops natural mob spawning** in those worlds so only ClickEm's spawn pads create mobs. `World6` is listed in advance. **If you add a world, add its name here**, or vanilla mobs will start to spawn in it.


---

# 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/server-setup/worlds-and-regions.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.