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

ItemStack.txt

Stackable-item rules

4.MuServer/Sub-1/Data/Item/ItemStack.txt
Section table5 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 item

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   Level   MaStack   CreateIndex   BreakUp

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
mainStable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
mainItem/character/requirement level according to the owning entry. Use the context and valid definition range.
mainObserved parameter MaStack. 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.
mainObserved parameter CreateIndex. 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.
mainObserved parameter BreakUp. 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.

5 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.