Arenas
The two regions, the four spawns, the protection radii and what makes an arena enableable.
An arena is a row in practice_arenas. Everything about it is edited from /epc → Manage Arenas.
The two regions
This is the part that confuses people, so it is worth being exact.
| Region | What it is for |
|---|---|
| Playable region | The area a match happens in. Leaving it kills you. It is what a regeneration restores between matches, and it is what carries the kit's rules as region policies. |
| Copy region | A larger box around the arena. It is what a clone is pasted from, and it is the origin every clone's coordinates are measured against. |
The copy region should contain the playable region. Walls, floor, decoration, the spectator platform — anything that has to exist for a copy of this arena to look and play right.
Regenerating the whole copy region between every match would rebuild walls nobody touched. The playable region is the part players can damage, so it is the only part restored.
The four spawns
| Spawn | Required | Used by |
|---|---|---|
| Spawn 1 | Yes | The first side of every match |
| Spawn 2 | Yes | The second side |
| Spectator spawn | No | Where a spectator lands |
| Party FFA spawn | No | The centre of a party FFA; players are scattered around it |
In a 1v1 or a party duel, players alternate between spawn 1 and spawn 2. In a party FFA everybody
starts around the FFA spawn within party.ffa-spawn-radius blocks — 7 by default.
Protection radii
| Setting | Effect |
|---|---|
| Spawn protection radius | Blocks may not be placed or broken within this many blocks of either spawn |
| Extra region protection radius | Same, around the centre of every extra region |
Both default to 0, which means no protection. They only matter for kits that allow building.
Schematics
Every arena owns two schematic files, named after its id:
| File | Saved from | Used for |
|---|---|---|
practice_arena_<id> | The copy region | Pasting clones |
practice_arena_<id>_playable | The playable region | Regeneration between matches |
Both are saved automatically the moment you set the matching region, and the Schematic button re-saves both. Re-save after any rebuild: a regeneration restores the file, not the blocks currently standing.
What an arena is used for
An arena declares which kinds of match it accepts, from the Usage buttons on its setup screen:
| Usage | Covers |
|---|---|
QUEUE | Ranked and unranked matchmaking, and plain 1v1 duels. |
DUEL | Duels a player sent by hand. |
PARTY | Party FFA and party team fights. |
BOT | Fights against bots. |
A map built for party fights is never handed to a queue match, and a bot arena is never duelled in.
Which is exactly what every row written before this existed says, so nothing had to be migrated: an empty list means "any match", and picking usages is how you narrow it.
What blocks an arena from being enabled
The Status button refuses and lists what is missing:
- Spawn 1
- Spawn 2
- Playable Region
- Copy Region
- Copy Schematic (save from Copy Region)
- Playable Schematic (save from Playable Region)
The check asks the schematic store whether the file exists. On a server without FastAsyncWorldEdit the answer is always no, so the arena can never be enabled and the reason reads as a missing schematic rather than a missing plugin. The console said the real reason once, at startup.
Instances
One arena is one or more instances. The original — the built one, in your world — is instance
<id>. Every clone is <id>_clone_<n>. Each instance is independently AVAILABLE, IN_USE,
REGENERATING or DISABLED, and taking one is a compare-and-set, so two matches can never land in
the same arena.
When a match asks for an arena it goes through its kit's compatible list in order, taking the first free instance of any of them. Only when every instance of every compatible arena is busy does it shuffle the list and clone one.
Deleting an arena
Deleting removes the row, unregisters every clone's region and resets the clone counter. It does not delete the schematic files and it does not touch the built arena in your world.
A kit whose compatible list still names the deleted arena keeps naming it. The entry matches nothing and is skipped; tidy it up from the kit's Compatible arenas screen.
Something missing on this page? Tell us on Discord