How to configure the White Wizard Invasion in MU Online

The White Wizard Invasion is one of the most complete invasion events in MU Online because it combines two elements that, on their own, already sustain other events: a horde of monsters that takes over the maps and a commander boss, the White Wizard himself, who leads the attack. At predefined times, the server announces the arrival of the White Wizard and his army invades early and mid-game maps — typically Lorencia, Devias and Noria. Players must first fight their way through the horde of minions and, at the end, face the boss, who carries the invasion's most coveted reward. This two-layer structure makes the White Wizard more strategic than a simple invasion, and that is exactly what this guide teaches you to configure: schedule, army, boss, drops and diagnostics. As usual, the file and key names are examples; the exact naming varies by emulator (classic Season 6, MuEMU, IGCN, X-Files and their derivatives), but the logic is the same in all of them.

If your server is not up yet, start with the guide on how to create a MU Online server and come back once the GameServer and the MuOnline database are running.

Prerequisites

Before editing any file, check:

• A working GameServer from a Season that includes the boss-based invasion system.
• The MuOnline database accessible via SSMS or an equivalent tool.
• Administrative access to the server directories, especially GameServer/Data/.
• Notepad++ or a similar editor, saving in the encoding the build expects (ANSI on the classics; UTF-8 on many modern ones).
• A full backup of Data/ and the database before touching anything.

> Tip: because it involves a boss, the White Wizard requires more calibration testing than a simple invasion. Set aside an off-peak window to tune the White Wizard's HP and the size of the horde.

How the White Wizard Invasion works

The event is controlled by the GameServer. An invasion file (for example GameServer/Data/Event/Invasion.txt, WhiteWizardInvasion.txt or an EventInvasion section) describes four blocks:

1. Schedule — the times or interval of the trigger.
2. Army — the IDs and quantity of the minions that make up the horde.
3. Boss — the White Wizard's ID, usually on a separate line, with much higher HP.
4. Reward — the drop tables, normally distinct for minions and for the boss.

At the scheduled time, the GameServer issues a global announcement, instantiates the horde and positions the boss. In many builds, the White Wizard only grants his reward when defeated, and some emulators globally announce who landed the final blow. Understanding this layered structure — schedule, army, boss and drop — is the secret to a stable configuration.

Step 1: Locate the invasion file

Explore GameServer/Data/ looking for the event files. Typical structure (varies by emulator):

GameServer/
└── Data/
    ├── Event/
    │   ├── Invasion.txt
    │   ├── WhiteWizardInvasion.txt
    │   └── EventInvasion.txt
    ├── MonsterSetBase.txt
    └── Monster/
        └── Monster.txt

In builds that group invasions in a single file, look for the entry named White Wizard or Mago Branco. Back it up before editing:

copy "GameServer\Data\Event\WhiteWizardInvasion.txt" "GameServer\Data\Event\WhiteWizardInvasion.bak"

Step 2: Set the schedule

Locate the schedule and adjust the times. Example:

[WhiteWizardInvasion]
Enable = 1
; Duration of each invasion in minutes
Duration = 25
; Start times (24h, HH:MM), comma-separated
Schedule = 02:00,08:00,14:00,20:00
; Announcement on start
Notice = 1
NoticeText = "The White Wizard and his army have invaded the continent!"

A cyclic-interval alternative, if the build supports it:

IntervalMinutes = 180
FirstRunAfterBootMinutes = 40

> Note: the GameServer uses the operating system clock. A server in UTC with a Brazilian audience (UTC-3) requires adding 3 hours. Check with tzutil /g and sync with w32tm /resync /force.

Step 3: Configure the army (the horde of minions)

Here you define the common monsters that accompany the White Wizard. The ideal is to use themed creatures at a level compatible with the invaded maps:

; Format: MapNumber MonsterID Count Dispersion
; MapNumber: 0=Lorencia, 2=Devias, 3=Noria
0   14   12   3   ; Skeleton Warriors in Lorencia
0   20    8   3   ; Elite Skeletons in Lorencia
2   45   10   3   ; Minions in Devias
3   16    8   3   ; Minions in Noria

The IDs above are examples — the real numbering varies by emulator. Always validate in Monster.txt. The Dispersion field spreads the minions around the base coordinate, preventing them from clumping in a single spot and creating the sense of an army taking over the map.

Step 4: Configure the boss (White Wizard)

This is the layer that sets the event apart. The White Wizard usually sits on a separate line, with quantity 1 and HP far higher than the minions':

; Boss on its own line: MapNumber MonsterID Count Dispersion
0   150   1   0   ; White Wizard in Lorencia (fixed position)

> Note: in many builds, if you forget this line, only the horde appears and the boss never shows up — the number-one cause of "only the minions come" complaints. Confirm that the boss ID is present and enabled.

The table below summarizes the event's layered structure:

Step 5: Adjust the White Wizard's HP and level

The boss needs to be resistant enough to demand a collective effort, but not so tough that it survives beyond the Duration:

; ID   Name             Level  HP      MinDmg MaxDmg Def
150   "White Wizard"    95     500000   350    420    200
14    "Skeleton Warrior" 25     3500      40     60     30

Calibrate the boss's HP to the average damage of the server's guilds. A good target is for an organized group to bring it down in 5 to 10 minutes — enough time to create competition, but within the event window.

Step 6: Configure the drops (minions and boss separated)

The White Wizard's strength is having two distinct drop tables. The minions drop modest rewards; the boss carries the main prize:

; Drop from the common minions
DropGroup = WhiteWizardMinions
Item = JewelOfBless   Rate = 800     ; 8% (base 10000)
Item = JewelOfSoul    Rate = 800     ; 8%
Item = Zen            Rate = 10000    ; always drops zen

; Drop from the White Wizard boss (exclusive bag)
DropGroup = WhiteWizardBoss
Item = BoxOfKundun5   Rate = 10000    ; 100%
Item = JewelOfLife    Rate = 5000     ; 50%
Item = JewelOfCreation Rate = 3000    ; 30%
Item = AncientItem    Rate = 1500     ; 15% (random ancient item)

Separating the bags is essential: if every monster used the boss's table, the economy would collapse within days. Keep the minions' drop lean and concentrate the generosity on the White Wizard, rewarding those who actually bring down the commander.

Step 7: Configure the global announcement

Communicate the start and, if the build supports it, the boss kill:

NoticeType = 2          ; 0=chat, 1=blue, 2=blinking gold
NoticeRepeat = 3
NoticeText = "White Wizard Invasion! Defeat the White Wizard in Lorencia!"
; Some builds announce the boss killer:
BossKillNotice = 1
BossKillText = "%s defeated the White Wizard and seized his treasure!"

Step 8: Restart and test

1. Save the files in the build's correct encoding.
2. Restart the GameServer — invasions are read at boot.
3. Watch the console/log for [Invasion] WhiteWizard loaded and the line for the next scheduled time.
4. For a quick test, set the Schedule to 1-2 minutes ahead and restart.
5. Log in with a character: confirm the announcement, the appearance of the horde and the boss, the White Wizard's behavior and the two drop tables.

Many emulators offer a GM command to force the event, such as /whitewizard or /invasion. Check your build's command list and document it for the team.

Common errors and fixes

Balancing best practices

• Respect the two layers: the horde should slow players down, the boss should reward. If the minions are too weak, there is no challenge; if the boss is easy, there is no competition.
• Concentrate the prize on the boss: it is what gives the event its identity and avoids inflating the economy with horde drops.
• Calibrate the boss's HP to the strength of the guilds, aiming for a kill in 5 to 10 minutes.
• Distribute the schedule: four to six invasions per day keep the event relevant without overloading the server.
• Do not overlap heavy events like Blood Castle and Chaos Castle in the same minute.
• Monitor the log in the first weeks and adjust Count, HP and Rate according to the community's response.

Launch checklist

• Backup of Data/Event/ and the MuOnline database done
• Enable=1 in the White Wizard invasion file
• Times set and adjusted to the target audience's time zone
• Minion IDs validated in Monster.txt
• Boss line (White Wizard) present and ID validated
• Total horde size compatible with the hardware
• Boss HP calibrated for a kill in 5 to 10 minutes
• Minions' drop table lean and reviewed
• Boss's exclusive bag configured with the main reward
• Start and boss-kill announcements configured with no corrupted accents
• Server clock synchronized (w32tm /resync /force)
• Successful forced test with a GM (horde + boss + drops) before the public time
• GM command to force the invasion documented for the team

With the schedule tuned, the army balanced, the boss well calibrated and the two drop tables separated, the White Wizard Invasion becomes the richest invasion event on your server — a two-phase battle that demands coordination to fight through the horde and bring down the White Wizard. Start conservative on the numbers, watch the guilds' response and refine each week, always keeping the backups up to date.

Frequently asked questions