Content generated with AI — it may contain mistakes.

ExyliaPracticeCore/GuidesUpdated in v1.4.0

Set up arenas

Set the two regions, the spawns and the protection radii, and see what an arena needs before it can be enabled.

Page 4 of 358 min read

You will end with an arena that is enabled, restores itself between matches and can be cloned. Everything is edited from /epc → Manage arenas; an arena is a row in practice_arenas.

Before you start#

  • ExyliaPracticeCore is installed: see Installation. FastAsyncWorldEdit is needed to save schematics, which an arena cannot be enabled without (see the warning below).
  • The arena is already built in a world on your server, with walls, floor and decoration.
  • You have exyliapractice.admin (operators do).

Steps#

Create the arena

Run /epc, click Manage arenas, then Create. Chat asks for an id, then a display name. The setup screen (titled ARENA: your-id) opens.

Set the two spawns

Click Spawn 1 and Spawn 2 with the left button; a wizard asks you to stand where each side starts. The right button teleports you to a spawn that is already set. Both are required.

Select the playable region

Click Playable region and select the area the match happens in. Leaving it through its sides or bottom kills the player; standing above its top does not.

Select the copy region

Click Copy region and select a larger box that contains the playable region, with walls, floor and the spectator platform. Clones are pasted from it.

Choose what the arena is used for

The five Use buttons (queue, duel, party, bot, event) narrow which matches may use the arena. Leave them alone and the arena accepts every kind.

Enable it

Click Status. While something is missing, the button's lore lists it (see What blocks an arena from being enabled) and the click is refused.

Give it to a kit

Click Kits and add the kits that may be played here, or do it from the kit's Compatible arenas screen: it is the same list. See Create kits and categories.

Optional on the same screen: Spectator spawn, Party FFA spawn, Extra regions (guide), the two protection radii, Start animation, Priority, Name and Icon.

Check that it works#

  • Status reads enabled and its lore no longer lists anything missing.
  • Click View clones: the original instance is listed as available.
  • Queue or duel with a kit that includes the arena: both players land on spawn 1 and spawn 2. See Play your first match.

The two regions#

This is the part that confuses people, so it is worth being exact.

RegionWhat it is for
Playable regionThe area a match happens in. Leaving it through its sides or bottom kills you; standing over its top does not. It is what a regeneration restores between matches, and it is what carries the kit's rules as region policies.
Copy regionA 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.

Why the playable one is smaller

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#

SpawnRequiredUsed by
Spawn 1YesThe first side of every match
Spawn 2YesThe second side
Spectator spawnNoWhere a spectator lands
Party FFA spawnNoThe 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#

Two buttons set how far from a spawn or an extra region nobody may place or break blocks. Left click adds 1, right click removes 1, Shift adds or removes 5. The minimum is 0.

ButtonEffect
Spawn protectionBlocks may not be placed or broken within this many blocks of either spawn
Extra region protectionSame, measured from the edge 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:

FileSaved fromUsed for
practice_arena_<id>The copy regionPasting clones
practice_arena_<id>_playableThe playable regionRegeneration between matches

Both are saved automatically the moment you set the matching region. The Schematic button re-saves both with a left click and restores the arena from them with a right click. Re-save after any rebuild: a regeneration restores the file, not the blocks currently standing.

What blocks an arena from being enabled#

While the arena is disabled, the Status button's lore lists what is missing, and a click refuses with a line pointing at it:

  • Spawn 1
  • Spawn 2
  • Playable region
  • Copy region
  • Copy schematic (save it from the copy region)
  • Playable schematic (save it from the playable region)
The two schematic entries are also how a missing FAWE shows up

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.

Going further#

Narrow what an arena is used for#

An arena declares which kinds of match it accepts, from the Use buttons on its setup screen:

ButtonCovers
Use: queueRanked and unranked matchmaking, and plain 1v1 duels.
Use: duelDuels a player sent by hand.
Use: partyParty FFA and party team fights.
Use: botFights against bots.
Use: eventOther plugins' events (tournaments, FFA, the sandbox) that borrow an arena copy through the API.

A map built for party fights is never handed to a queue match, and a bot arena is never duelled in.

An arena that declares none accepts everything

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.

Change how 1v1 fighters wait#

Start animation cycles through the server default, none, gate, rise and cage. It only affects 1v1 fighters during the start countdown and needs PacketEvents. gate needs marker blocks built within 8 blocks of each spawn; rise and cage need nothing. The block types and the server-wide default are in Configuration under game.start-animation.

Pick which arena is used first#

Priority works like the kit one: left click adds 1, right click removes 1, Shift adds or removes 10.

Instances and how a match picks one

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.

The world border

During a match every fighter and spectator sees a world border around the arena, sent to them alone: centred on the playable region and as wide as its longer side, so it never cuts into the play area. It does no damage and never tints the screen; leaving the playable region is still what the plugin enforces. A player combat-tagged in a lobby PvP zone sees the same around that zone until the tag ends. world-border.enabled: false stops drawing them.

Deleting an arena

Right click the arena in the list and confirm. 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