How to configure the Jewel of Guardian in MU Online

The Jewel of Guardian is one of the jewels that define the item protection layer on modern MU Online servers. While Bless and Soul handle refinement and Life handles options, Guardian moves into more delicate territory: item safety. It applies what is called the guardian option — a protection attribute that, depending on the emulator, reduces the risk of loss during refinement, adds defense, or marks the equipment as protected. Configuring this jewel correctly is what separates a tense, rewarding refinement system from a frustrating one in which players lose expensive items and abandon the server.

This guide covers the entire Jewel of Guardian cycle: understanding the attribute it grants, configuring the application success rate, restricting where it can be used, defining the behavior on failure, and calibrating the drop to keep the jewel at the right value. As always, I use table and file names as examples; the logic is common to almost every emulator, but the names and the exact mechanics of the guardian option vary by emulator. If you don't have your server up yet, start with the tutorial on how to create a MU Online server.

Prerequisites

• Server files that support the Jewel of Guardian and the guardian option natively.
• Database access with write permission on the game database (MuOnline in most cases).
• Access to the GameServer data folder, typically GameServer/Data/, where the jewel, item, and drop configurations live.
• A text editor with the correct encoding to edit .txt, .ini, or .xml without corrupting them.
• A full backup of the database and configurations before any change.
• A test GM character with high-refinement items to validate application, success, and failure.

Step 1: Understand the guardian option

The starting point is understanding what the Jewel of Guardian actually writes onto the item. The guardian option is a protection attribute associated with the equipment. In emulators, it usually manifests in one of these forms (or a combination):

The important point: the guardian option is an attribute written onto the item, with its own index or flag. Like other options, this index is a contract — the server writes it, and the client (when there is a visual display) translates it. Before configuring anything, find out which effect your emulator assigns to the jewel, because that changes your entire balancing strategy.

Step 2: Locate the jewel configuration

Find where your emulator declares the Jewel of Guardian and its behavior. There are two patterns:

1. File-based — a .txt/.ini/.xml in the data folder describes the jewel, its success rate, and restrictions.
2. Database-based — a table stores the jewel's parameters.

For the database pattern, explore the available names:

USE MuOnline
GO
SELECT name FROM sys.tables
WHERE name LIKE '%Jewel%' OR name LIKE '%Guardian%' OR name LIKE '%Option%'
GO

A jewel configuration table (illustrative name T_JewelConfig) usually has columns like:

In the file pattern, look for something like GameServer/Data/JewelOfGuardian.txt:

[JewelOfGuardian]
Enable=1
SuccessRate=60          ; 60% chance to apply the guardian option
MinItemLevel=7          ; item must be +7 or higher
AllowedItemKind=weapon,armor
FailBehavior=consume    ; on failure, just consume the jewel (varies by emulator)

Step 3: Configure the success rate

The success rate is the main dial for tension and value. A high rate makes protection accessible and refinement relaxed; a low rate makes Guardian a precious resource and the endgame risky. Choose deliberately according to the server's profile.

USE MuOnline
GO
-- Set 60% success on the Jewel of Guardian application
UPDATE T_JewelConfig
SET SuccessRate = 60
WHERE JewelType = 'Guardian'
GO

Calibration reference by server profile:

Step 4: Restrict where the jewel can be applied

Letting Guardian apply to any item makes the system trivial. Restrict it by item type and by minimum refinement level, ensuring protection is an investment in equipment already worth protecting.

USE MuOnline
GO
-- Only allow Guardian on items +7 or higher
UPDATE T_JewelConfig
SET MinItemLevel = 7
WHERE JewelType = 'Guardian'
GO

In the file pattern, adjust the allowed categories:

[JewelOfGuardian]
AllowedItemKind=weapon,armor,helm,gloves,boots
MinItemLevel=7

Step 5: Define the behavior on failure

What happens when the application fails defines how punishing the system is. The most common behaviors (the one supported varies by emulator):

1. Consume the jewel with no effect — the only penalty is the cost of the lost jewel. This is the friendliest.
2. Reduce the item's refinement — the failure downgrades the item a few levels. Medium penalty.
3. Destroy the item — the failure erases the equipment. Maximum penalty, typical of hard servers.

[JewelOfGuardian]
FailBehavior=consume     ; consume | downgrade | destroy (varies by emulator)

If the behavior is configurable in the database:

USE MuOnline
GO
-- On failure, just consume the jewel (safest behavior)
UPDATE T_JewelConfig
SET FailBehavior = 'consume'
WHERE JewelType = 'Guardian'
GO

Step 6: Configure the Jewel of Guardian drop

Guardian only has value if it is deliberately scarce. Like any jewel, it goes into your emulator's drop list (for example GameServer/Data/Item/ItemDrop.txt or a drop table — varies by emulator). The concept is always to associate the jewel item with a source at a percentage chance.

// MapNumber  MonsterClass  ItemGroup  ItemIndex  Chance(%)
8    45    14    31    0.8
// Jewel of Guardian (group 14, index 31) - 0.8% on the boss of map 8

Distribution strategies and reference chances:

Step 7: Test application, success, and failure

With everything configured, validate the cycle with the GM character. Create test items at the minimum required refinement level and run the application several times to observe both success and failure.

Test script:

1. Create an item at the minimum allowed level and one below the minimum.
2. Try to apply Guardian to the item below the minimum — it should be refused.
3. Apply it to the valid item and confirm success: the protection attribute appears.
4. Repeat several times to observe failures and confirm that FailBehavior acts as configured.
5. Verify that the protected item resists the scenario the protection covers (refinement, death, etc.).
6. Confirm that the jewel is consumed on each attempt.

USE MuOnline
GO
-- Inspect the raw item state of a test character
SELECT Name, Inventory FROM Character WHERE Name = 'YourGMChar'
GO

Step 8: Document and communicate the system

A protection system only fulfills its role if players trust it. Publish the rules on your website: success rate, minimum item level, accepted types, what the guardian option protects, and what happens on failure. Mirror the server configuration exactly. A gap between what is announced and what is real breeds accusations of manipulation — something that quickly erodes a private server's reputation.

Common errors and fixes

Launch checklist

• Full backup of the database and configurations done and verified
• Real effect of the guardian option on your emulator identified
• Jewel configuration located (file or table)
• Success rate set according to the server profile
• Item-type and minimum-level restrictions applied
• Failure behavior (consume/downgrade/destroy) chosen and tested
• Jewel of Guardian drop calibrated on the chosen sources
• Application cycle tested: refusal, success, and failure on the GM
• Protection effect validated in the scenario it covers
• Jewel consumption per attempt confirmed
• Rules documented publicly and synced with the server
• GameServer fully restarted after all changes

Frequently asked questions