Getting startedguide

First steps

Create, configure and run your first event from the panel.

Everything below happens in /captureadmin. Nothing needs a text editor.

Creating an event

Open the panel

/captureadmin lists the configured events and lets you create one.

Pick a type

The type selector shows the eight types with a short description of each. The type decides which settings screen you get afterwards, and it is chosen once.

Give it an id

The id is the key: it is what /captureadmin start <id> takes and what placeholders name.

Select the zone

The setup screen hands you the selection wand: left click for one corner, right click for the other. The zone is a cuboid. Payload asks for a start and an end point instead, Destroy The Core asks for a single block, and Bounty needs no zone at all.

Tune the settings

Each type has its own screen — capture time, target points, speeds, regeneration. The defaults are listed in Event types.

Add rewards

Winner, and first, second and third place, edited with the reward editor. See Rewards.

Enable it

An event that is not enabled cannot be started, by hand or by schedule.

Start it

/captureadmin start <id>, or a schedule. /captureadmin list shows what is running and /captureadmin stop <id> ends it.

What a running event needs

Type	Zone requirement
`koth`, `koth_points_exclusive`, `koth_points_multi`, `koth_capture_points`	One cuboid zone
`conquest`	One or more zones, each with its own name, colour, points and capture time
`payload`	A start location and an end location, joined by rails
`dtc`	One block location
`bounty`	Nothing: the target is picked when it starts

Conquest needs a clan plugin

Conquest attributes captures by clan tag. With no clan provider detected, its zones never register a capturer. See Clans.

Who counts as playing

Being inside the zone is geometry; counting is not. A player is ignored while they are dead, in creative or in spectator mode, or — with ExyliaStaff installed — in staff mode or vanished. Switching gamemode, or staff mode or vanish, inside a zone is re-evaluated immediately, not on the next sweep.

Staff on duty are ignored outright: they hold nothing, score nothing, are never picked as a bounty target, cannot claim one, and are not told they cannot capture.

A sensible first event

A plain koth is the shortest path to something working:

capture-time at the default 30000 ms.
Leave infinite off so the event ends on the first capture.
Set a winner reward.
Start it by hand with /captureadmin start <id> before trusting it to a schedule.

Once that runs, Scheduling makes it recurring.

Something missing on this page? Tell us on Discord