Skip to content
MOMU EMULATOR THE SERVER OWNER’S LIBRARYNeed a hand? Get support ↗
MOMUEMULATOR
简体中文
CONFIGURATION REFERENCE

034 - Senior Mix.txt

Reward bag: Senior Mix

4.MuServer/Sub-1/Data/EventItemBag/034 - Senior Mix.txt
Section table17 recorded fieldsutf-8-sigRecorded file structure
Recorded file structure

Verify the active copy and owning role before editing. Recorded structure does not prove feature activation.

APPLICATION / RELOAD/reload eventitembag

Apply on the owning role. Startup-only settings require a restart; spawn/event reloads can reset active state.

Open full tutorial
READ-ONLY CODE VIEW

Read the structure in context

RECORDED STRUCTURE SAMPLE · NOT A FULL ORIGINAL

Only the labelled excerpt below is available. Syntax is detected from structure; .ini may actually be a section/end table. Click a highlighted documented field to open its explanation.

034 - Senior Mix.txtSection table
"Senior Mix"		 1000	   100		  1		  0		    0		   0
0           20     5          0          1       1      0        1			0			100
0           21     5          0          1       1      0        1          0			100
READ ONLY · SAMPLE
Recorded column order
EventName              DropZen   ItemDropRate   ItemDropCount   SetItemDropRate   ItemDropType   Fireworks
Section   Type   MinLevel   MaxLevel   Skill   Luck   Option   Excellent	SetOption	DropRate

Field reference

Names and observations come from the supplied files. “Not established” means the unit/range/enum is not verified. Keep a known working value until confirmed.

Section / parameterMeaning and verified limits
0Name of the reward bag/event, normally quoted when it contains spaces.
0Classic bag: Zen amount used when the outer item roll fails. Zero disables that fallback Zen amount.
0Classic bag section 0: outer item roll uses 0..100 percent. Common.ini tier keys and other files have separate interpretations.
0Classic bag section 0: number of reward attempts, each with the outer item/Zen check.
0Classic bag section 0: random set-item attempt out of 10,000 after a successful outer item roll. This differs from MapManager’s million-unit SetDrop.
0Classic bag option-randomization mode. Nonzero enables the supported random option behavior; it is not an item category.
0Classic bag firework presentation flag; does not change the reward pool.
1Item category when used as an item coordinate. Packed ID = category×512+index; some tables use Group for a different grouping.
1Local type selector. In an item row it often means category/index position; in a mission or reward row it selects behavior. Do not reuse enums from another system.
1Lower level bound. In ItemDrop.xml MonsterMinLevel limits the monster, and -1 removes the bound.
1Upper level bound. In ItemDrop.xml MonsterMaxLevel=-1 removes that bound.
1Item option field. In ItemDrop.xml the *Option attributes reference option-generation groups; do not copy literal shop masks into them.
1Item option field. In ItemDrop.xml the *Option attributes reference option-generation groups; do not copy literal shop masks into them.
1Additional item option value in this row. The encoding and maximum are file-specific; preserve a validated example.
1Excellent option encoding depends on this file: normal shop/XML item masks differ from classic item-bag option counts.
1Item option field. In ItemDrop.xml the *Option attributes reference option-generation groups; do not copy literal shop masks into them.
1Context-dependent: ItemDrop.xml uses one-million roll units; classic item-bag candidate rows use relative weight. See the drop chapters.

17 fields · 1 / 1

Learn how to apply a change

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.