Content generated with AI — it may contain mistakes.

ExyliaEvents/GuidesUpdated in v1.12.0

Create an arena

Set the spawns, bounds, markers and schematic of an event arena, and learn what each game needs built into it.

Page 4 of 2515 min read

By the end of this page you have an arena that passes validation, is saved as a schematic so it resets after every game, and is built with the blocks its game expects. An event configuration is stored in the database and edited entirely from /eventsadmin.

Before you start#

Steps#

Open the setup screen

Run /eventsadmin, click Configurations, open the category and click your event.

Set the spawns

Left-click Lobby spawn where players wait and Spectator spawn where eliminated players watch. Left-click Spawn points at each place players start; right-click clears them. See Spawn points.

Set the bounds

Click Set bounds and select the two corners of the box the game happens in. Games that clone arenas can also use Copy region; see Bounds and the schematic.

Mark goals, flags and points

If the type needs places marked, click Arena markers and fill each red row. See Markers.

Save the schematic

Left-click Schematic to save the arena as it is now. The configuration cannot be enabled without it. Right-click restores it by hand.

Enable it

Click the switch. If something is missing it refuses and lists what; see Validation.

Check that it works#

Run /eventsadmin forcestart <id> and join with a second account. You should appear at a spawn point, see the arena border (if it is on), and after the game the arena is pasted back from the schematic. If the switch will not turn on, hover over it to read the missing pieces.

Going further#

The sections below cover validation, markers, the arena border, flags, running copies side by side and what the game restores.

What a configuration holds#

Everything a configuration stores
FieldWhat it is
idThe key. What commands, menus and placeholders name.
displayNameWhat players read. Defaults to the id.
eventTypeWhich of the 54 games it is. Chosen at creation.
markersThe places the type asked to have marked: goals, flag stands, capture points.
enabledWhether it may be started at all.
iconMaterialThe menu icon. Defaults to NETHER_STAR.
lobbySpawnWhere players wait before the game starts.
spectatorSpawnWhere spectators and eliminated players go.
spawnPointsWhere players are dropped at the start.
boundsThe cuboid the game happens inside.
copyBoundsAn optional second region, cloned instead of bounds by Brackets, Sumo and Build Battle.
settingsEverything the type itself reads.
Kits, loot, rewardsStored alongside, covered in their own pages.

Validation#

A configuration is playable when it has a lobby spawn, a spectator spawn, at least one spawn point, complete bounds and every marker its type requires. The setup screen lists whatever is missing by name.

Four extra rules:

  • Types marked as needing one spawn per player — Pillars of Fortune and Survival Games — require at least max-players spawn points, and the validator says how many are missing.
  • A team type requires at least as many spawn points as it has teams, so every team gets its own.
  • A type that generates its own spawns — Mace Roulette — is asked for none: it places players itself, and the setup screen does not even show them.
  • A saved arena schematic (event_bounds_<id>) is also required to enable a configuration. A configuration that was enabled and loses its schematic is switched off again when the server starts.

Markers#

Fourteen types need specific places on the arena marked by hand: The Bridge's goal, Capture the Flag's stand, Domination's points, KOTH's hill, Trivia's answer zones. Those places used to be found by scanning for materials; now the admin declares them.

Each type declares the markers it wants, and the Arena markers screen in setup shows one row per slot: one row per team when the marker is per team, and one row per allowed marker when it accepts several. Required rows that are not set show in red and appear in validation too.

ShapeHow it is set
AreaA cuboid selected with the region wand, like the arena bounds.
BlockA clicked block. What counts as "being there" is that block plus a radius.
Markers by type
TypeMarkerShapeHow many
The BridgeGoalAreaOne per team
Capture the FlagFlag standBlockOne per team
DominationCapture pointArea1 to 8
DodgeballCourtAreaOne per team
King of the HillHillArea1 to 4
King of the Hill TeamsHillArea1 to 4
Red Light, Green LightFinish lineArea1
Glass BridgeBridge glassArea1
Glass BridgeFinish platformArea1
Murder MysteryGold spawnBlock0 to 32
Zombie HordeMob spawnerBlock1 to 16
TriviaAnswer zoneAreaExactly 4
RaceCheckpointArea1 to 32
RaceFinish lineArea1
Mace RoulettePlatform centreBlock1
Beep TestLevel finishArea1 to 40

A marker can be cleared or teleported to from the same screen. Per-team markers follow team-count: raising it to four adds two more rows that have to be marked.

Markers live in the configuration

They are not WorldGuard regions or magic blocks in the map: they are stored on the event configuration, so rebuilding the arena does not clear them — but moving it leaves them behind.

Bounds and the schematic#

bounds does two jobs: it is what counts as "inside the arena", and it is what gets saved as a schematic named event_bounds_<id>.

copyBounds is a second, optional region used only by the three cloning types: Brackets, Sumo and Build Battle copy copyBounds when it is set and fall back to bounds when it is not. It exists for an arena whose playable area is smaller than what should travel with a clone — a duel ring inside a decorated hall, for instance. Restoring after a normal game always uses bounds.

Re-save after editing the map

The schematic is a snapshot. Change the arena and it keeps restoring the old version until you save it again from the setup screen.

The arena border#

Every event with bounds draws them as a world border for as long as it runs: a visible wall at the edge of the arena. It is sent to each player's own client, so two arenas in the same world each show their own and the world's real border is never touched. Only players standing inside the bounds see it — a spectator stand or a waiting cage outside the arena does not.

A border is square and bounds need not be, so it follows the longer side, and the short side is still guarded by the event's own bounds check. It hurts nobody and never tints the screen. It is only the wall a player sees: pearls and modified clients ignore it, and leaving the bounds is still the game's call.

bounds-border, on by default, is the per-event switch — Arena border on the setup screen. Five types never draw one: Mace Roulette, where being knocked over the edge is the game; Thimble, whose jump platform may stand outside the bounds; and Brackets, Sumo and Build Battle, which wall in each duel arena and each plot instead. The shrinking zone of Last Man Standing and Survival Games is drawn the same way.

world-border.enabled in config.yml is the server-wide switch above it: turned off, no event draws a border whatever its own setting says, and only a shrinking zone still appears. See Configuration · world-border.

Arena flags#

Each game sets its own rules for the arena — whether players fight, build, break blocks, drop items or take fall damage. Arena flags on the setup screen opens ExyliaLib's flag editor over them, so one configuration can play differently from another of the same type.

Every arena flag
FlagWhat it decides
pvpPlayers can hurt each other.
buildBlocks can be placed.
breakBlocks can be broken.
interactBlocks can be right-clicked.
item_dropItems can be dropped.
item_pickupItems can be picked up.
fall_damageFalls hurt.
player_build_onlyOnly blocks a player placed can be broken.
temporary_blocksPlaced blocks disappear after a while: 30 seconds when the game sets no time of its own.
temporary_blocks_secondsHow many seconds a temporary block lasts in this arena, a row under temporary_blocks in the flags screen. Left empty, the game's own time applies; a game that locks temporary_blocks ignores it. New in v1.12.0
re_give_blocksA temporary block that disappears is handed back to whoever placed it.
waterWater is harmless. Denied, touching it counts as a death in that game.
lavaLava burns as usual. Denied, touching it counts as a death in that game.
craftingItems can be crafted, at a crafting table or in the inventory grid.
skillsAuraSkills and mcMMO work as usual. Denied, players earn no skill experience and get no abilities or combat stats while in the event.
build_outsideBlocks can be placed beyond the arena's bounds. Denied, only inside them, so the top of the bounds is the height limit.

Below the flags the editor has Build height, ExyliaLib's build_max_y: the highest block Y a player can place at in this arena, 0 (the default) for no limit. It is stored beside the flags as build_max_y, and a player who hits it is told why.

A click cycles a flag through Default, Allow and Deny; a right click takes it back to Default. Default means whatever the game sets on its own, which the editor shows, so a configuration nobody touched plays exactly as before. Nothing is written until you save, and the item on the setup screen counts the overrides.

The rules hold only for the players of the game running in the arena, and only inside its bounds.

Every type declares both hazards. Water is denied by default in TNT Run, Spleef, Splegg, Block Party, Anvil Running and Sumo, and allowed everywhere else. Lava is denied by default everywhere except Brackets, Tournament and Pillars of Fortune, where it burns as usual. Brackets and Tournament take their water default from the old water-eliminates setting, so a configuration that had it on keeps playing the same. Override either flag per configuration like any other.

Skills and building outside the arena are denied by default in every type. Skills come back as soon as the player leaves the event.

Crafting is denied by default everywhere except Pillars of Fortune and Simon Says. Survival Games always lets its players craft, whatever the flag says, and nobody crafts before a game starts.

Some flags are the game's

A flag the game switches by itself during play cannot be overridden and shows why. PvP is locked in Block Party, Chairs, Simon Says and Tournament, which turn it on and off by phase. Crafting is locked on in Simon Says, where crafting something is one of the orders.

Simultaneous runs#

Simultaneous runs on the setup screen sets max-instances (default 1): how many runs of this arena may play at once. Every run past the first plays in a pasted copy of the arena, in the temporary world, with its markers, bounds and lobby moved along; places outside the arena's bounds stay where they are, and a spectator platform outside the footprint is replaced by the copy's first spawn. Brackets, Sumo and Build Battle already lease their own copies, so the setting is not offered for them. Starting an arena that is full says how many runs it allows.

Spawn points#

Most types put each player at a random spawn point. Some ask for a spawn far from other players, so several spread-out points are better than one — a single point means everyone lands on top of each other.

The temporary world#

Three types need more than one copy of the arena at a time, so they paste copies into ExyliaLib's temporary world, exylialib_temporary, side by side:

TypeWhat is cloned
BracketsOne arena copy per simultaneous match
SumoOne arena copy per simultaneous match
Build BattleOne plot per builder

The games are played in the copies, never in the original, so the arena flags are applied there too. Copies are pasted at the original's lowest Y, far enough apart that no copy sees another. A copy a game has finished with is regenerated and handed to the next one instead of being pasted again.

There is nothing to configure: the old auto-world block of config.yml is no longer read. The world is a void one, never kept — ExyliaLib deletes its folder when it starts and stops — and it is created through Bukkit normally and through the Worlds plugin on Folia, where Bukkit's own world creation is not available. Other Exylia plugins paste their own copies into the same world.

When a copy cannot be made, the fighters play on the configuration's own spawns instead and the console says so.

Cloning needs the schematic

A Brackets, Sumo or Build Battle arena with no saved schematic has nothing to clone. Save it before running either type.

Materials each type expects#

Several games look for specific blocks. Build the arena with these or the game will not work:

TypeWhat it needs
TNT RunA floor whose block has TNT directly beneath it — that is what makes a block fall away. Touching WATER eliminates.
SpleefSNOW_BLOCK as the breakable floor. Touching WATER eliminates.
SpleggThe breakable floor material is a setting, breakable-material, defaulting to SNOW_BLOCK. Touching WATER eliminates.
Block PartyThe floor scanner picks up WHITE_CONCRETE; those tiles are then recoloured each round. Falling into WATER eliminates.
SplatoonPaintable ground made of concrete or concrete powder — the full colour family is recoloured as players paint.
SlapRED_CONCRETE is the capture block: standing on it is what scores.
ParkourHEAVY_WEIGHTED_PRESSURE_PLATE for checkpoints, LIGHT_WEIGHTED_PRESSURE_PLATE for the finish.
ThimbleWATER blocks are the targets players dive into.
Water DropSurface WATER inside the arena bounds is the pool. No markers.
Anvil RunningTouching WATER eliminates.
Glass BridgeGlass inside the bridge marker, in rows of pairs. The event decides which panel is the fake one.
Mace RouletteNothing: it builds its own platform from the centre block using platform-material.
VolcanoA WHITE_CONCRETE floor. Only that block heats up (YELLOW_CONCRETE, ORANGE_CONCRETE, RED_CONCRETE) and vanishes; any other material never falls.
Gem CrawlerEMERALD_BLOCK inside the bounds: gems spawn on top of them. With none, no gems appear.
King KongA LIGHT_WEIGHTED_PRESSURE_PLATE as the goal: the runner who steps on it wins. Without one the runners have no way to win.
Survival GamesChests (CHEST or TRAPPED_CHEST) inside the bounds, filled from the loot table.
Water is the standard death plane

Several elimination games use water below the arena rather than a void: it is cheap to build, works at any Y, and lets a player's fall be seen. Where a type is listed above as eliminating on water, that is the mechanism, and the water arena flag is what switches it.

Restoring after a game#

When a game ends, the arena is restored from its schematic, which is what makes an arena reusable without an admin rebuilding blocks by hand. That is also why a type that changes the map — Spleef, TNT Run, Block Party, Splatoon — is unplayable twice in a row without one.

Types that never change their arena's blocks are not regenerated at all, which spares a full paste for nothing: Chairs, CS:GO, Dodgeball, Gem Crawler, Hide and Seek, Infection, King Kong, King of the Hill, Last Man Standing, Block Morph Hunt, Murder Mystery, OITC, Paintball, Parkour, Quake, Race, Red Light Green Light, Simon Says, Slap, TNT Tag, Top Killer, Tournament, Trivia, Beep Test, and the team variants of those. An admin who turns build or break on for one of them voids that promise, and its runs are regenerated as usual. A Tournament in that case is also regenerated between matches, so the next pair does not fight among the blocks, water and lava the last one left.

Between games an arena stays as it was saved. Mobs the world spawns on its own — natural spawns, spawners, patrols, raids — never appear inside one, playing or not, while the mobs an event spawns itself are left alone. An explosion next to an arena that is not being played leaves its blocks where they are; a running game keeps its explosions, and the schematic puts the blocks back when it ends.

Something missing on this page? Tell us on Discord