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

Reward bag section 0: quantity, Zen and quality rolls

The outer bag configuration is applied before the weighted candidate pool. Its rate scales differ from ItemDrop.xml and MapManager.

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

The outcome to aim for

The outer bag configuration is applied before the weighted candidate pool. Its rate scales differ from ItemDrop.xml and MapManager.

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

Understand the fields

FieldMeaning & dependencies
ItemDropRateOuter item check: 0..100 percent, per attempt.
DropZenFallback Zen when the outer item check fails; 0 means no fallback Zen.
ItemDropCountNumber of attempts; this is not the number of candidate rows.
SetItemDropRateRandom set attempt out of 10000 after the outer item roll.
ItemDropType / FireworksOption-randomization mode and visual firework flag.
VISUAL WALKTHROUGH

One step at a time

  1. STEP 1

    Preserve this section-0 order: quoted EventName, DropZen, ItemDropRate, ItemDropCount, SetItemDropRate, ItemDropType, Fireworks.

  2. STEP 2

    ItemDropCount is the number of attempts. In the classic bag path, each attempt checks ItemDropRate using 0..100 percent. If that check fails, positive DropZen produces the configured Zen fallback instead.

  3. STEP 3

    After a successful outer item check, SetItemDropRate uses 0..10000 units for a random set-item attempt. 100 means 1%, not 100%. If that path does not produce a set item, the normal candidate selection follows.

  4. STEP 4

    ItemDropType is an option-randomization mode and Fireworks is presentation. Extended bag sections can select a different reward path, so inspect the complete file.

  5. STEP 5

    Apply /reload eventitembag and test quantity, Zen fallback, weighted pool and item options separately. For a deterministic training test, isolate one valid candidate in a test-only copy.

Configuration example

TUTORIAL EXAMPLE · MERGE FRAGMENT

Keep the existing root/sections and unrelated rows. This example is not a complete original or a full replacement file.

TEACHING FRAGMENT
0
//EventName       DropZen ItemDropRate ItemDropCount SetItemDropRate ItemDropType Fireworks
"Training Bag"    0       100          1             0               0            0
end

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

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

Dependencies & important details

In classic item-bag rows, Excellent is generally a requested random option count, while normal shop rows use a bitmask. The same number can therefore mean different item options in the two formats.

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.