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

Items, prices, stacking, sets and sockets

Identify an item with its section and index. Packed ID = section×512+index, but some fields use option groups, bank slots or other local indexes instead.

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

The outcome to aim for

Identify an item with its section and index. Packed ID = section×512+index, but some fields use option groups, bank slots or other local indexes instead.

Success check: Test equip/unequip, damage/defense, wrong class, insufficient requirements, trade, storage and reconnect.

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

    Inspect Item.txt headers for that section and the associated Item.xml or Season20 definition files before changing stats, requirements or class permissions. Determine which definition your loader actually uses.

  2. STEP 2

    Prices belong in ItemValue or the chosen custom shop’s own price field. ItemValueTrade is a separate trading valuation table; avoid assuming a price change affects every shop system.

  3. STEP 3

    ItemStack controls eligible stacking rules. Test merging, splitting, overflow and relog with disposable items; changing a maximum does not automatically convert every existing stack.

  4. STEP 4

    SetItemType connects items to ancient sets and SetItemOption defines their bonuses. SocketItemType lists eligible equipment; SocketItemOption defines effects. Keep registration and effect tables aligned.

  5. STEP 5

    Use /reload item for the loaded item definitions and /reload shop when ItemValue changes. Client item names, models and tooltip data need matching client updates and a restart.

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 equip/unequip, damage/defense, wrong class, insufficient requirements, trade, storage and reconnect.

If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another 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.