How to configure 380 items (3rd option) on a MU Online server

The 380 items — so called because they typically require character level 380 for full use — represent one of the most coveted tiers of power in MU Online. They stand out for carrying a third option (3rd option), an extra attribute line that goes beyond the traditional excellent options and the additional Jewel of Life option. This third line usually brings potent bonuses like increased damage, increased defense, or high-value utility attributes, which makes these items objects of absolute desire in Guild wars and PvP rankings. Precisely because they are so strong, misconfiguring them is one of the fastest ways to break a server's balance: a drop that's too easy turns everyone into "full 380" within a week; a third option that's too strong makes anyone without the item irrelevant in the arenas.

In this advanced tutorial I explain what characterizes a 380 item, how to configure its drop and creation, how to define the third option, and above all how to think about the impact on PvP and the economy. The concepts apply to modern versions (Season 6+), but file names, columns, and configuration keys vary by emulator (IGCN, MuEmu, Zhyper, and derivatives). Treat every number as an example and validate it against your build's documentation before applying it in production.

Prerequisites

This is advanced content that assumes mastery of the server structure and the excellent item system. If you're still building the foundation, start with the guide on how to create a MU Online server and come back when the server is already stable.

• A working server with GameServer, ConnectServer, and DataServer running error-free.
• Administrative access to the database (MSSQL) and to the configuration folders.
• The drop and excellent item system already understood and configured.
• A configuration file editor (Notepad++ or equivalent).
• A staging environment separate from production.
• A complete backup of configurations and database before any change.
• A GM account able to generate 380 items and creation materials for testing.

What defines a 380 item

A 380 item is distinguished from an ordinary excellent by three main characteristics:

• High level requirement: it typically requires level 380 (hence the name) and higher strength/agility requirements, acting as a natural brake on access.
• Exclusive third option: on top of the excellent options and the additional option (Life), it carries an extra attribute line, usually of high value, that does not exist on ordinary items.
• Controlled origin: it isn't a trivial drop from just any mob; it comes from specific sources (high-level maps, creation in the Chaos Machine, combining materials), which preserves its rarity.

It's important to understand that "380 item" is a community convention describing this set of properties. The exact way each emulator implements the third option varies: some use an "ancient/380" flag on the item itself, others treat it as a separate option group. Confirm your build's model before configuring.

Third option attributes

The third option is the heart of the 380 item and the most sensitive balancing point. It usually rolls one of several possible attributes, with an associated value. Below is an example table of typical third options (illustrative values — the real ones vary by emulator):

The golden rule: the more direct the impact on PvP (damage reduction, percentage damage), the more conservative the cap should be. A "damage reduction taken" third option that's too high, stacked on a full set, creates nearly immortal characters — one of the most common mistakes on poorly balanced servers.

Configuring the drop of 380 items

The drop is what defines the rarity — and therefore the value — of 380 items. The exact locations vary by emulator, but the typical configuration points are:

• A drop table/file per monster or per map (e.g., ItemDrop, MonsterSetBase, GremoryCase, or similar): defines which mobs/maps drop 380 items and the chance.
• Excellent/380 item configuration (e.g., ItemOptionRate, Item380Option): defines the chance of the drop coming with the third option and which attribute.
• Event configuration (Blood Castle, Chaos Castle, Boss): many servers concentrate the 380 drop in event rewards.

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

; Illustrative example — the syntax varies by emulator
[Item380Drop]
MapId = 8              ; high-level map
DropRate = 3           ; base chance for the item to drop (thousandths/percentage varies)
ThirdOptionChance = 20 ; chance for the item to come with the 3rd option
ThirdOption_MaxValue = 30 ; cap on the third option's value

Always read the file's comments: they indicate whether the chance is in percentage, thousandths, or another unit — a detail that, if ignored, makes you configure a drop a thousand times larger than intended.

Creation via Chaos Machine

Beyond the drop, many servers allow players to create 380 items by combining materials in the Chaos Machine. This gives players an active path (farming materials) instead of relying only on drop luck. Points to configure:

1. Required materials: define the list of items/jewels needed for the combination (e.g., base item + a quantity of Jewel of Chaos + Zen).
2. Success chance: the combination usually has a chance of failure; on failure, the materials may be lost (varies by emulator).
3. Result: define whether the created item already comes with a guaranteed third option or whether the third option is rolled separately.
4. Zen cost: each attempt should drain Zen to reinforce the economic role.

General steps (adapt to your build):

1. Locate the Chaos Machine configuration for 380 items.
2. Define the material recipe and the Zen cost.
3. Adjust the success chance in a tiered way.
4. Configure whether the third option is guaranteed or rolled.
5. Save and restart only the GameServer.
6. Test the combination with a GM account before releasing it.

Impact on PvP and the economy

380 items are, by definition, "endgame" items that define the top of the power curve. Every configuration decision reverberates in PvP and the economy:

• Rarity sustains value: if the drop is high, the item loses market value and everyone goes full within days, shortening the server's life. Keep it rare.
• The third option defines the power ceiling: this extra line is what separates a top player from the rest. Conservative caps keep PvP contestable for those who don't yet have 380.
• Beware of stacking: a full 380 set, each piece with a defensive third option, can create immortality. Simulate the "full defensive 380" scenario before releasing it.
• Offer both path and luck: combining drop (luck) with Chaos creation (effort) gives different player profiles a route to the item, without inflating the market.

Testing the configurations

1. Bring up staging with 380 drop and creation configured.
2. With a GM account, force the drop and creation repeatedly, noting the distribution of third options.
3. Compare the actual distribution with the configured chances.
4. Build a full 380 character and one without 380 of the same class.
5. Simulate PvP between them and evaluate whether the item breaks combat or merely favors it.
6. Verify that the level and stat requirements prevent early use.
7. Only then replicate to production.

Common errors and fixes

Launch checklist

• Backup of configurations and database done.
• Drop sources for 380 items defined (maps/events/bosses).
• Drop chance unit confirmed (% or thousandths).
• Third option chance and value configured with a conservative cap.
• Chaos Machine creation recipe defined (materials and Zen).
• Combination success chance tiered.
• Item level and stat requirements validated.
• Full 380 vs. no-380 PvP scenario simulated.
• Full defensive stack tested against immortality.
• GameServer restarted and logs checked error-free.

Frequently asked questions