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

BonusManager.ini

Timed bonus schedules and values

4.MuServer/Sub-1/Data/Event/BonusManager.ini
Section table24 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 event

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

Open full tutorial
Recorded column order
Index   Year   Month   Day   DoW   Hour   Minute   Second
Index   StartMessage   FinalMessage   BonusTime
Index   BonusIndex   BonusValue_AL0   BonusValue_AL1   BonusValue_AL2   BonusValue_AL3   ItemIndex   ItemLevel   MapNumber   MonsterClass   MonsterLevelMin   MonsterLevelMax

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
0Stable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
0Schedule calendar/time field. Preserve supported wildcards and confirm the event’s weekday convention.
1Stable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
1Observed parameter StartMessage. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
1Observed parameter FinalMessage. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
1Observed parameter BonusTime. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
2Stable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
2Observed parameter BonusIndex. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
2Account-tier 0 parameter for BonusValue. AL0 is normal; AL1..AL3 are elevated account tiers. Units and limits belong to this specific setting.
2Account-tier 1 parameter for BonusValue. AL0 is normal; AL1..AL3 are elevated account tiers. Units and limits belong to this specific setting.
2Account-tier 2 parameter for BonusValue. AL0 is normal; AL1..AL3 are elevated account tiers. Units and limits belong to this specific setting.
2Account-tier 3 parameter for BonusValue. AL0 is normal; AL1..AL3 are elevated account tiers. Units and limits belong to this specific setting.
2Item number or packed item identifier according to this row. Verify whether a separate category column exists.
2Item/character/requirement level according to the owning entry. Use the context and valid definition range.
2Map identifier. -1 is a wildcard only in formats that explicitly support it.
2Monster/NPC class ID. In ItemDrop.xml MonsterIndex=-1 accepts any monster class.
2Observed parameter MonsterLevelMin. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
2Observed parameter MonsterLevelMax. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.

24 fields · 1 / 1

Learn how to apply a changeOpen related lab

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.