Create and manage arenas
Create an arena, set its spawns, enable or delete it, and see how the plugin picks one for each session.
An arena is a place with two spawns. It is never locked: any number of duels and solo sessions run in the same arena at once, and players of different sessions cannot see, hit, touch or pick up after each other. The arena knows nothing about who is inside it beyond a count.
Arenas live in the database, in totem_arenas, not in a YAML file. Servers pointing at the same
database share them according to arena.arenas-scope (by default, the network group set in ExyliaLib), and a reload does not touch them.
Before you start#
You need the exyliatotemtrainer.admin permission and the /totemtraineradmin command. Walk to the place
where you want players to stand, because the spawns are set from where you are.
Creating an arena#
Everything happens in /totemtraineradmin → Arenas. There is nothing to type on a command line
beyond reload.
Create
Click Create Arena and type an id when asked. The id is lowercased and refused if an arena already uses it. The arena appears enabled, with no spawns, and the chat says "Set both spawns next."
Name it
On the arena screen, Display name opens a text input: up to 64 characters, colours allowed. This is what players read; the id stays as it was.
Set both spawns
Click Spawn A, then stand where it goes: the wizard stores your position. Repeat with Spawn B. Solo training uses spawn A; a duel sends one player to each.
Check it is ready
The summary item shows Ready once the arena is enabled and both spawns are set in loaded worlds. The arena list marks each arena as ready or incomplete.
A duellist is pinned on the horizontal axes but is allowed to fall, so a spawn set slightly above the floor settles instead of leaving somebody hovering.
Check that it works#
Open /totemtraineradmin → Arenas: your arena is listed without the INCOMPLETE tag. Then run
/totem train normal as a player: you are teleported to spawn A, the countdown runs and the drill
starts. Leave with /totem leave.
Enabled, disabled, deleted#
| Action | Effect |
|---|---|
| Status (while enabled) | No new duel or session is sent there. Every duel running in it is stopped, and the chat says so. |
| Status (while disabled) | The arena is offered again, provided both spawns are set. |
| Delete | Behind a confirmation screen. Stops every duel running in it and removes the row. |
A duel stopped this way is cancelled: both players are sent back and nothing is stored.
How an arena is picked#
When a duel starts or a solo session begins, the plugin takes the ready arena hosting the fewest duels and solo sessions combined. Ten duels on one server therefore spread across the arenas instead of stacking on the first one.
arena:
max-matches-per-arena: 0
return-location: ""| Key | Default | What it does |
|---|---|---|
max-matches-per-arena | 0 | Sessions one arena may host at once, duels and solo sessions counted together. 0 is unlimited. An arena at its cap is skipped. |
return-location | "" | Where a player is sent after leaving, as world,x,y,z or world,x,y,z,yaw,pitch. Empty sends them back to where they came from. |
With return-location empty, a player goes back to the exact spot they started from. If that spot is
unknown, they go to their world's spawn.
Solo training and duels both need a ready arena with room. Without one, nothing is taken from the player: a session or a duel is refused with "No arena is ready. Ask an administrator."
The rest of the admin menu#
The main screen shows how many arenas exist and how many are ready, the duels running, the solo sessions and the players in a duel or session.
| Screen | What it does |
|---|---|
| Arenas | The list above, sorted by id, each with its spawns, enabled state and current load. |
| Running duels | Every duel in progress with players, score, arena, round, format, mode and speed. Each can be cancelled behind a confirmation: both players are sent back and nothing is stored. |
| Players | Everyone online with their state, wins, losses and total pops. Each can be reset through ExyliaLib's player reset, narrowed to this plugin: it asks first, then removes their profile and records. |
| Settings | The settings an admin tunes in game, in a hub with four pages: Training (default speed, countdown), Matches (format, delays, request expiry and cooldown, matches per arena), Scoring (reaction thresholds, fail penalty, full-credit pops, reference speed) and Records and chat (board and history sizes, retention, chat isolation). Modes, speeds and everything else stay in config.yml. |
| Reload | Runs the same reload as /totemtraineradmin reload and reopens the menu. |
Resetting a player sets their profile back to zero and deletes every training record they hold. The mode leaderboards are read from those records, so a player left with them would stay on every board they were on.
The admin menu files#
The player-facing menus in lang/<language>/menus/ follow the release without overwriting you: a
missing file is written, a new key is added, and a changed default waits in /exylialib updates. The
admin screens in lang/<language>/menus/admin/ are rewritten from the jar on every start: a button
added in a new release has to reach servers that already have the folder. Do not edit them.
Something missing on this page? Tell us on Discord