Troubleshoot by symptom
Start with the first failure and the exact role. Changing many settings at once usually hides the cause.
The outcome to aim for
Start with the first failure and the exact role. Changing many settings at once usually hides the cause.
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.
Files you need
This chapter is an operating procedure. Its steps identify when to use the related task and file references.
One step at a time
- STEP 1
Edit has no effect: confirm the running executable, correct Data location, MOMU-versus-Custom precedence, active profile and whether a restart is required.
- STEP 2
Server reports a parse error: check the named file, last edited line, column count, end markers, XML quotes/closing tags and encoding. Restore the last working file if necessary.
- STEP 3
NPC absent or wrong window: verify map ownership, the NPC XML placement, loaded monster class and competing quest/custom NPC handlers.
- STEP 4
Shop empty: verify the ShopManager index, exact filename prefix, item definitions and item grid capacity, then close and reopen the interface.
- STEP 5
Drop too high or too low: separate map multiplier, million-unit quality rolls, ItemDrop map scaling, overlapping rules, account tiers, bag weights and event penalties.
- STEP 6
Spot absent: confirm XML map filename, SPOT placement, valid class, valid rectangle, walkable terrain, allowed profile and owning role; reload in maintenance.
- STEP 7
Teleport fails: trace Move row → Gate ID → arrival map/rectangle → map ownership → active server → matching client resources.
- STEP 8
Reward missing: check trigger mapping, reward type, target storage, eligibility, full inventory/storage, account claim history and DataServer errors.
- STEP 9
Chinese text corrupt: distinguish editor encoding, TSV/XML syntax, client font/resource support, SQL data type/collation and the selected language.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
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
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.