Arenas

An event configuration is a row in the database. It carries the arena, the settings, the kits and the rewards for one event, and it is edited entirely from /eventsadmin.

What a configuration holds

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.
• An arena schematic is checked separately, because it is not needed to play but is needed to restore.

Markers

Thirteen 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 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.

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.

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 two cloning types: Brackets 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.

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. Four 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 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.

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.

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 auto world

Two types need more than one copy of the arena at a time, so the plugin generates a flat, empty world called exyliaevents_autoworld and pastes copies into it side by side:

auto-world:
  clone-spacing: 500
  clone-paste-y: 64

The world is created at startup: through Bukkit normally, and through the Worlds plugin on Folia, where Bukkit's own world creation is not available. If it already exists it is adopted rather than regenerated.

Materials each type expects

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

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.

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.