Content generated with AI — it may contain mistakes.

ExyliaPracticeCore/GuidesUpdated in v1.4.0

Run many matches in one arena

Let one built arena host several matches at once with clones, and restore its blocks between matches.

Page 5 of 355 min read

A practice server runs more matches at once than it has arenas built. ExyliaPracticeCore pastes copies of an arena into a void world and treats each one as a separate arena, up to ten per arena by default. Clones are made on demand; you can also create them in advance before an event.

Before you start#

  • The arena is fully set up and enabled, with both schematics saved: see Set up arenas.
  • FastAsyncWorldEdit is installed. Without it cloning is off (see the last section).
  • On Folia, the Worlds plugin is installed: Folia cannot create a world through Bukkit, so without it there is nowhere to paste clones (see Common problems).

Steps#

Nothing has to be configured for clones to work: they are made automatically when every arena a kit may use is busy. To create some ahead of time:

Open the arena's clones

Run /epc, click Manage arenas, pick the arena, then click View clones. The screen lists the original and every clone, with their status.

Preload clones

Click Force load clones. Chat asks how many, between 1 and arena.max-clones-per-arena (10 by default). The arena setup screen reopens when they are pasted and a message tells you how many were created.

Look at one

Click an instance in the list to teleport to it. It is the only way to look at a clone.

Do this before an event, so the first matches do not each pay for a paste.

Check that it works#

  • View clones shows the number of active clones on the setup screen and lists each as Clone #<n> next to the original.
  • Start more simultaneous matches than you have arenas: players land in different copies and none of them shares blocks with another.

When a clone is made#

Only on demand, and only as a last resort:

Try every compatible arena

The match walks the kit's compatible-arena list in order and takes the first free instance it finds, original or clone.

Shuffle and clone

If nothing is free, the list is shuffled and the first fully-configured arena in it is cloned. The shuffle is what keeps a busy server from cloning the same arena ten times.

Give up

If no arena can be cloned (clone limit hit, no schematic, clone world not ready) the players are told there are no arenas available and put back in the lobby.

Where they go#

Each clone gets its own plot in ExyliaLib's temporary world, pasted at the Y from arena.clone-paste-y (64 by default). Plots start on a chunk boundary, are never reused during a run, and sit further from each other than the server's view distance, so a player on the edge of one copy never sees another and nothing from one match reaches the next.

SettingDefaultWhat it does
arena.max-clones-per-arena10The hard ceiling per arena. Includes clones already made and still alive.
arena.clone-paste-y64The Y the copy region's corner is pasted at
Clones are never destroyed

A clone stays pasted for the life of the server and is reused for the next match that needs it. What resets between matches is the blocks, not the paste. Ten clones of one arena means the clone world holds ten copies until restart, and the whole world is deleted on shutdown anyway. To use less memory, lower arena.max-clones-per-arena.

Regeneration#

When a match ends, the arena instance is released. What happens to the blocks depends on the kit:

Kit rulesWhat happens
build or block-break enabledThe playable region is restored from practice_arena_<id>_playable, then the chunks are unloaded
Neither enabledNo block work at all, just entity cleanup and a chunk unload

Dropped items, arrows, TNT and every other non-player entity inside the playable region are removed either way. To restore an arena by hand, right click Schematic on its setup screen.

Mid-match regeneration#

A kit with Regenerate after point (see Set the rules of a kit) restores the arena without freeing it, between one point and the next. The instance goes IN_USE → REGENERATING → IN_USE, and the point-reset countdown starts once the blocks are back.

When cloning is off#

If the schematic module reports itself unsupported (no FastAsyncWorldEdit), the console says so once at startup:

Arena regeneration is off: <reason>

From then on, every arena has exactly one instance, matches queue behind each other, and blocks are never restored.

What is relocated into a clone

Pasting the blocks is the easy half. Everything the arena knows about itself moves with it:

  • Spawn 1, spawn 2, spectator spawn, party FFA spawn: offset from the copy region's minimum corner, keeping their exact facing.
  • The playable region: offset and re-registered under the id practice_arena_<id>_clone_<n>_playable.
  • Every extra region: offset and re-registered as practice_arena_<id>_clone_<n>_extra_<i>.
Players inside are not moved by a regeneration

The regeneration is told explicitly not to relocate trapped players. Whoever is still in there belongs to the match that just ended, and that match decides where they go, which it does a tick later by sending them to the lobby.

Something missing on this page? Tell us on Discord