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

Daily missions and login rewards

DailyMissions.xml contains account/day assignments, login rewards and a full-completion reward. This differs from the sequential WinQuest system.

Runtime unconfirmedEdition 2.0 · English / 简体中文
Do not assume runtime support

The file exists, but its runtime loader was not found in the inspected version. Verify support before offering the feature.

01 / WHAT YOU WILL LEARN

The outcome to aim for

DailyMissions.xml contains account/day assignments, login rewards and a full-completion reward. This differs from the sequential WinQuest system.

Success check: Test the daily rollover in a test environment; do not change the production machine clock to force it.

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

    Enable controls the system; ResetHour controls its daily reset setting. AssignmentCount chooses the number assigned and AssignmentScope identifies the scope. Keep enough distinct valid templates for the requested count.

  2. STEP 2

    Each Mission needs a unique Id and a supported Type. Target is the required progress, while reward fields describe the payout. Preserve Group rules to avoid unintended duplicate assignments.

  3. STEP 3

    DailyLogin and CompletionBonus are separate rewards. CompletionBonus Required should be attainable under the assignment policy. Delivery Mode determines where items are delivered.

  4. STEP 4

    After a planned restart or the verified reload path for this module, test with two characters of one account and another separate account. Confirm the intended account scope and one-time reward behavior.

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

Test the daily rollover in a test environment; do not change the production machine clock to force it.

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

Dependencies & important details

This file is present in the package, but no runtime loading reference was found in the inspected GameServer version. Verify support on your deployed build before offering this feature to players.

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.