How to configure the Golden Invasion in MU Online

The Golden Invasion is one of the most traditional invasion events in MU Online and one of the first that any administrator learns to master. The idea is simple and effective: at predefined times, golden creatures — the Golden Monsters — appear simultaneously across several server maps, showing a characteristic glow, HP far above normal and a generous drop table that includes Box of Kundun and jewels such as Jewel of Bless, Soul and Life. The result is predictable: channels fill up, guilds organize to "farm" the golden ones and the server economy gains a regular pulse of items. This guide shows how to configure the Golden Invasion from scratch, tune schedules, control spawns and rewards, and solve the most common problems. The file and key names here serve as examples — the exact naming varies by emulator (IGCN, MuEMU, X-Files, classic Season 6, etc.), but the logic is the same in all of them.

If you do not yet have a running server, start with the base tutorial on how to create a MU Online server and come back here once you have a working GameServer and MuOnline database.

Prerequisites

Before touching any file, confirm that the environment meets these points:

• A functional GameServer of any Season that includes the invasion event (the Golden Invasion has existed since old Season 3/4 builds and has remained in modern Seasons).
• The MuOnline database accessible via SQL Server Management Studio (SSMS) or equivalent.
• Administrative access to the server directories, especially GameServer/Data/.
• A suitable text editor — use Notepad++ and always save in the encoding your build expects (usually ANSI; some modern emulators use UTF-8). The wrong encoding corrupts accents and breaks the server parser.
• A full backup of the Data/ directories and the database before any change.

> Tip: reserve an off-peak test slot to force the event without affecting real players. You will restart the GameServer a few times during calibration.

How the Golden Invasion works internally

The Golden Invasion is controlled by the GameServer, not by a dedicated EventServer like Crywolf. In almost every emulator, there is an invasion configuration file (for example GameServer/Data/Event/Invasion.txt, GoldenInvasion.txt or a section inside GameServerInfo / EventInvasion) that defines three things:

1. When the event fires (a list of times or an interval in minutes).
2. What appears (which monster IDs, how many per spawn).
3. Where it appears (map and coordinate range).

When the server clock hits the scheduled time, the GameServer sends a golden announcement to all channels ("Golden Invasion has started!") and instances the monsters at the defined positions. On death, each golden one consults its drop table to decide what to release. Understanding this separation — schedule, population and drop — is what makes the configuration predictable.

Step 1: Locate the invasion file

Open the GameServer/Data/ directory and look for the event files. Typical structures (varies by emulator):

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

If your build uses a single Invasion.txt with several numbered invasions, the Golden is usually invasion index 0 or 1. Make a safety copy of the file before editing:

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

Step 2: Define the event schedule

Inside the invasion file, locate the schedule key. A generic example:

[GoldenInvasion]
Enable = 1
; Duration of each invasion in minutes
Duration = 30
; Start times (24h HH:MM format), separated by commas
Schedule = 00:00,04:00,08:00,12:00,16:00,20:00
; Global announcement on start
Notice = 1
NoticeText = "O Golden Invasion comecou! Cacem os monstros dourados!"

Some emulators do not use fixed times but a cyclic interval:

; Interval alternative: fires every 120 minutes after boot
IntervalMinutes = 120
FirstRunAfterBootMinutes = 30

The interval is simpler, but fixed times are better for communicating to players ("Golden every 4 hours on the dot"). Choose one of the two models depending on your build's support.

> Note: the GameServer uses the operating system's time. If the server is in UTC and your audience is in Brazil (UTC-3), add 3 hours to the desired times. Check with tzutil /g in CMD and sync the clock with w32tm /resync /force.

Step 3: Configure which Golden Monsters appear

Here is the heart of the event. You define the list of IDs, the map and the quantity. An example block:

; Format: MapNumber MonsterID Count Dispersion
; MapNumber: 0=Lorencia, 3=Noria, 2=Devias, 7=Atlans, 8=Tarkan, 33=Aida
0   43   3   1   ; Golden Budge Dragon in Lorencia
2   78   2   1   ; Golden Goblin in Devias
3   53   2   1   ; Golden Titan in Noria
7   45   1   1   ; Golden Vepar in Atlans
8   65   1   1   ; Golden Lizard King in Tarkan

The IDs above are examples — the real numbering of the Golden Monsters varies by emulator. Always confirm it in your build's Monster.txt (or MonsterList) before applying. The table below summarizes the classic golden ones and where they usually appear:

Step 4: Adjust the golden ones' HP and level

What sets a Golden Monster apart from the common monster of the same name is the inflated HP and, sometimes, a higher level. This normally lives in Monster.txt:

; ID  Name                 Level  HP     MinDmg MaxDmg Def
43   "Golden Budge Dragon" 88     35000  180    210    120
78   "Golden Goblin"       50     18000   90    120     60

Raising the HP makes the hunt more cooperative (a single player cannot take one down alone), but overdoing it frustrates servers with low population. Calibrate the HP to your players' average damage.

Step 5: Configure the drops (Box of Kundun and jewels)

The drop can be tied to the monster itself (via ItemDrop / MonsterItemBag) or to the event configuration. In many emulators, each Golden drops a Box of Kundun of a proportional level, and the Box, in turn, has its own table. Example of a drop bag definition:

; Golden Vepar (ID 45) -> guaranteed Box of Kundun +3 + jewel chance
DropGroup = GoldenVepar
Item = BoxOfKundun3   Rate = 10000   ; 100% (base 10000)
Item = JewelOfBless   Rate = 3000    ; 30%
Item = JewelOfSoul    Rate = 3000    ; 30%
Item = JewelOfLife    Rate = 1500    ; 15%

For more generous servers, increase the jewels' Rate; for servers focused on slow progression, reduce it. Always test the numbers with a GM before releasing to the public — a poorly calibrated drop destroys the economy in a week.

Step 6: Enable the global announcement

A good Golden Invasion is announced. If your build supports golden messages (GoldNotice), configure the text:

NoticeType = 2          ; 0=chat, 1=blue, 2=blinking golden
NoticeRepeat = 3        ; repeat the announcement 3 times
NoticeText = "Os Golden Monsters invadiram Lorencia, Devias e Atlans!"

Step 7: Restart and test

1. Save all files in the correct encoding.
2. Restart the GameServer (invasions are loaded at boot).
3. Watch the console/log: look for lines like [Invasion] GoldenInvasion loaded and [Invasion] Next Golden: 04:00:00.
4. Force a test by temporarily setting Schedule to 1-2 minutes ahead of the current time and restarting.
5. Log in with a character and confirm the announcement, the spawn across maps and the drop on kill.

Many emulators expose a GM command to force the invasion manually, for example /goldeninvasion or /invasion 0. Check your build's command list.

Common errors and fixes

Balancing best practices

• Spread the maps: scattering golden ones across Lorencia, Devias, Atlans and Aida avoids crowding and reduces the chance of widespread kill-stealing.
• Scale by level: golden ones in early maps drop Box +1/+2 (for newcomers), while those in Tarkan/Aida drop Box +4/+5 (for veterans). This keeps the event relevant for the entire base.
• Do not overlap heavy events: avoid starting the Golden exactly alongside Blood Castle or Chaos Castle so as not to overload CPU and network.
• Monitor the log during the first weeks to confirm that schedules and drops behave as expected.

Launch checklist

• Backup of the Data/Event/ files and the MuOnline database completed
• Enable=1 in the Golden invasion file
• Times defined and adjusted to the target audience's time zone
• Golden Monster IDs validated in Monster.txt
• Spawn count compatible with the hardware
• Golden ones' HP calibrated to the players' average damage
• Drop tables (Box of Kundun and jewels) reviewed and tested
• Global announcement configured and free of corrupted accents
• Server clock synchronized (w32tm /resync /force)
• Forced test successful with a GM before the public time
• GM command to force the invasion documented for the team

With these three pillars aligned — schedule, population and drop — the Golden Invasion becomes one of the most reliable and beloved events on your server, capable of gathering the community at fixed times and injecting items into the economy without requiring manual intervention. Adjust the numbers gradually, watch how players behave and keep your backups up to date.

Frequently asked questions