Content generated with AI — it may contain mistakes.

ExyliaAimTrainer/GuidesUpdated in v1.2.0

Set up arenas

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

Page 4 of 258 min read

An arena is the place where drills and duels happen: one spawn, with the targets appearing in the direction it faces. Create one and your players can start training.

Before you start#

  • ExyliaAimTrainer and PacketEvents installed, see Install ExyliaAimTrainer.
  • The exyliaaimtrainer.admin permission, see Permissions.
  • Open space in front of where the spawn goes. The default precision drill places targets up to 12 blocks away and a player can push their distance setting to x3.00, so leave well over thirty blocks clear.

Steps#

Open the admin menu

Run /aimtraineradmin (or /aimadmin) and click Arenas.

Create the arena

Click Create arena and type a short id when asked, such as aim1. It is stored lowercased and refused if it is taken. The chat says "Arena aim1 created. Set its spawn next."

Name it

Left-click the new arena, then click Display name. Type what players should read, up to 64 characters, colours allowed.

Set the spawn

Click Spawn, then stand where players should appear and face the open space where the targets should show up. The arena stores your position and where you look.

Check that it works#

Back in the Arenas list, your arena shows as a grass block. An arena without a spawn, or a disabled one, is a coarse dirt block marked [NO SPAWN], and players cannot be sent there. Run /aim train: you should land on the spawn, a countdown runs, and the first targets appear in front of you.

Going further#

Have several arenas#

Repeat the steps. Every new drill or duel goes to the ready arena with the fewest players, so busy servers spread out by themselves. To cap how many players one arena hosts, set arena.max-players-per-arena in config.yml (0, the default, is no cap).

Turn an arena off or delete it#

Open the arena and click Status to switch it between enabled and disabled. A disabled arena takes nobody new, and every drill or duel running there is stopped. To delete one, click Delete on the arena screen, or right-click it in the list, then confirm.

Send players somewhere after training#

By default players go back to where they started. To send them to one place instead, set arena.return-location in config.yml as world,x,y,z.

The rest of the admin menu#

/aimtraineradmin also holds Duels (every duel running, click one to cancel it), Players (rating, accuracy and state of everyone online; stop a drill or reset someone's stats), Settings (the options below) and Reload.

Technical details

An arena is a place with one spawn. It is never locked: any number of drills and duels run in the same arena at once, every player in it is isolated from every other, and each sees only their own targets. The direction the spawn faces is where the targets appear. The arena knows nothing about who is inside it beyond a count.

Arenas live in the database, in aim_arenas, not in a YAML file. Every server pointing at the same database shares them, and a reload does not touch them.

No arena, nothing to play

A drill and a duel both need a ready arena. With none, a drill reads "No arena is ready. Ask an administrator." before the player is touched, and so do both sides of an accepted duel. There is no training where the player stands.

Where the targets appear#

A player is frozen on the spawn, so every drill is laid out around the spawn's position and facing.

  • Flick targets are placed around the eyes, within the drill's horizontal spread either side of that facing and its range of elevations, never in the floor.
  • A tracking target strafes in an arc in front of the player; a fighter circles round them and closes in.
  • A target is placed at the drill's distance times the player's distance setting. The shipped precision drill reaches 12 blocks, and a player may push the distance to ×3.00, so leave a clear space of well over thirty blocks in front of the spawn if you keep those defaults.

Drills and settings are on Drills and Settings.

Enabled, disabled, deleted#

ActionEffect
Status (to disabled)No new drill or duel is sent there. Every drill running in it is stopped and its player sent home; every duel running in it is cancelled. The chat says "Arena <id> disabled. Sessions there were stopped."
Status (to enabled)The arena is offered again, once its spawn is set.
Delete, or right click in the listBehind a confirmation screen. Stops every drill and duel running in it the same way, then removes the row.

A duel stopped this way is cancelled: both players are sent back and nothing is stored. A drill stopped this way is a run cut short, and is not stored. See Training.

How an arena is picked#

When a drill or a duel starts, the plugin takes the ready arena hosting the fewest players: one per drill, two per duel, a duel still showing its result included. Ten players training at once therefore spread across the arenas instead of stacking on the first one.

plugins/ExyliaAimTrainer/config.yml
yaml
arena:
  max-players-per-arena: 0
  return-location: ""
KeyDefaultWhat it does
max-players-per-arena0Players one arena may host at once, drills and duels counted together. 0 is unlimited. An arena without room for the newcomers is skipped: one place for a drill, two for a duel.
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.
arenas-scopedefaultWhich servers share the arenas stored in the database: default follows the network group set in ExyliaLib's config.yml, server gives each server its own, global shares with all, any other value is a group name. Read at startup.

A duel needs room for both players, so an arena one player below its cap takes a drill but not a duel.

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.

Right after a start

Arenas are read from the database asynchronously once the plugin enables; the console prints "Loaded <n> arenas and <m> drills" when they are in. Until then there is no ready arena to pick: a drill is refused with the no-arena line, and an accepted duel does nothing.

The rest of the admin menu#

The main screen shows how many arenas exist and how many are ready, the duels and drills running, and the players in a drill or duel.

ScreenWhat it does
ArenasThe list above, sorted by id, each with its id, enabled state, spawn and current load of duels and drills.
Running duelsEvery duel in progress with its players, series score, round, format, drill, arena and state. Clicking one cancels it behind a confirmation: both players are sent back and nothing is stored.
PlayersEveryone online, sorted by name, with their rating, accuracy, sessions, wins, losses and state. A free player: click to reset their statistics. A busy player: left click stops their drill, right click resets their statistics. Both resets go through a confirmation.
SettingsThe settings an admin tunes in game, in a hub with four pages: Training (countdown, rotation lock, rest time, default drill, players per arena, chat isolation), Duels (format, delays, request expiry and cooldown), Practice queue and Boards and history (board and history sizes, retention). Drills, scoring and everything else stay in config.yml.
ReloadRuns the same reload as /aimtraineradmin reload and reopens the menu.
Stopping a player stops a drill

The left click on a busy player stops a drill only. A player in a duel is left where they are; cancel the duel from Running duels instead.

What a reset clears, and what it keeps

Resetting a player goes through ExyliaLib's player reset, narrowed to this plugin. It asks first, then kicks the player and locks them out while it runs (the staff member needs exylialib.admin.wipe). It deletes the player's progress rows: the profile (lifetime numbers, duel record, overall rating and the player's settings) and every drill record, so they leave every board. Session and duel history rows are removed only when the staff member adds history to the reset; otherwise they stay until retention removes them.

The admin menu files#

The admin screens in menus/admin/ are rewritten from the jar on every start and every reload, so a button added in a release reaches servers that already have the folder. Nothing an owner is meant to edit lives there. How the player-facing menus are updated is on Menus.

Something missing on this page? Tell us on Discord