Skip to content

Hosted Event Setup Guide

This guide is for server owners and staff who configure and operate Athena's hosted events. Athena supports Last Man Standing (LMS), One In The Quiver (OITQ), Sumo, Wool Shuffle, Red Light Green Light, TNT Run, and TNT Tag. Only one hosted event can be active at a time.

Before you begin

  1. Install the current Athena jar and start the server once so events.yml is generated.
  2. Give the staff account the event permissions listed in Permissions. Setup actions must be run by a player because they save the executing player's location.
  3. Create and mark the server's lobby region as a safe zone if require_safezone_to_join is enabled (the default):

text /region togglesafezone <region>

  1. Choose an arena world and a rectangular play area. Bounds must be in the same world. Plan one distinct normal spawn per player you want the event to support; the default minimum for LMS and OITQ is 40.

Setup commands save locations to events.yml immediately. Configuration values such as limits, timers, kits, and messages can be changed in events.yml and loaded with /reloadathena; restart after changing the plugin jar or dependencies.

Administrator command reference

Command Permission Purpose
/event start <lms\|oitq\|sumo\|wool-shuffle\|rlgl\|tnt-run\|tnt-tag> athena.event.start Opens a queue for an event type.
/event force-start athena.event.force-start Starts the active queue early when its event rules allow it. LMS/OITQ require at least two waiting players.
/event cancel athena.event.cancel Cancels the active event and restores participating players.
/event setup <type> status athena.event.setup Checks whether the selected arena is ready.
/event setup <type> first athena.event.setup Sets the first cuboid bound for LMS, OITQ, Wool Shuffle, Red Light Green Light, TNT Run, or TNT Tag. bound-first is an alias.
/event setup <type> second athena.event.setup Sets the second cuboid bound for LMS, OITQ, Wool Shuffle, Red Light Green Light, TNT Run, or TNT Tag. bound-second is an alias.
/event setup <type> add-spawn athena.event.setup Adds the player's current location to the normal spawn list.
/event setup <type> clear-spawns athena.event.setup Removes all normal event spawns. Aliases: clear, clear-spawn, clearspawns, and clear_spawns.
/event setup lms add-final-spawn athena.event.setup Adds a final-stand spawn for LMS.
/event setup lms clear-final-spawns athena.event.setup Removes all LMS final-stand spawns.
/event setup sumo a athena.event.setup Sets Sumo participant spawn A.
/event setup sumo b athena.event.setup Sets Sumo participant spawn B.
/event setup sumo spec athena.event.setup Sets Sumo spectator spawn.
/event setup wool-shuffle first\|second athena.event.setup Sets Wool Shuffle arena bounds. The arena should contain a flat floor made from the configured wool colors.
/event setup rlgl first\|second athena.event.setup Sets Red Light, Green Light bounds. first is the starting side and second is the finish marker.
/event setup tnt-run first\|second athena.event.setup Sets TNT Run platform bounds.
/event setup tnt-tag first\|second athena.event.setup Sets TNT Tag arena bounds.
/events None Opens the event menu. A waiting event card is clickable for players to join or leave the queue.
/sumo join None Legacy shortcut for joining the active Sumo queue.
/sumo leave None Legacy shortcut for leaving the active Sumo queue.

<type> accepts lms, oitq, sumo, wool-shuffle, rlgl, tnt-run, or tnt-tag (each new event also accepts its underscore and compact aliases). The setup commands use the player's current world, coordinates, yaw, and pitch.

Configure Last Man Standing (LMS)

LMS is an elimination event in which the last remaining player wins.

  1. Stand at one corner of the arena and run:

text /event setup lms first

  1. Stand at the opposite corner and run:

text /event setup lms second

  1. Reset the normal spawn list before a fresh setup:

text /event setup lms clear-spawns

  1. Stand at every safe starting position and run /event setup lms add-spawn once per position. Add at least the configured lms.minimum_players (40 by default). The effective event maximum is also capped by the number of valid decoded spawn locations.

  2. Configure the final stand. Clear old positions, then add two or more final locations:

text /event setup lms clear-final-spawns /event setup lms add-final-spawn /event setup lms add-final-spawn

  1. Verify the setup:

text /event setup lms status

The command should report that the LMS arena is ready. If it is incomplete, the message identifies the missing bounds, normal spawns, or final spawns.

  1. Tune events.yml under lms before opening the queue. Important values are:
Key Default Description
minimum_players 40 Players required before the queue countdown begins.
maximum_players 50 Configured cap; the spawn list can impose a lower effective cap.
queue_start_seconds 60 Seconds to wait after the minimum is reached.
start_countdown_seconds 5 Countdown before teleporting players into the arena.
winner_credits 100 Credits awarded to the winner.
require_safezone_to_join true Requires joiners to be inside an Athena safe-zone region.
  1. Start the event:

text /event start lms

Players open /events and click the LMS card to join. Once the minimum is reached, Athena starts the queue countdown; reaching the maximum starts the event immediately. Use /event force-start for a smaller test queue.

During the match, Athena applies the configured LMS kit, prevents normal event participants from using commands or modifying the arena, and eliminates a participant on lethal damage. When two players remain, they are moved to the final-stand spawns. The winner receives lms.winner_credits and an Events Won increment. Use /event cancel if the event must be stopped.

Configure One In The Quiver (OITQ)

OITQ is a score-to-objective event. Players respawn at random arena spawns after kills, and the first player to reach the objective wins.

  1. Set the two corners of the arena:

text /event setup oitq first /event setup oitq second

  1. Clear old points and add one normal spawn per intended minimum player:

text /event setup oitq clear-spawns /event setup oitq add-spawn

Repeat add-spawn at each distinct location. The default minimum is 40, so add at least 40 valid locations unless you lower oitq.minimum_players.

  1. Verify the setup:

text /event setup oitq status

  1. Tune events.yml under oitq:
Key Default Description
minimum_players 40 Players required before the queue countdown begins.
maximum_players 50 Configured cap; the spawn list can impose a lower effective cap.
queue_start_seconds 60 Seconds to wait after the minimum is reached.
start_countdown_seconds 5 Countdown before the round begins.
kill_objective 20 Kills required to win.
wood_sword_damage 4.0 Damage used for regular event sword hits.
winner_credits 100 Credits awarded to the winner.
require_safezone_to_join true Requires joiners to be inside an Athena safe-zone region.
  1. Start the event and have players join from /events:

text /event start oitq

An event arrow hit scores a kill. A wooden-sword hit scores when it is lethal using the configured damage value. The killer receives another arrow, the victim is given the OITQ kit and teleported to a random configured spawn, and the first player at kill_objective wins.

Configure Sumo

Sumo uses the existing one-on-one arena flow. It needs two participant locations and one spectator location; it does not use cuboid bounds or normal spawn lists.

  1. Stand at the first platform and run:

text /event setup sumo a

  1. Stand at the opposing platform and run:

text /event setup sumo b

  1. Stand where eliminated or waiting players should watch and run:

text /event setup sumo spec

  1. Verify the three locations:

text /event setup sumo status

  1. Configure sumo.max_players, sumo.winner_credits, safe-zone requirements, wait/countdown values, and messages in events.yml, then open the queue:

text /event start sumo

Sumo must be started by an in-game staff member because its host is a player. With sumo.require_safezone_to_join: true, the host must also be standing in an Athena safe-zone region. Participants join from /events or the legacy /sumo join shortcut; /sumo leave leaves the queue. /event force-start and /event cancel are available to staff when needed.

Configure Wool Shuffle

Wool Shuffle uses a prebuilt, flat, multicolored wool floor. Players are given a target wool color each round; anyone standing on another block when the round resolves is eliminated.

  1. Set the two opposite corners around the wool floor:

text /event setup wool-shuffle first /event setup wool-shuffle second

  1. Add one spawn per player and verify the setup:

text /event setup wool-shuffle clear-spawns /event setup wool-shuffle add-spawn /event setup wool-shuffle status

  1. Tune wool_shuffle.colors, round_seconds, player limits, and messages in events.yml, then start it with /event start wool-shuffle.

Configure Red Light, Green Light

Red Light, Green Light is a race. Players may move during green light; movement during red light eliminates them. Reaching the second setup point wins.

  1. Stand at the starting side and run /event setup rlgl first. Stand at the finish marker and run /event setup rlgl second.
  2. Add race spawns with /event setup rlgl add-spawn and verify with /event setup rlgl status.
  3. Tune red_light_green_light.green_seconds, red_seconds, player limits, and messages. Start with /event start rlgl (aliases: red-light-green-light and red_light_green_light).

Configure TNT Run

TNT Run removes blocks beneath players as they move. Players who fall below the configured platform bounds are eliminated; the last remaining player wins. Athena restores every removed block when the event ends.

  1. Set the platform corners:

text /event setup tnt-run first /event setup tnt-run second

  1. Add one spawn per player and verify with /event setup tnt-run status.
  2. Tune tnt_run.remove_radius, player limits, and messages. Start with /event start tnt-run.

Configure TNT Tag

TNT Tag assigns one or more players the TNT tag. Hitting another participant transfers the tag. Tagged players are eliminated when the round timer expires; the last player wins.

  1. Set the two arena corners with /event setup tnt-tag first and /event setup tnt-tag second.
  2. Add one spawn per player and verify with /event setup tnt-tag status.
  3. Tune tnt_tag.round_seconds, initial_tagged_players, player limits, and messages. Start with /event start tnt-tag.

Event kit format

LMS and OITQ kits are configured in events.yml under lms.kit.items and oitq.kit.items. Each entry uses this compact form:

slot-or-armor;MATERIAL;amount;unbreakable;ENCHANT:level,ENCHANT:level

Examples:

lms:
  kit:
    items:
      - "helmet;DIAMOND_HELMET;1;true;PROTECTION:1,UNBREAKING:3"
      - "0;DIAMOND_SWORD;1;true;SHARPNESS:1,UNBREAKING:3"
oitq:
  kit:
    items:
      - "0;WOODEN_SWORD;1;true;"
      - "1;BOW;1;true;"
      - "2;ARROW;1;false;"

Armor slots are helmet, chestplate, leggings, and boots; other entries use a zero-based inventory slot. Material and enchantment names must be valid Bukkit/Paper names. Invalid entries are skipped.

Operations and troubleshooting

  • Arena reports incomplete: run the relevant status command. Check that both bounds decode in the same world, then count valid normal spawns. LMS also needs two final spawns.
  • The queue never starts: the queue countdown begins only after minimum_players join. Check the safe-zone requirement and lower the minimum temporarily for testing.
  • The configured maximum is not reached: Athena caps LMS/OITQ's effective maximum at the number of valid normal spawn locations. Add more spawns or lower maximum_players.
  • Players cannot join: with require_safezone_to_join: true, the player must currently stand inside a region marked safe zone. Use /region togglesafezone <region> or disable the event-specific setting.
  • A test event is stuck: run /event cancel. Participant snapshots are restored on cancellation, elimination, disconnect, and normal completion.
  • An arena is inaccessible to spectators: staff with athena.event.bypass can bypass the hosted-event movement and interaction restrictions for moderation.
  • After changing YAML: use /reloadathena for config-backed values. Setup commands write locations themselves; restart after plugin or dependency changes.

For command syntax see Command Reference, for all event keys see Configuration Reference, and for the event lifecycle see Feature Reference.