Skip to content
MOMU EMULATOR THE SERVER OWNER’S LIBRARYNeed a hand? Get support ↗
MOMUEMULATOR
简体中文
PRACTICAL TUTORIAL / 284 min read · Advanced

Create and edit quests without breaking progress

This package has several quest systems. Classic class quests, QuestWorld, WinQuest and CustomNpcQuest use different IDs and layouts. Choose the system shown to the player.

Recorded procedureEdition 2.0 · English / 简体中文
01 / WHAT YOU WILL LEARN

The outcome to aim for

This package has several quest systems. Classic class quests, QuestWorld, WinQuest and CustomNpcQuest use different IDs and layouts. Choose the system shown to the player.

Success check: Apply the group that loads the chosen system: /reload quest for classic tables, /reload custom for custom tables and /reload spk for WinQuest.

Before you start

Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.

ScopeTeaching examples and recorded structures. Application and gameplay must be verified on your deployed version.

Files you need

VISUAL WALKTHROUGH

One step at a time

  1. STEP 1

    Classic quests link Quest.txt, QuestObjective.txt and QuestReward.txt. Preserve their quest IDs and stage order, including prerequisite quests and class checks.

  2. STEP 2

    WinQuest: CreationQuestSystem.xml controls its NPC and Presentation/Quest text; CreationQuestData_1.ini controls gameplay. Presentation Index is zero-based and must match the corresponding gameplay quest.

  3. STEP 3

    Each WinQuest keeps five mission rows and four reward rows. Mission type 1 hunts monsters, 2 collects items, 3 counts resets and 4 counts master resets. Use the supplied quest guide for the row layout.

  4. STEP 4

    Collection MissionID is Type×512+Index; MissionLevel=255 accepts any item level. For hunts, MissionID=65535 accepts any monster and MissionLevel=-1 accepts any map. These wildcards are specific to this format.

  5. STEP 5

    Test accept, reject, kill credit, item consumption at claim, party behavior, reward delivery and relog. Avoid renumbering quests already held by live characters.

Apply the real change

Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.

Find the file’s reload instructions →

Verify the result in game

Apply the group that loads the chosen system: /reload quest for classic tables, /reload custom for custom tables and /reload spk for WinQuest.

If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.

Dependencies & important details

Keep the fixed mission/reward row counts. In the supplied WinQuest layout: reward type 1=Zen, 2=level-up points, 3=item, 4=WCoinC. Do not reuse these numbers for another reward system.

Built around the supplied MOMU configuration snapshot. Reference entries flag alternate copies and unconfirmed fields. Match the guide to your deployed version; archived packages and live gameplay were not audited by publishing these pages.