How to configure the Loren Deep (Ferea) event in MU Online

Loren Deep is one of the most sought-after endgame content maps in modern MU Online seasons, and it serves as the stage for the Ferea event, whose climax is the confrontation against the Lord of Ferea. Unlike classic events such as Blood Castle or Devil Square, Ferea combines a dedicated map with its own access rules, high-density spawns and a reward table tied directly to the boss. Configuring it correctly requires touching three server layers at once: the GameServer's map and monster definition files, the event INI that controls schedules and parameters, and the drop and gate tables in the database. This guide walks through each of those layers in detail, always noting where file names and parameters tend to vary by emulator, so you can adapt the script to your base without depending on a single build. By the end, you will have the map accessible, the monsters spawning, the boss dropping correctly and a launch checklist to validate everything before opening it to players.

Prerequisites

Before editing any file, confirm that your environment meets the minimum conditions. The Ferea event depends on features that only exist in more recent builds, and trying to enable it on an old emulator usually results in a GameServer crash when loading the map.

• A modern-season server with native support for the Loren Deep map (the map index and the corresponding .att/.map must exist in both client and server data).
• GameServer, ConnectServer, DataServer (or JoinServer) and, where applicable, EventServer installed and functional.
• The MuOnline database accessible via SQL Server Management Studio (SSMS) with write permission.
• A client (Main) with the Loren Deep map files already present in Data\ — without them the player gets a black screen or is disconnected on entry.
• A full backup of the database and of the GameServer\Data\ folders and the event INI before any change.

> Note: the paths cited here (GameServer\Data\, EventServer\) are common examples. The exact name of the folders and executables varies by emulator — adapt it to your installation's structure.

How Ferea works on the server

Understanding the internal flow saves hours of trial and error. When the scheduled time arrives (or when a player uses the access portal), the server unlocks entry to the Loren Deep MapNumber. The map's monsters are governed by two files: the MonsterSetBase (where each line defines which monster spawns, at which coordinate and facing which direction) and the Monster file (which defines attributes such as HP, attack, defense and level for each MonsterIndex). The Lord of Ferea boss is just another MonsterIndex, but with much higher HP and a dedicated drop table, usually called EventItemBag or similar. The event's rewards — which typically include upgrade items, jewels and season-specific materials — do not come from the map's common drop table, but from that bag linked to the boss. That is why configuring Ferea is essentially chaining together correctly: gate → map → spawns → boss → reward bag.

Step 1: Unlock the Loren Deep map on the server

The first step is to ensure the GameServer recognizes and loads the map. In many emulators there is a configuration file that lists the active maps, something like MapServerInfo.txt or a maps section in GameServerInfo. Locate the Loren Deep entry (identified by its MapNumber) and confirm it is enabled.

; Illustrative example — the file name and syntax vary by emulator
; MapNumber / Name / Enabled / PKFree / MoveEnable
79   "Loren Deep"   1   0   1

If the map is not in the list, add it using your season's correct MapNumber. A wrong map index is the number one cause of crashes: the GameServer tries to open a nonexistent .att and shuts down. Confirm the index in your emulator's documentation before proceeding.

Step 2: Configure the Ferea event INI

The event's behavior — whether it is on, how many players it requires, how long it lasts and at what times it starts — lives in an event INI file. Depending on the emulator, it may sit in GameServer\Data\ or in an EventServer folder. Open it with an editor that preserves the encoding (Notepad++ saving in ANSI is a safe choice).

[Ferea]
FereaEnable=1
FereaUserMin=0
FereaDuration=45
FereaEntranceLevel=400
FereaSchedule=01:00,09:00,17:00,23:00
FereaMaxUser=15
FereaBossRespawn=1

> The exact key names (FereaEnable, FereaSchedule, etc.) are illustrative and vary by emulator. Some builds use a central scheduler (for example EventTimer or EventSchedule) instead of times inside the event INI itself. Consult your build's reference INI.

Step 3: Define the monster spawns in MonsterSetBase

With the map active and the INI ready, it is time to populate Loren Deep. Open GameServer\Data\MonsterSetBase.txt (or the equivalent file) and locate — or create — the block for the Loren Deep MapNumber. Each line represents a monster that will spawn on the map.

// Loren Deep - Map 79
// MapNumber / MonsterIndex / X1 / Y1 / X2 / Y2 / Dir / Count
79   681   120   050   180   110   0   40   // common Ferea creatures
79   682   130   060   190   120   0   30   // stronger variant
79   683   140   070   170   100   0   15   // elite
79   690   160   090   160   090   0   1    // Lord of Ferea (boss)

When the coordinate fields appear in pairs (X1/Y1 and X2/Y2), the server distributes the monsters randomly within that rectangle — useful for mob density. The boss, on the other hand, gets a fixed coordinate (X1=X2, Y1=Y2) and Count=1. Check the map's boundaries in MapInfo before setting coordinates: positions outside the valid area cause a spawn at position zero or a crash.

Step 4: Adjust attributes and the boss in the Monster file

Defining where the monsters spawn is not enough; each MonsterIndex must exist with coherent attributes in the Monster.txt file (name varies). The Lord of Ferea, as an endgame boss, needs HP high enough to sustain a fight of several minutes, but not so high that it becomes impossible for your server's target audience.

// MonsterIndex / Name / Level / HP / MinDmg / MaxDmg / Defense / MagicDef ...
690  "Lord of Ferea"  140  25000000  2200  3200  1500  900

Adjust the HP in proportion to your server's rates. On a high-rate server with lots of damage, a boss with too little HP dies in seconds and the event loses its appeal; on low rates, excessive HP drags the fight beyond the event's duration and the boss "expires" without being defeated. A good starting point is to calibrate it so a mid-level group takes between 40% and 70% of the FereaDuration to win.

Step 5: Configure the rewards (the boss's EventItemBag)

This is the heart of the event. Ferea's rewards come from a dedicated drop table, usually files of the EventItemBag type (for example ItemBag_Ferea.txt), linked to the boss's MonsterIndex. This structure lets you list items, percentage chances and quantity ranges independently of the common drop.

// Item / Section / Index / Level / Durability / Chance(%)
// Illustrative example of a Lord of Ferea bag
14  13   0   0   1   30.0   // Jewel of Bless
14  14   0   0   1   30.0   // Jewel of Soul
14  22   0   0   1   15.0   // Jewel of Life
12  15   0   0   1   3.0    // wing / rare season item

Confirm, in the INI or the monster configuration, that the boss points to the correct bag file. In many emulators there is an ItemBag field or a mapping in MonsterItemBag that associates the MonsterIndex with the bag. Without that link, the boss dies and drops nothing — one of the most reported problems in Ferea configuration.

Step 6: Configure the access gate/portal

If your server requires players to use a portal to enter Loren Deep (instead of just moving by command), the gate needs to be enabled in the database.

-- Check the Loren Deep gate (number varies by emulator)
SELECT Number, GateType, Map, X, Y, TargetGate, Level, Enable
FROM MuOnline..Gate
WHERE Map = 79;

-- Enable the gate if needed
UPDATE MuOnline..Gate
SET Enable = 1
WHERE Map = 79;

Some builds still control entry via an access item (a consumable "ticket"). In that case, make sure the item exists in the item table and that the consumption logic is enabled in the event INI.

Step 7: Startup sequence and testing

With everything configured, restart the server in the correct order so each component finds its dependencies ready:

1. Start the DataServer (or JoinServer) and wait for the ready status.
2. Start the ConnectServer and confirm it is listening.
3. Start the GameServer and watch the console — it should load map 79 and the MonsterSetBase without errors.
4. If there is an EventServer, start it last.
5. Log in with a GM account, use the move command to Loren Deep and visually confirm the spawns.
6. Force a nearby time in FereaSchedule, restart the event service and watch the boss spawn.

> Always test during a low-traffic time. A poorly calibrated spawn (count too high) can generate hundreds of monsters and take down the GameServer from CPU consumption.

Common errors and fixes

Launch checklist

• Backup of the MuOnline database and the data folders completed
• Loren Deep MapNumber enabled in the server's map list
• Map files present on both the server and the client
• Ferea INI with Enable=1, valid duration and schedules
• Spawns defined in MonsterSetBase with coordinates within the boundaries
• Lord of Ferea MonsterIndex present in the Monster file with calibrated HP
• Boss EventItemBag created and linked to the MonsterIndex
• Access gate with Enable=1 (or access item configured)
• Test with a GM account confirming spawns, boss and drop
• Schedules adjusted to the time zone and the server's peak audience
• GameServer logs free of map or monster loading errors

Once you validate every item on the checklist, the Ferea event will be ready to enter your server's rotation. If you are still building the base from scratch, it is worth reviewing the guide on how to create a MU Online server to ensure the main components are correctly installed before adding endgame content like Loren Deep. With the map unlocked, the spawns calibrated and the Lord of Ferea bag working, Ferea starts offering high-level players a recurring, rewarding objective, helping keep the server active well beyond the classic content.

Frequently asked questions