Wiki Release: 2026.09.8 · UltimateRaids: 0.12.0 · Documentation branch: 1

Admin GUI and raid editor#

The admin GUI is not a separate configuration system; it edits the same raid, scheduler, loot and runtime data used by the YAML files. It is intended to make common operations safer in-game while keeping advanced YAML available.

Open the admin hub#

/uraid gui

The current GUI configuration contains dedicated screens for:

raid list and raid editor;
general raid information;
entry/minigame and participation settings;
loadout and kit selection;
join/lobby NPC appearance;
locations, environment and border;
player death/disconnect/finish rules;
access requirements and cooldowns;
stages, objectives, waves and spawn groups;
bosses, phases, minions and equipment;
rewards and reusable loot;
actions and reusable skills;
display events, bossbar and scoreboard;
schedulers;
active runtime instances;
implementations/providers;
validation.

Chat-input fields#

Some GUI buttons open a chat-input capture rather than cycling fixed values. The next chat message becomes the requested value/path. Cancel/return through the GUI rather than continuing to type unrelated chat while an edit prompt is active.

Direct path editing#

For values that are faster to change manually:

/uraid edit <raid> <path> <value>

Examples:

/uraid edit ancient_crypt participation.max-players 8
/uraid edit ancient_crypt environment.border.enabled true
/uraid edit ancient_crypt environment.border.size 48

The command parser converts true/false, integers and decimals to native YAML types. ~ or null removes a value.

When YAML is better#

Use direct YAML for large lists, complex boss definitions, carefully formatted displays, custom processor options or copying a known-good raid between servers. After manual edits, reload and validate before testing.

Validation screen#

The validation GUI should be treated as a pre-flight check, not an optional cosmetic screen. It surfaces the same structural checks as /uraid validate <raid>.