Content generated with AI — it may contain mistakes.

Configuring

Arenas

What an arena is, how it is created from the admin menu, how one is picked, and the rest of the staff screens.

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. Every server pointing at the same database shares them, and a reload does not touch them.

Creating an arena

Everything happens in /totemtraineradmin → Arenas. There is nothing to type on a command line beyond reload.

Create

Click the create button 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.

Set the spawns a block above the floor if you want

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.

Enabled, disabled, deleted

ActionEffect
DisableNo new duel or session is sent there. Every duel running in it is stopped, and the chat says so.
EnableThe arena is offered again, provided both spawns are set.
DeleteBehind 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.

plugins/ExyliaTotemTrainer/config.yml
arena:
  max-matches-per-arena: 0
  return-location: ""
KeyDefaultWhat it does
max-matches-per-arena0Sessions 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.

No arena, no duel

With no ready arena, solo training still works: the player trains where they stand. A duel cannot start without one; both players read "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 online.

ScreenWhat it does
ArenasThe list above, sorted by id, each with its spawns, enabled state and current load.
Running duelsEvery 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.
PlayersEveryone online with their state, wins, losses and total pops. Each can have their statistics reset behind a confirmation.
ReloadRuns the same reload as /totemtraineradmin reload and reopens the menu.
A reset is both halves

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 menus/ are copied from the jar once and then left alone, so your edits survive. The admin screens in 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