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

Tune EXP, level caps and starting characters

Normal level, Master level, EXP gain and starting stats are separate controls. Account-tier values can make the same monster award different EXP to different accounts.

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

The outcome to aim for

Normal level, Master level, EXP gain and starting stats are separate controls. Account-tier values can make the same monster award different EXP to different accounts.

Success check: Test level gain at the beginning, around 400 and near the configured maximum; relog to verify EXP is saved without truncation.

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

    Use AddExperienceRate_AL0..AL3 for normal account-tier EXP and AddMasterExperienceRate_AL0..AL3 for Master EXP. MapManager ExpRate and party/event bonuses can add further scaling.

  2. STEP 2

    NormalMaxLevel is the normal-level cap. MasterSkillTreeMaxLevel is a separate cap. Above-classic normal levels require matching client, GS, GSCS and DataServer plus the supported 64-bit Experience database column.

  3. STEP 3

    DefaultClassInfo defines new-character starting values. CustomStartItem defines starter items and is resolved through the MOMU/Custom fallback rules. These edits do not automatically reset existing characters.

  4. STEP 4

    Create one new character of each supported class and test starting attributes, learned skills, equipment, inventory and the first level gain.

  5. STEP 5

    Before changing an EXP table or database type, back up the database and compare values near each cap. Use the supplied migration only after confirming it applies to your deployed schema.

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 level gain at the beginning, around 400 and near the configured maximum; relog to verify EXP is saved without truncation.

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.