How to configure +jewel rates (Bless, Soul, Life) in MU Online

Correctly configuring the success rates of the Jewels — Bless, Soul and Life — is one of the most important balancing decisions when launching a MU Online server. These three jewels directly control the players' power progression: they are what turn a plain +0 item into a +13 piece of equipment with a +28 additional option, the kind of gear that decides Guild wars and dominates the ranking. If you set them too high, the economy inflates within days and everyone is "full +15" without effort, killing the sense of achievement. If you set them too low, players spend thousands of jewels without getting past +9, grow frustrated and abandon the server. This tutorial explains how each jewel really works, shows how to scale the chances by level, how to enable item protection and how to think about the economic impact of every adjustment.

Throughout the text I cover concepts that exist in practically every version of the game (Season 6 onward) and use numeric values only as an example — the exact names of files, columns and configuration keys vary by emulator (IGCN, MuEmu, Zhyper, Xteam and their derivatives). Always validate against the documentation for your build before applying anything in production.

Prerequisites

Before touching the rates, make sure your environment is ready and that you understand the basic server ecosystem. If you have not built the initial structure yet, start with the general guide on how to create a MU Online server and then come back to this specific balancing step.

• A working server with GameServer, ConnectServer and DataServer starting without errors.
• Access to the database (MSSQL) and to the emulator's configuration folders.
• A text editor capable of handling .ini, .txt or .dat files (Notepad++ recommended).
• A test environment (local or staging server) separate from production.
• A full backup of the configuration files and the database before any change.
• Basic knowledge of how to restart only the GameServer to apply changes.

Never test new rates directly on the server where players are logged in. Every chance change should go through a staging environment with a GM account creating test items.

How each Jewel works

Understanding the role of each jewel is what separates an admin who copies values off the internet from one who actually balances the server.

• Jewel of Bless (JOB): raises the item level from +0 up to +6. In the classic mechanic it carries no risk — each Bless used increases the item by +1 in a guaranteed way (in many versions the chance is 100% up to +6). It is the "warm-up" jewel of the progression.
• Jewel of Soul (JOS): responsible for taking the item from +7 up to +9. This is where risk comes in: each attempt has a success chance and a failure chance. On failure, depending on the configuration, the item may drop one level or fall back to +0. It is the main jewel "sink" (drain) of the economy.
• Jewel of Life (JOL): does not touch the +item level. It adds or increases the additional option of the equipment (that extra +4/+8/.../+28 of damage or defense). On failure the value simply does not go up; there is no risk of destroying or downgrading the item.

It is worth remembering the practical distinction: Bless and Soul control the "+" that appears before the item name, while Life controls the "additional option" line. An item can be +9+28, meaning +9 level (Bless/Soul) and +28 additional option (Life). They are independent power axes.

Success chances by level

The golden rule is to scale the difficulty: each higher level should be harder than the previous one. This creates a healthy progression curve, in which reaching +13/+15 is a milestone of dedication and not a walk in the park. Below is an example table for a medium-difficulty server (the real numbers depend on your emulator and your rate philosophy):

Note that levels +10 and up usually use combination mechanics in the Chaos Machine (Jewel of Chaos + Bless + Soul), rather than simply applying a single jewel to the item. This varies quite a bit by emulator: some builds handle +10 to +15 entirely through the Chaos Machine with their own formulas, while others extend the Soul logic. Confirm which model your version uses before setting the numbers.

Where to configure the rates

The exact locations vary by emulator, but the most common configuration points are:

• Item rate file (e.g. ItemOptionRate, IGC_ItemLevelUp, or a database table): defines the chance per +item level.
• Chaos Machine configuration (e.g. ChaosMix / CustomJewelMix): controls the +10 to +15 combinations and their chances.
• Additional option configuration (Jewel of Life): defines how much it raises (+4 per success is the classic) and the success chance.
• General GameServer file (GameServerInfo.dat or similar): sometimes contains global protection flags and multipliers.

An illustrative snippet of what a configuration entry might look like (a hypothetical format — your emulator will have its own syntax):

; Illustrative example — syntax varies by emulator
[ItemLevelUp]
Level7_SuccessRate = 60
Level8_SuccessRate = 50
Level9_SuccessRate = 40
Protection_MinLevel = 6   ; on failure, never drops below +6

Whenever the file has comments (lines starting with ; or #), read them: many emulators document there the meaning of each column and the valid value range.

Configuring +item protection

Protection is the feature that prevents the item from dropping below a minimum level when Soul (or Chaos) fails. Without protection, a player can spend 40 Souls, reach +9 and, in a single unlucky failure, watch the item fall back to +0 — which breeds resentment and churn. With protection set to +6, for example, the worst consequence of a failure is returning to +6, preserving part of the investment.

General steps to enable it (adapt to your build):

1. Locate the protection key in the rate file (something like Protection_MinLevel or SafeLevel).
2. Set the minimum safe level. Common values: +6 (friendlier) or +7 (more hardcore).
3. Check whether protection also applies to the Chaos Machine at levels +10 to +15 — in many emulators it is a separate flag.
4. Save the file and restart only the GameServer.
5. Test with a GM account: create a +9 item and force failures until you confirm it does not drop below the defined minimum.

Many commercial servers keep full protection up to +9 and remove protection from +10 onward, creating a "risk wall" that makes top-tier items rare and valuable. This is a legitimate and widely used design decision.

Configuring the Jewel of Life

Life is where many admins stumble, because the logic differs from the other jewels. It controls the additional option (add option), which rises in increments — typically +4 per success, going from +4 up to +28 (or up to +32 in versions with an extended option). Each attempt has a success chance; on failure the value simply does not increase (no penalty).

Points of attention when configuring Life:

• Increment per success: the classic is +4. Some servers use a fixed +4, others randomize between +4 and +16 on the first success (varies by emulator).
• Maximum cap: decide whether the limit is +28 or +32. This directly affects the maximum item power in PvP.
• Success chance: usually sits between 40% and 60%. Chances that are too high quickly inflate "full option" items.
• Consumption: each attempt consumes one Life, so the chance defines, on average, how many jewels a full item costs — a central figure for the economy.

Impact on economy and balancing

Every rate adjustment is, in practice, an adjustment to the server's economy. Jewels are currency: the easier it is to upgrade items, the fewer jewels are consumed per piece and the cheaper the market becomes, which devalues farming. Some principles to keep the balance:

• Always scale: +15 should cost, on average, far more jewels than +9. The exponential difficulty curve is what sustains the value of top-tier items.
• Consider the jewel drop rate together: a high +item rate combined with a high jewel drop = hyperinflation. Adjust both as a system, not in isolation.
• Think about the server's life cycle: a "long term" server uses harsher rates; a "fast season" server may use generous rates so everyone has fun quickly.
• Measure, do not guess: track how many +13/+15 items exist in the database after the first week. If half the population is full, your rates are too high.

Testing the settings

Never trust the file numbers alone — test empirically before opening to players.

1. Bring up the staging server with the new rates.
2. With a GM account, generate a large stock of Bless, Soul and Life.
3. Upgrade 20 identical items from +0 to +9, noting how many Souls each one consumed.
4. Calculate the real average success rate and compare it with the configured value.
5. Force failures at +9 to validate the protection.
6. Raise 10 items with additional option up to +28 and note the average Life consumption.
7. Only then replicate the configuration to production.

Common errors and fixes

Launch checklist

• Backup of the configuration files and the database done.
• Bless chances (100% up to +6) validated.
• Soul chances scaled by level (+7, +8, +9).
• +item protection enabled and tested with forced failures.
• Chaos Machine configuration (+10 to +15) reviewed.
• Jewel of Life with increment, cap and chance defined.
• Empirical average-consumption tests completed on staging.
• Jewel drop rate adjusted together with the rates.
• GameServer restarted and logs checked with no errors.
• Count of +13/+15 items in the database monitored in the first week.

Frequently asked questions