Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanGladiator

ClanGladiator#

ClanGladiator adds clan-versus-clan arena event with recruitment, leader lineup confirmation, server kits or own items, spectators, schedules, rewards, world border, protection modes, history and recovery. The pages in this section explain what players see in-game, what administrators need to configure, the normal setup flow, and the most common problems you may need to diagnose.

Compatibility#

Component version: 4.0.0
Documentation release: 2026.09.5
Minimum UltimateClans version: 9.1.3
Minimum Minecraft generation: V118

What you can do with it#

Run /clanglad wand, select both arena corners, then /clanglad arena create <arena>
Stand at the waiting location and run /clanglad arena setlobby <arena>, then set the return point with setexit
Add enough independent clan combat points with /clanglad arena addspawn <arena>; use arena info to validate the setup
Choose serverkit or ownitems. For serverkit, prepare your inventory, run /clanglad kit create <kit>, then assign it with arena setkit
Set clan/player limits, recruitment/countdown/max duration/shrink/finishing times, border size, timeout resolution and block protection
Configure rewards with arena reward addcommand and/or additem

How it works#

Event lifecycle#

A Gladiator event moves through recruitment/waiting, countdown, active combat and finishing states. Clans join as teams; the event normally ends when only one eligible clan remains or when the configured maximum duration/timeout resolution decides the result. Friendly clan combat and arena protection are handled by the event rules rather than by manually changing global server PvP.

The admin GUI mirrors the command workflow: arenas, identity, locations, limits, times, rules and rewards can be edited without requiring YAML edits for ordinary event setup. YAML remains useful for defaults, visuals, scheduler behavior and global safety policies.

First setup#

Before enabling the feature for players, review these installed files:

commands.yml
config.yml
gui.yml
languages/Lang_EN.yml
languages/Lang_ES.yml
polymart.yml

Recommended in-game workflow#

Run /clanglad wand, select both arena corners, then /clanglad arena create <arena>.
Stand at the waiting location and run /clanglad arena setlobby <arena>, then set the return point with setexit.
Add enough independent clan combat points with /clanglad arena addspawn <arena>; use arena info to validate the setup.
Choose serverkit or ownitems. For serverkit, prepare your inventory, run /clanglad kit create <kit>, then assign it with arena setkit.
Set clan/player limits, recruitment/countdown/max duration/shrink/finishing times, border size, timeout resolution and block protection.
Configure rewards with arena reward addcommand and/or additem.
Enable the arena, then use /clanglad start <arena> for recruitment. Players use /gladiator join <arena>; if lineup confirmation is required, the clan leader confirms the lineup.
Use /clanglad forcestart only when you intentionally want to bypass the normal waiting flow. Schedules can automate event opening.

Useful command entry points#

/clanglad help
/clanglad admin [arena]
/clanglad wand
/clanglad arena help
/clanglad arena create
/clanglad arena delete
/clanglad arena list
/clanglad arena info
/clanglad arena setlobby
/clanglad arena setexit
/clanglad arena addspawn
/clanglad arena clearspawns
/clanglad arena enable
/clanglad arena setmode
/clanglad arena setkit
/clanglad arena setlimit
/clanglad arena settime
/clanglad arena setborder

See Commands in the sidebar for the full command reference and configured aliases/permissions.

GUI areas#

The installed GUI configuration contains screens/sections such as:

Gui
Admin.home
Admin.arenas
Admin.arena
Admin.identity
Admin.locations
Admin.limits
Admin.times
Admin.rules
Admin.rewards
Admin.kits
Admin.kit
Admin.schedules
Admin.schedule
Admin.settings
Admin.history

What administrators should configure#

Use arena info after every structural change; an arena should have bounds, lobby, exit and usable combat spawns before production.
For serverkit mode, configure inventory restrictions deliberately: storage/armor/offhand/cursor checks exist to prevent item duplication or unintended carry-over.
Select NORMAL/INDESTRUCTIBLE/REGENERATE protection according to whether blocks should be changed and later restored.
Test player disconnect/reconnect and a forced stop once; recovery storage exists specifically to restore interrupted sessions.

Configuration map#

config.yml — file-version; General (debug, allow-multiple-events, prevent-non-participants-in-arena, disconnect-grace-seconds, lobby-radius, restore-health-on-exit, teleport-to-arena-exit, allowed-commands, arena-rules); Default-Arena (enabled, display-name, icon, mode, kit, min-clans, max-clans, max-players-per-clan, recruitment-seconds, countdown-seconds, max-duration-seconds, shrink-at-remaining-seconds); Server-Kit (force-survival, clear-potion-effects-on-entry, require-empty-storage, require-empty-armor, require-empty-offhand, require-empty-cursor, block-inventory-containers, block-item-drop, block-item-pickup); WorldBorder (enabled, warning-distance, warning-time, portal-teleport-boundary); Rewards (recipient-scope, run-commands-for-offline-players, drop-overflow-items-at-exit); Scheduler (enabled, check-interval-seconds); Visuals (scoreboard, bossbar, actionbar, announcements); Spectator (enabled, allow-external-players, allow-eliminated-players); Lineup (require-leader-confirmation)

The Configuration page lists the available paths and defaults from the installed configuration, with notes on what each area controls.

Before going live#

Back up the component data/configuration.
Start the server and confirm the component is detected without startup errors.
Test with a non-OP player and the lowest clan role that should have access.
Exercise the complete flow once, including the failure/deny path, not only the happy path.
Restart the server and verify that persistent state survives.
If the network is multiserver, repeat the test from a second node and verify storage/synchronization.

Troubleshooting quick reference#

Symptom	Likely cause	What to check
Arena will not start or enable	Selection/setup is incomplete, too few spawns, disabled arena, missing server kit, or participation limits cannot be satisfied	Run `/clanglad arena info <arena>` and correct every missing setup field; verify mode/kit and min/max limits.
Player cannot join serverkit event	Inventory safety rule rejects armor, offhand, cursor or storage items, or player/clan limit was reached	Read the rejection message and `Server-Kit.*` settings; empty the required slots and retry.
Event stays in recruitment/countdown	Minimum clans or leader lineup confirmation has not been satisfied	Check joined clans, `Lineup.require-leader-confirmation`, and the configured minimum clan count.
World border is not visible/shrinking	WorldBorder is disabled, shrink time/final size is invalid, or the optional border implementation is unavailable	Check `WorldBorder.enabled`, arena timing and final size; inspect startup integration logs.
Players keep event inventory after stop/restart	Session/recovery restore did not complete	Do not delete recovery data; stop cleanly, check recovery/storage errors, then retest with a disposable account.
Blocks are not restored	Arena protection is NORMAL or regeneration snapshot could not be applied	Use REGENERATE when rollback is required and verify the arena bounds before the event starts.
Scheduler does not open event	Scheduler disabled, schedule entry disabled/invalid, or server time does not match the configured HH:mm/day rule	Check `Scheduler.enabled`, `/clanglad schedule list`, server clock/timezone and arena enabled state.

For a longer diagnostic flow, open the Troubleshooting page for this component.