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

Select map profiles, edit moves and fix teleports

603 is the classic map profile; 621 adds the supplied modern map preview. The selector is cached at startup. A new Move row alone cannot create map terrain or transfer ownership.

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

The outcome to aim for

603 is the classic map profile; 621 adds the supplied modern map preview. The selector is cached at startup. A new Move row alone cannot create map terrain or transfer ownership.

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

1Move destination
2Gate ID
3Map + ownership
4Client resources
VISUAL WALKTHROUGH

One step at a time

  1. STEP 1

    Read Move/Profile.txt in each role to identify the selected profile. Under that profile, Move.txt selects a destination gate and its entry requirements; Gate.txt defines arrival map and rectangle.

  2. STEP 2

    Before adding a destination, confirm its terrain exists, the profile allows it, MapServerInfo assigns it to a running server and the client contains matching world resources.

  3. STEP 3

    Copy a valid Move and Gate row and use unique IDs. Preserve class-specific entry columns, gate direction and all section boundaries. Do not reuse a gate ID for an unrelated destination.

  4. STEP 4

    For ordinary Move/Gate edits use /reload move, then test outbound travel, arrival terrain, return travel and reconnect. Changing Profile.txt requires both affected servers to restart.

  5. STEP 5

    For a coordinated profile switch, follow Tool/GetMain/MOVE_PROFILE_SETUP.txt with your own GetEngine.ini and ServerFolder. GetMainInfo exports PREMIUM/ServerData.bmd beside the tool; install it into the actual client Data/Local/MOMU.

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.

Dependencies & important details

MapManager directly under Data remains global. Profile 621 is a compatibility preview, not proof that every original modern event or mining system is implemented.

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.