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

Edit coin shops, extended shops and Cash Shop

These are different shop systems with different currencies and delivery paths. Identify which interface the customer uses before editing a price.

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

The outcome to aim for

These are different shop systems with different currencies and delivery paths. Identify which interface the customer uses before editing a price.

Success check: Record item count and all potentially affected currencies before and after one purchase. Never validate a shop solely from its displayed price.

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

    CustomShop.xml: Enable is the master switch. MainCategory is the top category and DanhMuc/NameShop defines submenus. Duplicate an item within the intended submenu and change Type/Index, item options and GiaCoin.

  2. STEP 2

    Keep PriceType from a working item using the intended currency; enum numbers are not universal across systems. Verify the displayed label and actual deducted balance.

  3. STEP 3

    ExtendShop.xml: Enable controls availability; Count is created quantity and Price is WCoinC according to its supplied file. Read Sale and RateExchange handling before changing those fields.

  4. STEP 4

    Standard Cash Shop requires Common.ini CashShopSwitch and matching CashShopPackage/CashShopProduct entries. Keep package and product identifiers linked; server data and client shop data may both need updating.

  5. STEP 5

    Apply /reload spk for MOMU XML shops, /reload cashshop for standard Cash Shop. Test correct balance, insufficient balance, full inventory/storage, item duration and relog persistence.

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

Record item count and all potentially affected currencies before and after one purchase. Never validate a shop solely from its displayed price.

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.