How to set up Ruud and the Ruud shop in MU Online

Ruud is one of the most important special currencies on modern MU Online servers. Unlike Zen — which is abundant and serves day-to-day needs — Ruud was designed as an endgame progression currency: you earn it in difficult content and spend it on items that make a real difference to your character. That's why configuring Ruud is not just about flipping on a column in the database; it's about designing a complete economic circuit where the income sources, the Ruud shop, and the balancing all talk to each other. A poorly calibrated circuit breaks the server in two ways: if Ruud is too easy to get, exclusive items lose value and the endgame evaporates; if it's too hard, the casual player never reaches anything and quits.

This guide covers the full cycle: understanding where Ruud lives in the data, enabling its income sources, building the shop with exclusive items, placing the vendor NPC and — the point most people ignore — balancing the currency's inflow and outflow. I use table and file names as examples; the architecture is common to almost every emulator, but the exact names vary by emulator. If you're still building the foundation, first check out the tutorial on how to create a MU Online server.

Prerequisites

• Modern server files with Ruud support (very old files don't have the currency natively).
• Database access with write permission on the game database (MuOnline in most cases).
• Access to the GameServer data folder, typically GameServer/Data/.
• A text editor with the correct encoding to edit .txt and .ini files without corrupting them.
• A full backup of the database and configurations before any change.
• A test GM character to validate balance, shop, and purchase limits.

Step 1: Understand the Ruud circuit

Before touching anything, picture Ruud as a three-stage circuit:

1. Income (inflow) — where Ruud comes from: events, maps, quests, bosses, invasion rewards.
2. Storage — where the balance is recorded: usually a column in the character table.
3. Spending (outflow) — where Ruud goes: the Ruud shop and its exclusive items.

Balancing is nothing more than keeping inflow and outflow in equilibrium. If the average monthly inflow of an active player is X and the most desired item costs far more than a few months of X, the item is a long-term goal. If it costs less than a week, it's disposable. You decide where each item falls on that scale.

Step 2: Locate and verify Ruud storage

The first technical task is confirming where the balance lives. In most emulators, it's a column in the character table:

USE MuOnline
GO
-- Check whether the Ruud column exists in the character table
SELECT COLUMN_NAME, DATA_TYPE, COLUMN_DEFAULT
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'Character' AND COLUMN_NAME = 'Ruud'
GO

If the column doesn't exist and your emulator expects it to, create it with a zeroed default value:

USE MuOnline
GO
ALTER TABLE Character ADD Ruud INT NOT NULL DEFAULT 0
GO

To inspect a character's current balance:

USE MuOnline
GO
SELECT Name, Ruud FROM Character WHERE Name = 'YourGMChar'
GO

Step 3: Configure the Ruud income sources

Here is the heart of inflow balancing. Each source you enable adds Ruud to the economy; the sum of all of them sets the pace at which players accumulate. The classic sources:

Event reward configuration usually lives in a rewards .ini file or in a configuration table. Example in .ini (illustrative — varies by emulator):

; Ruud reward per event and level
[BloodCastle]
BC1_Ruud=200
BC4_Ruud=500
BC7_Ruud=1000

[DevilSquare]
DS1_Ruud=150
DS5_Ruud=700

[ChaosCastle]
CC1_Ruud=100
CC7_Ruud=800

Or via a configuration table:

USE MuOnline
GO
-- Adjust an event's Ruud reward (illustrative names)
UPDATE T_EventRuudConfig
SET RuudReward = 1500
WHERE EventType = 1 AND EventLevel = 7
-- EventType 1 = Blood Castle (example; varies by emulator)
GO

Step 4: Build the Ruud shop

The Ruud shop is the currency's main outflow. It's usually defined by a table that lists each available item, with its price and restrictions. An exploratory query to see the structure:

USE MuOnline
GO
SELECT TOP 20
    ShopCode, ItemGroup, ItemIndex, ItemLevel, ItemOption,
    Price, ClassFlag, BuyLimit, Enabled
FROM T_RuudShopList
ORDER BY ShopCode
GO

The most relevant fields (illustrative names):

To add an exclusive item — for example, an endgame wing for 15,000 Ruud, available to all classes:

USE MuOnline
GO
INSERT INTO T_RuudShopList
    (ShopCode, ItemGroup, ItemIndex, ItemLevel, ItemOption, Price, ClassFlag, BuyLimit, Enabled)
VALUES
    (1, 12, 36, 0, 0, 15000, 255, 0, 1)
-- ClassFlag 255 = all classes; BuyLimit 0 = no limit
GO

To adjust the price of an already registered item:

USE MuOnline
GO
UPDATE T_RuudShopList
SET Price = 8000
WHERE ShopCode = 1 AND ItemGroup = 13 AND ItemIndex = 0
GO

Step 5: Set purchase limits

The purchase limit is the most important tool against imbalance. Very strong items need a per-character cap so that the advantage isn't merely a function of who has more free hours.

USE MuOnline
GO
-- Limit a special item to 1 purchase per character
UPDATE T_RuudShopList
SET BuyLimit = 1
WHERE ShopCode = 1 AND ItemGroup = 12 AND ItemIndex = 36

-- Remove the limit from a consumable item
UPDATE T_RuudShopList
SET BuyLimit = 0
WHERE ShopCode = 1 AND ItemGroup = 14
GO

If the emulator records purchase history, you can audit who bought what:

USE MuOnline
GO
SELECT TOP 50 CharName, ItemGroup, ItemIndex, Price, BuyDate
FROM T_RuudShopBuyLog
ORDER BY BuyDate DESC
GO

Step 6: Place the vendor NPC

The shop needs an NPC to be accessible in the world. Placement is usually done in a monster/NPC spawn file (for example GameServer/Data/Monster/MonsterSetBase.txt — varies by emulator). Each line defines the NPC index, map, coordinates, and direction:

// Ruud Shop NPC - starting town
// Index  Map  X    Y    Dir  Action  Range
658    0    136  140  0    0       50

To offer the shop in more than one town, replicate the line with different maps and coordinates:

658    3    170  100  0    0       50
658    51   215  45   0    0       50

Step 7: Balance inflow and outflow

With the sources and shop ready, do the math that sustains the economy. Estimate the average monthly inflow of an active player by adding up the realistic rewards from the sources they frequent. Then look at the shop prices and classify each item:

Adjust until the curve makes sense for your server's audience. A "hard" server pushes everything to the right; an "easy/fun" server concentrates on the left. The fatal mistake is mixing them without intent — cheap powerful items next to expensive cosmetics confuse and frustrate.

Step 8: Test the full cycle

Before opening to players, close the loop with the GM character:

1. Add test Ruud to the character.
2. Go to the placed NPC and open the shop.
3. Confirm that the items appear with correct prices and restrictions.
4. Buy an item with a limit and try to buy it again — the limit must block it.
5. Confirm in the database that the correct amount of Ruud was deducted.

USE MuOnline
GO
-- Credit test Ruud
UPDATE Character SET Ruud = Ruud + 50000 WHERE Name = 'YourGMChar'
-- Check the balance after the test purchase
SELECT Name, Ruud FROM Character WHERE Name = 'YourGMChar'
GO

Common errors and fixes

Launch checklist

• Full backup of the database and configurations made and verified
• Ruud balance column/table confirmed and in the right model (account or character)
• Income sources enabled with calibrated rewards
• Ruud shop built with exclusive items and defined prices
• Purchase limits applied to strong items
• Class restrictions (bitmask) checked on each item
• Vendor NPC placed at a valid coordinate and tested
• Monthly inflow estimated and prices classified on the balancing scale
• Full cycle (earn, open shop, buy, deduct) tested on the GM
• Balance persistence confirmed after relog and restart
• Periodic balancing reassessment plan defined

Frequently asked questions