Brazil's biggest MU Online portal — since 2003
Tutorial Intermediate Tutoriais

How to Configure Chaos Castle on MU Online Server

Complete guide to configuring the Chaos Castle event on your MU Online server: INI files, SQL tables, schedules and troubleshooting.

VI ViciadosMU Team · Updated on 3 jul 2026 · ⏱ 12 min read

Introduction

Chaos Castle is one of the most popular MU Online events, placing players on a shrinking platform until only one survivor remains. Configuring it correctly requires adjustments to configuration files, database tables, and EventServer parameters. This guide covers the complete setup for Season 6 Episode 3 servers running MuServer with SQL Server.

Nota: This guide was written for MuServer Season 6 EP3. On older versions (S2-S4), configuration files live exclusively under GameServer/Data/Events/ with no separate EventServer involved.

Prerequisites

  • SQL Server 2008 or later with the MuOnline database configured
  • GameServer, ConnectServer, and EventServer installed and functional
  • Administrator access to the Windows server
  • SQL Server Management Studio (SSMS)

Step 1: Verify the File Structure

Before any configuration, confirm that the event files exist in the correct directories.

GameServer/
  Data/
    Events/
      ChaosCastle/
        ChaosCastle.txt
        ChaosCastleReward.txt
        ChaosCastle_ItemList.txt
EventServer/
  Data/
    ChaosCastle/
      IGS_ChaosCastle.txt

If ChaosCastle.txt or ChaosCastleReward.txt are missing, copy them from the server installation package before continuing.


Step 2: Configure ChaosCastle.txt

Open GameServer/Data/Events/ChaosCastle/ChaosCastle.txt in a text editor (Notepad++ is recommended to avoid encoding issues).

; Chaos Castle Configuration
; Format: Level, MinLevel, MaxLevel, MaxUserCount, StayTime, PlayTime, MapNumber

1  15  49  80   3  15  29
2  50  99  100  3  15  29
3  100 149 100  3  15  29
4  150 199 100  3  15  29
5  200 249 100  3  15  29
6  250 299 100  3  15  29
7  300 400 200  3  15  29

Field reference:

  • Level: Chaos Castle tier (1 to 7)
  • MinLevel/MaxLevel: Character level range allowed to participate
  • MaxUserCount: Simultaneous player cap per instance
  • StayTime: Waiting-room hold time in minutes before the event starts
  • PlayTime: Event duration in minutes
  • MapNumber: Map ID (29 = Chaos Castle)
Dica: Lower MaxUserCount to 50 on servers with fewer than 100 online players so the lobby fills faster and the event feels competitive.

Step 3: Configure Rewards

Edit GameServer/Data/Events/ChaosCastle/ChaosCastleReward.txt:

; Format: CCLevel, ItemCode, ItemIndex, ItemLevel, ItemDurability, ExcellentOption, Zen
1  13  8   5  255  0  5000000
2  13  8   6  255  0  7000000
3  13  36  6  255  0  8000000
4  13  36  7  255  0  9000000
5  13  37  7  255  0  10000000
6  13  37  8  255  0  12000000
7  13  37  9  255  0  15000000
Atenção: ItemCode 13 corresponds to the Jewel of Chaos. Make sure the ItemIndex and ItemLevel values exist in the client's Item.bmd. Invalid values will crash the GameServer when delivering the reward.

Step 4: Schedule the Event in the Database

Open SSMS and connect to the MuOnline database. Run the script below to set Chaos Castle schedules (Event_Code = 8):

-- Remove old Chaos Castle schedule entries
DELETE FROM IGS_Event_TimeTable WHERE Event_Code = 8;

-- Insert new schedules (example: every 2 hours)
INSERT INTO IGS_Event_TimeTable (Event_Code, StartHour, StartMinute, IsActive)
VALUES
  (8, 0,  0,  1),
  (8, 2,  0,  1),
  (8, 4,  0,  1),
  (8, 6,  0,  1),
  (8, 8,  0,  1),
  (8, 10, 0,  1),
  (8, 12, 0,  1),
  (8, 14, 0,  1),
  (8, 16, 0,  1),
  (8, 18, 0,  1),
  (8, 20, 0,  1),
  (8, 22, 0,  1);
Nota: Some MuServer builds use the table T_IGS_Event_Time instead of IGS_Event_TimeTable. Run SELECT name FROM sysobjects WHERE xtype = 'U' AND name LIKE '%Event%' to confirm the exact table name in your database.

Step 5: Enable the Event in the Control Table

Check and activate Chaos Castle in the event control table:

-- Check current state
SELECT * FROM IGS_ChaosCastle_Info;

-- Enable the event
UPDATE IGS_ChaosCastle_Info
SET Operate = 1,
    MinUserCount = 2,
    MaxPlayTime = 15,
    WaitingTime = 3
WHERE Event_Code = 8;

If the table IGS_ChaosCastle_Info does not exist, use:

-- Enable via generic event table (older builds)
UPDATE IGS_EventInfo
SET Operate = 1
WHERE Event_Code = 8;

Step 6: Configure the EventServer

Open EventServer/EventServer.ini and locate the Chaos Castle section:

[ChaosCastle]
Enable=1
ServerCode=0
GameServerIP=127.0.0.1
GameServerPort=55557
MinPlayerToStart=2
MaxWaitTime=180
EventDuration=900

Key parameters:

  • Enable: 1 to activate, 0 to disable
  • MinPlayerToStart: Minimum players required to start the event (recommended: 2 for smaller servers)
  • EventDuration: Duration in seconds (900 = 15 minutes)
  • GameServerPort: Internal communication port between EventServer and GameServer
Atenção: The GameServerPort in EventServer.ini must match the EventServerPort parameter in GameServer/GameServer.ini. A mismatch silences the event without generating a visible error in the main logs.

Step 7: Configure GameServer.ini

Open GameServer/GameServer.ini and confirm the Chaos Castle-related parameters:

[EventServer]
Enable=1
EventServerIP=127.0.0.1
EventServerPort=55557

[ChaosCastle]
Enable=1
MapNumber=29

Step 8: Test the Event

Follow this sequence to test without waiting for a scheduled time:

  1. Restart the EventServer
  2. Restart the GameServer
  3. Connect to the server with a GM account
  4. Type in chat: /chaoscastle 1 (or the equivalent command for your build)
  5. Join with at least one additional character to meet MinPlayerToStart
Dica: On many MuServer builds, the GM force-start command is /event chaoscastle or available through the web administration panel. Check GameServer/Data/Command.txt for the exact commands supported by your version.

Troubleshooting

Event does not open on schedule

  1. Confirm IGS_Event_TimeTable has rows with Event_Code = 8 and IsActive = 1
  2. Verify the EventServer is running: tasklist | findstr EventServer
  3. Review EventServer/Log/EventServer_YYYYMMDD.log for connection errors

Players cannot enter

-- Check the configured level range
SELECT * FROM IGS_ChaosCastle_Info;

-- Confirm the map is enabled
SELECT * FROM IGS_MapInfo WHERE MapNumber = 29;

GameServer crashes when delivering rewards

Verify that all items in ChaosCastleReward.txt exist on the client side. Items with ItemLevel higher than the maximum allowed (typically 15) cause a crash on reward delivery:

-- Recent error log entries
SELECT TOP 50 * FROM T_Log_Error
ORDER BY LogDate DESC;

Final Notes

With all steps completed, Chaos Castle will run automatically on schedule. Monitor the first few event cycles by watching the logs under EventServer/Log/ and GameServer/Log/ to ensure stable communication between services. Adjust MinUserCount upward as your server population grows.

Perguntas frequentes

What is the maximum number of players in Chaos Castle?

It depends on the event level. CC1 accepts up to 80 players, CC2-CC6 accept up to 100, and CC7 (available from Season 6 onward) accepts up to 200 players per instance.

The event is not opening at the configured time — what should I check?

Confirm that the Operate field in IGS_ChaosCastle_Info is set to 1, that the schedule rows in IGS_Event_TimeTable have Event_Code = 8, and that the EventServer is running and connected to the GameServer.

How do I change the Chaos Castle reward items?

Edit the IGS_ChaosCastle_Reward table in SQL Server or the file ChaosCastleReward.txt under GameServer/Data/Events/ChaosCastle/, replacing or adding ItemCode and ItemLevel values as needed.

Players are falling off the map during the event. What causes this?

This happens when the player limit is exceeded or there is a desync between EventServer and GameServer. Check the logs under EventServer/Log/ and temporarily lower MaxUserCount to diagnose.

VI

ViciadosMU Team

Equipe editorial do ViciadosMU — portal de MU Online no ar desde 2003.

Keep reading

Related articles