How to Enable the 4th Quest on MU Online Server

The 4th Quest is one of the most significant milestones in MU Online Season 6 character progression. It represents the second class change — turning a Blade Knight into a Blade Master, for instance — and unlocks new skills, attribute bonuses, and access to the Master Level system. From the server administrator's perspective, properly enabling this quest requires careful attention to multiple configuration files, database tables, and per-class conditions.

This guide covers the full technical process for enabling the 4th Quest on a Season 6 server, using only standard configuration methods — no paid third-party tools, no commercial services.

Understanding the 4th Quest and Its Role in S6 Progression

Each character in S6 follows a defined evolution path through class changes:

Dark Knight    → (3rd Quest) → Blade Knight    → (4th Quest) → Blade Master
Dark Wizard    → (3rd Quest) → Soul Master     → (4th Quest) → Grand Master
Fairy Elf      → (3rd Quest) → Muse Elf        → (4th Quest) → High Elf
Summoner       → (3rd Quest) → Bloody Summoner → (4th Quest) → Dimension Master
Dark Lord      → (no std 3rd Quest) →           (4th Quest)  → Lord Emperor
Magic Gladiator → evolves via Master Level to Duel Master (no class quests)

For the 4th Quest, each eligible character must meet the following conditions on the server side:

1. Already completed the 3rd Quest (first class change into the intermediate form).
2. Reached the minimum level defined in the server configuration (commonly 380+ depending on server rates).
3. Have the correct Wing Level 2 item in inventory to submit as proof of progression.
4. Complete a kill task — eliminating a set number of specific monsters, typically found in high-level maps such as Land of Trials, Raklion, Acheron, or Kanturu.

Locating and Checking Core Configuration Files

Before making any edits, identify the files that control the quest system. In S6 servers based on text/ini configuration (common among private server setups), the key files are:

/GameServer/Data/Quest/QuestInfo.txt
/GameServer/Data/Quest/QuestReward.txt
/GameServer/Config/GameServerInfo.ini
/DataBase/MuOnline/dbo.Quest  (SQL table)

In GameServerInfo.ini, look for the 4th Quest control keys:

; Enable the 4th Quest system
Enable4thQuest = 1

; Minimum level to start the 4th Quest
4thQuestMinLevel = 380

; Require Wing L2 sacrifice item
Require4thQuestItem = 1

; Monster kill count required to complete
4thQuestKillCount = 100

If Enable4thQuest or Require4thQuestItem are absent entirely, your server build may not support the 4th Quest natively through INI — in that case you will need to configure it directly via QuestInfo.txt entries.

Setting Up QuestInfo.txt Per Class

The QuestInfo.txt file holds one entry per quest, with fields separated by tab or comma depending on the server version. The standard format is:

QuestID | ClassID | MinLevel | KillMonsterID | KillCount | RewardType | RewardID

The default QuestIDs reserved for the 4th Quest in S6 are:

; 4th Quest - Dark Knight (evolves to Blade Master)
QuestID=10 | ClassID=1 | MinLevel=380 | KillMonsterID=459 | KillCount=100 | RewardType=2

; 4th Quest - Dark Wizard (evolves to Grand Master)
QuestID=11 | ClassID=5 | MinLevel=380 | KillMonsterID=459 | KillCount=100 | RewardType=2

; 4th Quest - Fairy Elf (evolves to High Elf)
QuestID=12 | ClassID=9 | MinLevel=380 | KillMonsterID=459 | KillCount=100 | RewardType=2

; 4th Quest - Summoner (evolves to Dimension Master)
QuestID=13 | ClassID=24 | MinLevel=380 | KillMonsterID=459 | KillCount=100 | RewardType=2

; 4th Quest - Dark Lord (evolves to Lord Emperor)
; Note: Dark Lord uses the CMD (Command) stat in addition to STR/AGI/VIT/ENE
QuestID=14 | ClassID=16 | MinLevel=380 | KillMonsterID=459 | KillCount=100 | RewardType=2

Configuring the Wing L2 Item Submission

The item submission step is the most strategically important part of the 4th Quest. The server validates that the player carries the Wing Level 2 correct for their class before accepting quest completion. The Wing L2 items per class are:

; Wing L2 items required per class
; Dark Knight      → Wing of Dragon   (ItemID=30)
; Dark Wizard      → Wing of Soul     (ItemID=31)
; Fairy Elf        → Wing of Spirit   (ItemID=39)
; Dark Lord        → Cape of Lord     (ItemID=40)
; Summoner         → Wing of Despair  (ItemID=43)
; Magic Gladiator  → NO QUEST (no Wing L1 or L2 quest in S6)

In QuestReward.txt, verify that each 4th Quest QuestID points to the correct item as a requirement (not a reward). The item requirement fields should look like:

; Format: QuestID | RequiredItemID | RequiredItemLevel | RemoveItemOnComplete
10 | 30 | 0 | 1   ; BK submits Wing of Dragon, item consumed on completion
11 | 31 | 0 | 1   ; SM submits Wing of Soul
12 | 39 | 0 | 1   ; ME submits Wing of Spirit
13 | 43 | 0 | 1   ; BS submits Wing of Despair
14 | 40 | 0 | 1   ; DL submits Cape of Lord

Database Side: Quest Status Table

In SQL Server, the MuOnline.dbo.Quest table (or the equivalent in your specific build) stores each character's quest state. To diagnose issues or reset the 4th Quest for a specific character:

-- Check a character's 4th Quest status
SELECT Name, QuestID, QuestState, QuestProgress
FROM MuOnline.dbo.Quest
WHERE Name = 'CharacterName' AND QuestID IN (10, 11, 12, 13, 14);

-- Reset a stuck 4th Quest entry
UPDATE MuOnline.dbo.Quest
SET QuestState = 0, QuestProgress = 0
WHERE Name = 'CharacterName' AND QuestID = 10; -- Replace QuestID as needed

-- Force completion (admin/testing only)
UPDATE MuOnline.dbo.Quest
SET QuestState = 2, QuestProgress = 100
WHERE Name = 'CharacterName' AND QuestID = 10;

Testing the Configuration

After editing all files, restart the GameServer and run the following tests:

1. Eligibility test: Create a test character at the required level (use GM commands to set level and experience). Verify that the quest NPC shows the 4th Quest as available.

1. Item validation test: Attempt to complete the quest without the correct Wing L2 — the server must refuse. Then add the correct Wing L2 via GM command and attempt again; it should succeed.

1. Kill counter test: Temporarily set 4thQuestKillCount = 1 for testing. Verify that killing the configured monster increments the counter in the player's quest interface.

1. Class change test: After meeting all requirements, confirm the character changes to the correct class (e.g., Blade Knight → Blade Master) and that Master Level attribute points become available.

Special Class Notes: Dark Lord and Magic Gladiator

The Dark Lord possesses the unique CMD (Command) attribute, which determines how many creatures he can summon and command. Upon completing the 4th Quest and becoming Lord Emperor, the CMD multiplier increases — ensure your server's character class info file (CharacterClassInfo.txt or equivalent) correctly reflects the updated CMD scaling for class ID 16 (Lord Emperor), separate from the standard STR, AGI, VIT, and ENE stats.

The Magic Gladiator has no 1st, 2nd, or 4th Quest in S6. His evolution to Duel Master is handled entirely by the Master Level system. There is also no Wing Level 1 for the MG — this is a design decision carried through from the original S6 release. Do not attempt to create a quest entry for the MG; doing so will result in undefined server behavior and potential crashes.

With all these configurations in place and properly tested, your S6 server will deliver the authentic MU Online Season 6 class progression experience, giving players a meaningful and mechanically correct path from their second class all the way to the pinnacle Master-tier forms.

Perguntas frequentes