How to configure the Jewel of Harmony and item refinement in MU Online

The Jewel of Harmony system is one of the most sophisticated progression layers in MU Online and, for that very reason, one of the most misunderstood by beginner administrators. Unlike the Bless, Soul, and Life jewels — which respectively raise the item's level and the additional option — Harmony introduces a third dimension of power: refinement. It applies a special attribute to the equipment (increased damage, increased defense, reduced mana per hit, critical damage rate, among others) that depends on a refinement level and requires the character to have a sufficient level to activate it. Configuring this system correctly is essential: poorly calibrated values can turn refinement into a "win button" in PvP, while badly tuned chances frustrate players who spend stacks of jewels with no result.

In this advanced guide I explain the real mechanics of Harmony, how to configure the refinement options, costs, and chances, how to enable the removal of unwanted attributes, and, most importantly, how to balance all of it to preserve the health of PvP. The concepts are universal to modern versions (Season 6+), but file names, columns, and keys vary by emulator (IGCN, MuEmu, Zhyper, and derivatives). Use the numeric values only as examples and always validate against your build's documentation.

Prerequisites

This is an advanced tutorial. Before touching refinement, you need to master the server's basic structure. If you're still getting started, first follow the guide on how to create a MU Online server and only then move on to configuring Harmony.

• A stable server with GameServer, ConnectServer, and DataServer running without errors.
• Administrative access to the database (MSSQL) and to the configuration folders.
• Familiarity with the basic jewel system (Bless, Soul, Life) already configured.
• A configuration file editor (Notepad++ or equivalent).
• A staging environment isolated from production.
• A full backup of configurations and database before any change.
• A GM account to generate Jewels of Harmony and test items.

Understanding the Harmony system

Harmony works on its own layer, independent of the item's "+" (Bless/Soul) and the additional option (Life). When applied, it rolls a refinement option type and a level for that option. Each item type (weapon, shield, armor set) has its own set of possible options.

The most common option groups are:

• Weapons: increased damage (minimum and maximum), increased damage percentage, increased attack speed, increased skill damage.
• Shields and armor: increased defense, increased defense percentage, increased maximum HP, reduced incoming damage.
• Utility options: reduced strength/agility requirement, increased recovery rate, reduced mana per hit.

Each option has a refinement level (for example, from 1 to 15) and each level requires the character to have a minimum level for the attribute to work. A high-level refinement on an item used by a low-level character stays inactive until they reach the requirement — a mechanic that exists precisely to prevent beginners from carrying absurdly strong items.

Refinement options and their values

The key to balancing lies in defining which options exist and the value of each level. Below, an example table illustrating how a group of weapon options could be scaled (the values are purely illustrative — the real ones vary by emulator):

Notice the role of the "required character level": it is the system's main balancing brake. A level 13 maximum-damage refinement might require, for example, level 260 to work — which prevents the attribute from dominating low-level arenas. Adjusting that column is as important as adjusting the attribute value itself.

Where to configure Harmony

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

• Refinement options table/file (e.g., HarmonyOption, JewelOfHarmony.txt, or a database table): defines the option types, values per level, and requirements.
• Success chance configuration per item group: defines the probability of rolling each option and each level.
• Refinement cost configuration (e.g., in Zen or jewel consumption): controls the price of each attempt and of removal.
• General GameServer flags: enable/disable the system and define global rules.

An illustrative example of a configuration entry (hypothetical format — your emulator will have its own syntax):

; Illustrative example — the syntax varies by emulator
[HarmonyWeapon]
Option_IncreaseMaxDamage_MaxLevel = 13
Option_IncreaseMaxDamage_ValuePerLevel = 3
Option_IncreaseMaxDamage_ReqCharLevel = 20   ; multiplied by the refinement level
SuccessRate = 45          ; chance to apply refinement
RemoveCost_Zen = 1000000  ; cost in zen to remove the option

Always read the file's comments. Most emulators document there the valid range of each value and the meaning of the columns, keeping you from applying a number outside the accepted range and jamming the system.

Configuring cost and chance

Harmony refinement needs to be a significant economic sink, otherwise it loses its appeal and inflates the server's overall power. There are three cost variables to control:

1. Cost per refinement attempt: each Harmony application consumes a jewel and, in many cases, an amount of Zen. Set a value that makes top-tier refinement expensive but not impossible.
2. Success chance: the probability of the refinement "landing" and rising to a high level. The classic approach is for the chance to fall as the target level rises — a level 13 refinement should be rare.
3. Removal cost: erasing a bad option to try again should also cost Zen (and sometimes jewels). Without a removal cost, the player re-rolls infinitely until the perfect result, which nullifies balancing.

General steps to configure (adapt to your build):

1. Locate the Harmony options file/table.
2. Define each option's value per level and the required character level.
3. Adjust the SuccessRate in a graduated way per target level.
4. Configure the Zen cost per attempt.
5. Configure the option removal cost.
6. Save and restart only the GameServer.

Removing unwanted attributes

An essential part of the system is allowing the player to remove a bad option. Since Harmony rolls the type and level, it is common to get an attribute that doesn't fit the character's build (for example, requirement reduction on a pure PvP item). Removal returns the item to a neutral state for a new attempt.

Aspects to define for removal:

• Method: some emulators use the Jewel of Harmony itself in "removal mode"; others use a dedicated item. Confirm your build's model.
• Cost: charge Zen (and optionally jewels) so removal is not free.
• Preservation: ensure removal erases only the Harmony option, without affecting the +level (Bless/Soul) or the additional option (Life). Test this explicitly.

PvP balancing

Harmony refinement affects PvP more than any other layer, because many of its options are directly offensive or defensive: extra damage, percentage damage, reduced incoming damage. Some principles to avoid breaking the arenas:

• Cap the ceilings: a high "percentage damage increase" collapses TTK (time to kill) and makes PvP binary. Prefer conservative ceilings.
• Use the required level as a brake: the stronger the option, the higher the required character level to activate it.
• Beware of damage reduction: defensive Harmony options combined with high-defense sets can create practically immortal characters. Test extreme combinations.
• Consider the stack with other layers: an item +15 + additional option +28 + maximum-damage Harmony level 13 is the absolute peak. Simulate that scenario before releasing.

Testing the system

1. Bring up staging with the Harmony configuration applied.
2. With a GM account, generate a stock of Jewels of Harmony and Zen.
3. Apply refinement to 20 identical weapons, noting which options and levels came out.
4. Compare the actual distribution with the configured chances.
5. Test removal and confirm that the +level and the additional option remain intact.
6. Build a test character with maximum refinement and validate the PvP impact against another without refinement.
7. Only then replicate to production.

Common errors and fixes

Launch checklist

• Backup of configurations and database done.
• Refinement options per item type defined.
• Values per level and required character level reviewed.
• Success chances scaled per target level.
• Cost per attempt in Zen configured.
• Option removal cost configured.
• Removal tested without affecting +level and additional option.
• PvP scenario with maximum refinement simulated.
• Offensive and defensive ceilings validated in balancing.
• GameServer restarted and logs checked with no errors.

Frequently asked questions