How to configure the Pet System (Fenrir, Panda, Uniria) in MU Online

The Pet System is one of the pillars of mid- and high-level gameplay in MU Online. While the Guardian Angel and the Imp deliver simple passive bonuses, pets like the Fenrir, the Panda and the Uniria combine combat effect, mount and account economy, and that is why they require careful configuration on the server. A poorly balanced Fenrir destroys your server's difficulty curve; a well-configured Fenrir becomes a progression goal that keeps players hooked for weeks. This tutorial covers the full cycle: understanding the pet slots, enabling the items on the server side, building the Fenrir's creation and upgrade recipe, tuning durability and effects, and validating everything in a test environment before opening it up to players.

An important note up front: the file names, columns and IDs cited here are examples of how most emulators organize this data. The actual structure varies by emulator (Season 6 based on text files, newer emulators with a SQL database, and forks with a web panel all have different layouts). Use the concepts as a map and confirm each field in your specific emulator's documentation before editing in production.

Prerequisites

Before touching any pet file, make sure the server's foundation is already up and stable. If you have not gone through that yet, start with the guide on how to create a MU Online server and only then come back here.

You will need:

• A working server (GameServer, ConnectServer, JoinServer and DataServer/database online).
• Write access to the item configuration files (Item.txt/ItemList or equivalent tables) and to the client's item file (Item.bmd/Item.txt of the Main).
• A text editor with UTF-8 support and column view (VS Code, Notepad++), and a database client (HeidiSQL, SSMS) if the emulator uses SQL.
• A GM account or admin command to generate items in testing (/make, /item or equivalent).
• A full backup of the files and the database before starting. This is not optional.

Also set aside a "guinea pig" character account separate from your main account, so you do not corrupt real progress during durability and drop testing.

Understanding the slots and the pet types

In classic MU, pets are not all treated the same way by the server. It is useful to split them into three categories:

1. Passive-bonus pets (Guardian Angel, Imp, Satan/Dinorant in part): occupy a pet slot and apply an effect while equipped.
2. Mounts (Dark Horse, Uniria, Fenrir): occupy the mount slot; the character rides and gains mobility in addition to the bonus.
3. Event/EXP pets (Panda, Skeleton, Rudolph, Uniria in some seasons): themed items with an experience or drop bonus, almost always with durability that expires.

The critical balancing point is that the Fenrir and the Uniria compete for the same mount slot. This means a player cannot stack both; they choose. The Panda, being a wing/back pet in many seasons, can coexist with a mount. Document which slot each item uses on your emulator before defining bonuses, because stackable bonuses completely change the PvP math.

Enabling the pet items on the server

The first practical step is to make sure the pet IDs are active and consistent between server and client. Each item in MU is identified by a section/index pair (category and index within the category). Classic pets are traditionally in section 13 (miscellaneous/wings/pets), but this varies by emulator.

Locate the pet entries in your item file/table. In a text-based emulator, the line usually looks like this (illustrative example):

// section index name       slot durability ...
13   37    "Fenrir"          -1   255        ...
13   3     "Uniria"           7   60         ...
13   80    "Panda"            8   60         ...

What to check in each entry:

• The name matches the client's exactly. A mismatched name causes a "blank" item or an inventory crash.
• The maximum durability is defined. A pet with durability 0 disappears when equipped.
• The tradeable/droppable flag is set to the value you want (the norm is a non-droppable Fenrir).
• The item is marked as a pet/mount in the type field, so the client renders the mount animation.

After editing, the item must exist identically on the client. If the server knows the Fenrir at 13/37 but the client expects it at 13/38, the player sees the wrong item or nothing. Always sync both ends.

Creating and upgrading the Fenrir

The Fenrir is the high point of the system because it is not just dropped: it is built from a recipe, usually in the Chaos Goblin Machine (the "combination machine"). The traditional flow has two phases: create the base Fenrir (broken/incomplete) and then perform the upgrade into one of the bonus variations.

Step by step of the classic flow:

1. Gather the components. The historical recipe calls for items like Splinter of Armor, Bless of Guardian, Claw of Beast and Fragment of Horn, obtained in events like Kanturu and drops from specific maps. The items and quantities vary by emulator.
2. Combine in the Chaos Machine with the configured success rate. The result is the base Fenrir, still without a defined combat bonus.
3. Perform the upgrade by adding a refining item (commonly a quantity of Jewel of Chaos, Jewel of Bless/Soul or Zen) to turn the base Fenrir into a variation:

• Strength Fenrir (damage bonus),
• Health Fenrir (HP bonus),
• Mana Fenrir,
• black/golden Fenrir (the "perfect" version, with the best bonus).

1. Define the success rate and the zen cost of each stage in the server's combinations file.

On the server side, the recipe lives in the Chaos Machine's combinations file (something like ChaosMix, ChaosBox or a T_ChaosMix table, depending on the emulator). A recipe block usually declares: input items, output item, zen cost, base success rate and modifiers. Conceptual example:

[FenrirBase]
Cost      = 5000000
Rate      = 80
In1  = 13:37:0     ; ingredient
In2  = 14:13:0     ; jewel
Out  = 13:37:0     ; base Fenrir

Adjust the Rate carefully: a rate that is too high trivializes the Fenrir, and one that is too low generates frustration and account reselling. On moderate-progression servers, rates between 60% and 80% for the base and slightly lower for the perfect version work well.

Configuring effects and bonuses

The Fenrir's effects have two natures. The first is the area attack characteristic of the mount: a strike that hits several enemies around it, very strong in farming and in crowded PvP. The second is the static bonus of the variation (damage, health or mana), applied while the Fenrir is equipped and has durability.

On the server, these bonuses are normally defined by an item option or by a rule coded to the Fenrir's ID. Where there is an options table, you associate a bonus value with the item; where the effect is fixed in the emulator, you adjust configuration constants. Balancing points worth attention:

• Scale of the area attack. If the area damage is too high, the Fenrir becomes mandatory and kills build diversity. Measure the damage against the mobs of the main farming maps.
• Stacking with wings and sets. Confirm whether the Fenrir's bonus stacks with level-3 wings and ancient sets. Uncontrolled totals break PvP.
• Bonus per variation. Document exactly how much each Fenrir (strength/health/mana/perfect) grants, so players understand the choice and so you can audit suspicious accounts.

Durability, repair and pet items

Mount and event pets have durability that drops with use or over time. For the Fenrir, durability drops when taking hits and when using the area attack; when it hits zero, the Fenrir stops applying bonuses and the character dismounts. Repair is usually done at the blacksmith NPC by paying zen, or by consuming a jewel, depending on the configuration.

For the Panda and the Uniria, which are event items, the common approach is durability that expires with playtime, not just with damage. This is intentional: they are temporary campaign or reward bonuses. Configure the maximum durability value and the consumption per minute/use according to your server's pace.

Practical recommendations:

• Mark Fenrir, Dark Horse and event items as non-droppable on death, by editing the item-loss rule or the item's own flag. Nothing generates more complaints than losing a hard-won Fenrir.
• Decide whether the Fenrir can be traded. On many servers it is locked from trade to prevent RMT and account theft.
• Test the repair with a guinea pig account: wear the durability down to zero, repair it, and confirm the bonuses come back.

Synchronizing server and client

Every pet item must exist on both sides with the same section/index, name and type. Beyond the item file, the client needs the mount's models and textures (Fenrir model files and effects) and the translation/name entries. If you added a custom Fenrir or a new color, the client package must include the corresponding model, otherwise the player rides an invisible "ghost" or the client crashes.

Safe synchronization flow:

1. Edit the item on the server.
2. Mirror the same entry in the client's item file.
3. Confirm the model/effect files exist on the client.
4. Generate the item on a test account and mount it to validate the animation, bonus and durability.
5. Only then distribute the client patch to players.

Common errors and fixes

Balancing tests

Before release, run a battery of tests with guinea pig accounts representing the main classes (DK, DW, Elf, MG). Measure the Fenrir's farming damage on mid- and high-level maps, and simulate 1v1 and group PvP. Note the numbers. If the Fenrir dominates every build decision, reduce the area damage or the perfect variation's bonus. The goal is for the Fenrir to be strong and desirable, without being mandatory.

Also test the economy: how much does it cost, in time and resources, to build a perfect Fenrir? If it is too fast, everyone has one in a day and the item loses value. If it is impossible, no one chases it. Calibrate the recipe and the rates so that the Fenrir is a goal of a few weeks of dedicated play.

Launch checklist

• Full backup of files and database before any edit
• Fenrir, Panda and Uniria IDs checked and identical between server and client
• Maximum durability defined for all pets
• Fenrir, Dark Horse and event items marked as non-droppable on death
• Fenrir creation and upgrade recipe with IDs and rates reviewed
• Bonus of each Fenrir variation documented
• Mount slots checked (Fenrir vs Uniria vs Dark Horse do not stack)
• Mount models and effects present in the client patch
• Durability repair tested with a guinea pig account
• Area-damage balancing validated in farming and PvP
• Trade/RMT rule defined for the Fenrir
• Final creation-upgrade-mount test on a clean account passed

Frequently asked questions