CustomArena.xml

Scheduled PvP tournament arenas. Each arena defines its own schedule, entry gates (level / reset / master reset), class whitelist, point scoring, and teleport targets. Up to 30 independent arenas can be scheduled on one server.

File Location#

Data/Plugins/Events/CustomArena.xml

Loaded once at GameServer startup. Supports hot reload via plugin admin command.

Root Attributes#

<CustomArena Enabled="..." VictimScoreDecrease="..." KillerScoreIncrease="...">

Messages#

19 customizable message strings inside a <Messages> block. Each <Text Id="N" Value="..."/> replaces the default broadcast for that event type.

<Messages>
    <Text Id="1" Value="[%s] will close in %d minute(s)"/>
    ...
</Messages>

Keep the format specifiers or replacement text will be garbled.

Arenas#

Each arena is wrapped in its own <Arena Index="0-29"> block and contains its own <Schedule> and <Rules> elements. The schedule is per-arena, not global.

<Arena Index="0">
    <Schedule>
        <Time Year="-1" Month="-1" Day="-1" DayOfWeek="-1" Hour="20" Minute="0" Second="0"/>
    </Schedule>
    <Rules Name="..." AlarmTime="..." StandTime="..." EventTime="..." CloseTime="..."
           StartGate="..." FinalGate="..."
           MinUser="..." MaxUser="..." MaxDeath="..."
           MinLevel="..." MaxLevel="..."
           MinMasterLevel="..." MaxMasterLevel="..."
           MinReset="..." MaxReset="..."
           MinMasterReset="..." MaxMasterReset="..."
           DW="..." DK="..." FE="..." MG="..." DL="..." SU="..." RF="..." />
</Arena>

Schedule#

<Time Year="-1" Month="-1" Day="-1" DayOfWeek="-1" Hour="20" Minute="0" Second="0"/>

-1 = wildcard. DayOfWeek: 1 = Sunday through 7 = Saturday. Multiple <Time> entries can be added to schedule the same arena at several instants.

Rules#

Class gate values#

Each class attribute accepts a small integer that sets the maximum tier allowed for that class. The value is compared against the character's class-change tier plus one.

Default when the attribute is omitted is 1.

Match Lifecycle#

Each arena cycles through these states:

1. Empty - Counting down to the next scheduled start. AlarmTime minutes before start, entry opens and countdown announcements begin.
2. Stand - Entry closed. Waits StandTime minutes for participants to gather. Drops back to Empty if participant count falls under MinUser.
3. Start - Combat phase, lasts EventTime minutes. Ends early if only one player remains.
4. Clean - Ranks are calculated and saved to the ranking database. Winner announcement broadcast server-wide. CloseTime minutes before the arena returns to Empty and players are teleported out via FinalGate.

Players exceeding MaxDeath are teleported to FinalGate mid-match and their rank is locked at 0.

How players join#

Players join from the Move window (M). Each arena needs a Move.txt row whose gate is that arena's StartGate. The shipped file has "Arena Survivor" and the seven class arenas (Move indices 70-77 → gates 750-757). A move to an arena outside its entry window is refused with message 9 ("This arena is not currently open"); class, level and reset rules are checked at that moment.

Kill Scoring#

On each kill inside an active arena:

• Victim loses VictimScoreDecrease points (floored at 0), kill streak resets, death count and death streak increment.
• Killer gains KillerScoreIncrease points, kill count and kill streak increment, death streak resets.

Cross-File Dependencies#

Common Issues#

• Arena never starts, nobody can join - no Move.txt row points at its StartGate, so MinUser is never reached
• Arena starts but players teleport to wrong map - StartGate points at a gate that is not on the Silent Map
• No one can enter at level 400 - MaxLevel set below 400 for a high-level server; raise it
• Winner announce shows literal %s %s - message text missing a format specifier; the engine uses positional parameters
• Class filter rejects everyone - every per-class flag (DW/DK/FE/MG/DL/SU/RF) is 0; at least one must be nonzero for anyone to enter
• Points go negative - cannot happen; victim score is floored at 0. If you see negative on-screen values, it is a display bug, not a score bug
• Arena never triggers - missing <Schedule> block inside the <Arena> node, or all <Time> entries have already passed with no recurring wildcard