How to configure the Tormented Square (Burning Kundun) in MU Online

The Tormented Square is a wave-based arena event that has become a favorite on MU Online servers looking for genuine cooperative challenge. The formula is classic and effective: groups of players enter a closed arena and face successive waves of monsters, each tougher than the last, until the final confrontation against the Burning Kundun — the flaming version of the legendary Kundun, with intensified HP and damage. Surviving every wave and bringing down the boss unlocks high-value rewards, which makes the Tormented Square one of the best endgame hooks an administrator can offer.

This guide is advanced because the event combines three configuration challenges at once: the entry control into the arena, the wave sequence with an advance condition, and the final boss with its rewards. All of them need to be in sync. I will use file names, tables and keys as examples; the structure is common to most emulators that implement the event, but the exact names, the IDs and some rules vary by emulator. If your server is not up yet, start with the tutorial on how to create a MU Online server and come back once the foundation is stable.

Prerequisites

The Tormented Square relies on wave logic and access control, so it demands a solid foundation before any tuning.

• A stable MU Online server, with the GameServer starting without errors.
• An active event process — in many emulators the event is handled by an EventServer or a dedicated module. Confirm which one yours uses.
• The MuOnline database accessible via SSMS, with permission to create and alter tables.
• The Tormented Square arena map present on both the server and the client.
• A text editor that preserves encoding (Notepad++), saving in the same standard as the other files.
• A full backup of the database and the configuration folders before you start.

> Test with a GM account before releasing. A poorly configured wave event tends to "stall" on an intermediate wave — the monsters do not advance and players are stuck until time runs out. Discovering this with a GM is trivial; discovering it with 40 players in the event triggers a flood of complaints.

How the Tormented Square works under the hood

Before editing files, understand the flow. The event has four components that form a chain:

1. Entry control — who can enter, with what item/cost and in which time window.
2. Arena map — the dedicated map index where the waves take place.
3. Wave sequence — the ordered list of spawns, with the condition that triggers the next wave (typically "eliminate all monsters in the current wave").
4. Boss and rewards — the Burning Kundun on the final wave and what it/the event grants when defeated.

The golden rule: entry → waves in order → boss → reward. If the wave-advance condition is not met, the flow stops; if the boss has no spawn on the final wave, the event never concludes. Keeping the chain continuous is the central goal of this guide.

Step 1: Confirm the arena map

Every map event starts with the correct map index.

1. Open the GameServer map definition (example: Data/MapInfo.txt).
2. Locate the Tormented Square map and note the numeric index.
3. Confirm that the client has the corresponding map file.

; Illustrative example (the REAL index varies by emulator)
; Format: Index  Name  ... flags
ZZ  Tormented_Square  ...

> Do not copy the index from another server. Different emulators (and different versions of the same emulator) may use different indexes for the same event. A wrong index makes the waves spawn on the wrong map — or not spawn at all.

Step 2: Enable the event and set the schedule

Activate the Tormented Square in the event configuration file and define the window.

; Example configuration block (key names vary by emulator)
[TormentedSquare]
Enable=1
MapNumber=ZZ           ; map index from Step 1
WaveCount=5            ; number of waves
Duration=30           ; maximum event time in minutes
EntryItemIndex=<entryItem>   ; item required to enter
EntryLevelMin=380     ; minimum level to participate
Schedule=13:00,19:00,23:00

Most relevant parameters:

> Since the Tormented Square is an endgame event, use a minimum level compatible with your server's cap. Without that filter, weak characters get in, die on the first wave and ruin the group's experience. EntryLevelMin is what keeps the arena filled with participants able to progress.

Step 3: Configure the entry control

Entry is what gives the event its exclusivity. The most common pattern is to require an entry item (an "invitation"/scroll) and/or to go through an NPC within the time window.

-- Example: confirm the entry item in the item base
-- (table and columns vary by emulator)
SELECT ItemIndex, ItemName
FROM MuOnline..ItemBase
WHERE ItemIndex = <entryItem>;

If the event uses an entry NPC, confirm it exists and is placed on the main map. Also define how the player is moved to the arena — normally the system teleports the character (or the group) to the starting coordinates of map ZZ once entry is validated.

Entry best practices:

1. Make the entry item a reward from other content (drops, events, event shop), building an economy around access.
2. Decide between individual or group entry; wave arenas tend to work better with organized groups.
3. Close entry as soon as the first wave begins, so no one enters an arena already in progress.

Step 4: Configure the wave sequence

The heart of the event is the ordered list of waves. Each wave is a set of spawns; once all the monsters in a wave are eliminated, the next one is released.

; Illustrative wave example on map ZZ
; Typical format: Wave  Map  MonsterID  Count  X  Y
1  ZZ  <weakMob>   10  120  120
2  ZZ  <mediumMob>   12  120  120
3  ZZ  <strongMob>   14  120  120
4  ZZ  <eliteMob>   16  120  120
5  ZZ  <burningKundun>  1  120  120   ; final wave: the boss

Points of attention:

1. Scale the difficulty gradually — each wave a little tougher than the previous one. Sudden jumps frustrate; smooth progression keeps players hooked.
2. Ensure the advance condition. In most emulators, the next wave only triggers when all monsters in the current one die. Confirm that no monster spawns on an unreachable coordinate, or the group cannot clear the wave and the event stalls.
3. Reserve the last wave for the boss. The Burning Kundun should be the only one on the final wave, with a single spawn.

Step 5: Configure the Burning Kundun

The Burning Kundun is the climax and requires attention on three points: existence in the base, calibrated attributes and a reward on death.

-- Example: confirm the Burning Kundun exists and is enabled
-- (table/column name varies by emulator)
SELECT MonsterID, MonsterName, Enable
FROM MuOnline..MonsterBase
WHERE MonsterID = <burningKundun>;

-- Enable it if disabled
UPDATE MuOnline..MonsterBase
SET Enable = 1
WHERE MonsterID = <burningKundun>;

If the monster attributes in your emulator live in a text file (example: Data/Monster.txt), adjust HP, attack, defense and EXP of the Burning Kundun there. Calibrate it so the final fight is tense but winnable by the typical group on your server — the boss should be the hardest moment, not an impossible wall.

> A common mistake is to copy the normal Kundun's attributes and forget to intensify them. The "Burning" exists precisely to be stronger; if it dies as fast as the regular Kundun, the climax is lost. Raise HP and damage enough to make the final wave memorable.

Step 6: Define the rewards

The rewards justify the entry cost and the effort of the waves. They can drop from the Burning Kundun itself or be granted via a reward system upon completing the event.

-- Illustrative boss drop / completion reward example
UPDATE MuOnline..ItemDrop
SET DropRate = 25
WHERE MonsterID = <burningKundun>
  AND ItemIndex = <prizeItem>;

Guidelines for a healthy economy:

• The Burning Kundun should concentrate the best drops, with low chances, to make completion valuable.
• Consider a guaranteed completion reward (event currency, materials) on top of the random drops, so groups that finish the event never leave empty-handed.
• Do not duplicate rare items that are already easily obtained elsewhere; exclusivity is what makes the Tormented Square appealing.

Step 7: Sync the client and test

1. Ensure the client has the arena's map file and the models of the monsters and the Burning Kundun.
2. Distribute any custom files via patch/launcher.
3. Start the services in order: DataServer → ConnectServer → GameServer → event process (last).
4. Temporarily set Schedule to a nearby time, restart the event process and run a full test: entry, wave 1, wave advance, Burning Kundun spawn on the final wave, boss death and reward delivery.

In the event log, confirm the stages: event started, wave N started/completed, boss spawned and event finished.

Common errors and fixes

> After changing waves, boss attributes or entry rules, restart the event process. This data is almost always read at startup and not in real time; changes "with no effect" are usually a missing restart.

Operational best practices

• Announce the event with a global message before each window; groups need to organize.
• Monitor the logs in the first weeks to catch stalling waves or problematic coordinates.
• Tune the difficulty curve as you observe how many groups finish — if almost no one clears, ease it up; if everyone clears easily, tighten it.
• Review the rewards periodically to keep pace with the economy's evolution.
• Document the indexes, IDs, waves and schedules used, so you do not rely on memory during maintenance.

Launch checklist

• Full backup of the database and configurations done
• Arena map index confirmed in MapInfo
• Event enabled (Enable=1) with correct MapNumber and Schedule
• Entry control (item/NPC) validated and minimum level set
• Wave sequence with progressive difficulty and advance condition tested
• All monsters in each wave on reachable coordinates
• Burning Kundun with a single spawn on the final wave and intensified attributes
• Boss/completion rewards defined and tested
• Client with map and models distributed via patch
• Full test on a GM account: entry, waves, boss and reward validated
• Entry closing when the first wave starts enabled
• Global announcement configured before each window

With entry, waves, boss and rewards forming a continuous chain — and the difficulty curve calibrated to your players' real power — the Tormented Square becomes one of the server's best endgame challenges. Tune the waves and prizes by watching how many groups manage to bring down the Burning Kundun, and the event will become the trial by fire that your strongest players will want to repeat every week.

Frequently asked questions