How to Configure Experience, Drop Rates and Tax on Your MU Server

Understanding the Core Rate Configuration Files

Before touching any values, you need to know which files govern your server's economy. MU Online server emulators — regardless of the specific version you are running — share a common pattern: a main server settings file handles global multipliers, while secondary files handle map-specific or event-specific overrides.

The files you will interact with most frequently are:

• GameServerInfo.ini (or equivalent) — global experience and drop multipliers
• ItemDropRate.cfg (or equivalent) — per-item-type or per-monster drop chance tables
• CommonServer.cfg — Zen tax settings, trade fees, and related economy knobs

Always make a timestamped backup of each file before editing. A single misplaced decimal or an out-of-range integer can cause the server to reject the configuration entirely and fall back to defaults — or, in worse cases, crash on startup.

> [!WARNING] > Never edit live configuration files while the GameServer process is running. Write your changes, verify the syntax, then perform a clean restart. Hot-editing can produce partial reads by the server process and lead to unpredictable behavior that is difficult to diagnose.

Configuring the Experience Rate

Experience rate is a multiplier applied to the base experience awarded by each monster kill. A value of 1 means vanilla rates. A value of 100 means players earn one hundred times the base experience per kill.

Open your primary server configuration file and locate the experience block. It typically looks like this:

; ── Experience Settings ──────────────────────────────────────
ExpRate            = 100     → global experience multiplier (1 = default)
MasterExpRate      = 50      → Master Level experience multiplier
MarbleExpRate      = 30      → Majestic / 4th class experience multiplier

; ── Per-map experience overrides ─────────────────────────────
; Format: MapID → Multiplier (overrides global ExpRate for that map)
MapExpOverride_017 = 200     → Icarus (map 017) gets double the global rate
MapExpOverride_033 = 150     → Kanturu Relics boosted rate
MapExpOverride_056 = 80      → Nars reduced rate to increase difficulty

Key considerations when setting ExpRate:

• Low-rate servers (1x–10x) appeal to players who enjoy long-term progression but require a strongly committed community.
• Mid-rate servers (50x–300x) are the most common and attract the widest audience.
• High-rate servers (500x–9999x) offer quick character advancement and are popular for weekend events or test realms.

For Master Level experience (MasterExpRate), it is standard practice to set this lower than the base rate. Master Levels represent endgame content; accelerating them too much removes a long-term goal that keeps players engaged.

> [!TIP] > If you want to run seasonal events with boosted experience without permanently changing your configuration, use a scheduled script that swaps the ExpRate value before the event window and reverts it afterward. Keep both a "normal" and an "event" version of the config file and automate the swap with a task scheduler.

Configuring Item Drop Rates

Item drop rates control how often monsters drop items and which items appear. This is separate from experience and has a larger impact on the in-game economy than many administrators realize.

Drop rate configuration usually lives in a dedicated file and uses a combination of:

1. Global drop multiplier — scales all item drops up or down
2. Item-tier thresholds — separate multipliers for Normal, Excellent, Ancient, and Socket items
3. Per-monster overrides — specific monsters can have fixed drop chances regardless of the global setting

A typical drop rate block looks like this:

; ── Global Drop Settings ─────────────────────────────────────
DropRate           = 3       → multiplier applied to all item drops
JewelDropRate      = 2       → separate multiplier for Jewels of Bless, Soul, etc.
ExcellentDropRate  = 1       → Excellent item drop multiplier (keep low)
AncientDropRate    = 1       → Ancient item drop multiplier (keep very low)
SocketDropRate     = 1       → Socket item drop multiplier

; ── Zen Drop Settings ────────────────────────────────────────
ZenDropRate        = 5       → how much Zen monsters drop
ZenDropMax         = 100000  → cap on Zen dropped per kill

; ── Per-monster overrides ────────────────────────────────────
; Format: MonsterID → ItemID → DropChance (0-100000, where 100000 = 100%)
MonsterDrop_007_002 = 45000  → Budge Dragon (007) dropping Short Sword (002) at 45%
MonsterDrop_024_000 = 800    → Elite Skeleton (024) has 0.8% chance of Jewel of Bless

Jewel economy balance: Jewels of Bless, Soul, Chaos, Creation, and Life are currencies in their own right. If they drop too freely, item upgrading becomes trivial and players lose the satisfaction of achieving +13 or +15 items through effort. A JewelDropRate between 1x and 3x is a safe range for most server types.

Configuring Zen Tax and Trade Fees

The Zen tax system acts as an economic pressure valve. Without it, Zen accumulates indefinitely and eventually hyperinflates to the point where even basic repairs become comically cheap in relative terms.

Open your economy or common server configuration file and look for the tax block:

; ── Zen Tax / Economy Settings ───────────────────────────────
PersonalStoreTax   = 7       → percentage taken from personal store sales (0-100)
AuctionTax         = 10      → percentage taken from auction house transactions
RepairCostRate     = 1       → multiplier for NPC repair costs
WareHouseFee       = 30      → flat Zen fee per item stored in warehouse

; ── Trade Channel Settings ───────────────────────────────────
TradeZenTax        = 5       → percentage removed from Zen in direct player trades
TradeItemTax       = 0       → item tax (leave at 0 unless you want item sinks)

; ── Drop Zen Tax ─────────────────────────────────────────────
DropZenDecay       = 0       → Zen lost when dropped on the ground (anti-afk measure)

Recommended starting values for a mid-rate server:

• PersonalStoreTax at 7-10% discourages excessive merchant camping and removes Zen passively.
• AuctionTax at 10% is the closest analogy to a real-world transaction tax and feels natural to players.
• RepairCostRate at 1x keeps vanilla repair costs, which already serve as a mild Zen sink during regular play.
• WareHouseFee is optional. Setting a small flat fee encourages players to clean their warehouse and keeps item storage intentional rather than a dumping ground.

> [!WARNING] > Setting TradeZenTax too high (above 20%) will push player trading into unofficial channels — in-game mail, face-to-face drops, or external platforms — where you have no visibility or control. Keep trade taxes moderate to retain economic activity inside your monitored systems.

Testing and Iterating After Changes

After editing your configuration files, the process is:

1. Stop the GameServer process cleanly — avoid kill signals if your emulator supports a graceful shutdown command.
2. Validate your edited files by running the server's built-in config check tool if one is available (many emulators ship with a --check-config flag).
3. Start the GameServer and connect with a test account.
4. Use GM commands to spawn monsters and verify kill experience matches expectations.
5. Use GM item-spawn commands to test drop rates at scale — spawn 50-100 instances of a monster and record drop results.
6. Check the server log for any warnings about out-of-range values or unrecognized keys.

Document every change with a date and the reason for the adjustment. A simple changelog text file alongside your configs is invaluable when you need to roll back three weeks of incremental tweaks because a new patch changed the baseline behavior.

Rate configuration is never truly "finished." As your player base grows and the in-game economy matures, you will revisit these values repeatedly. Treat them as living settings, not one-time decisions.

Perguntas frequentes