Brazil's biggest MU Online portal — since 2003
Tutorial Intermediate Tutoriais

How to Configure the Wings System on MU Online Server

Complete technical guide to configure the Wings system on a MU Online server: SQL tables, .ini files, craft requirements, and drop rates by season.

VI ViciadosMU Team · Updated on 3 jul 2026 · ⏱ 12 min read

How to Configure the Wings System on MU Online Server

The Wings system is one of MU Online's core mechanics — it defines character progression, combat power, and visual prestige. Configuring this system correctly on your server involves three layers: SQL Server tables, GameServer configuration files, and Chaos Goblin craft rules. This guide covers complete configuration for MuServer Season 6 (the most widely used season on private servers), with notes for earlier and later seasons.


Prerequisites

  • MuServer installed (GameServer/, DataServer/, ConnectServer/)
  • SQL Server 2008 or higher with the MuOnline database configured
  • Access to SQL Server Management Studio (SSMS)
  • GameServer configuration files in the GameServer/Data/ directory

Part 1 — Wings System Database Structure

Step 1: Identify the relevant tables

Connect to SQL Server via SSMS and run the following to list wing-related tables in the MuOnline database:

USE MuOnline;
SELECT TABLE_NAME
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_NAME LIKE '%WING%' OR TABLE_NAME LIKE '%CHAOS%'
ORDER BY TABLE_NAME;

The main tables in Season 6 are:

TablePurpose
T_GS_CHAOSMIXChaos Goblin rates and ingredients
T_GS_WINGSOPTIONINFOWing options and bonuses
T_GS_ITEMDROPINFOItem drop control in the world
T_GS_GSINFOGlobal GameServer flags (enables/disables systems)

Step 2: Check global wing flags

USE MuOnline;
SELECT ServerCode, WingLv1Enable, WingLv2Enable, WingLv3Enable
FROM T_GS_GSINFO
WHERE ServerCode = 1;

To enable all wing levels:

UPDATE MuOnline..T_GS_GSINFO
SET WingLv1Enable = 1,
    WingLv2Enable = 1,
    WingLv3Enable = 1
WHERE ServerCode = 1;
Nota: WingLv3Enable controls third-level wings such as Cape of Lord, Wing of Ruin, and Wing of Dimension. If this field is set to zero, players will not be able to create or equip these wings, even if they exist in the client.

Part 2 — Chaos Goblin Configuration (Wing Crafting)

Step 3: Understand the T_GS_CHAOSMIX table

USE MuOnline;
SELECT MixType, MixName, MixRate, NeedChaos, NeedBless, NeedSoul
FROM T_GS_CHAOSMIX
ORDER BY MixType;

Relevant MixType values for wings in Season 6:

MixTypeDescription
1Wings Level 1 (Wing of Elf, Wing of Heaven, etc.)
2Wings Level 2 (Wing of Dragon, Wing of Eternal, etc.)
22Wings Level 3 (Wing of Ruin, Cape of Lord, etc.)
23Condor Flame (ingredient for Level 3 wings)

Step 4: Adjust craft success rates

-- Set success rate for Wings Level 1 (recommended: 80%)
UPDATE MuOnline..T_GS_CHAOSMIX
SET MixRate = 80
WHERE MixType = 1;

-- Set success rate for Wings Level 2 (recommended: 70%)
UPDATE MuOnline..T_GS_CHAOSMIX
SET MixRate = 70
WHERE MixType = 2;

-- Set success rate for Wings Level 3 (recommended: 60%)
UPDATE MuOnline..T_GS_CHAOSMIX
SET MixRate = 60
WHERE MixType = 22;

Step 5: Configure craft ingredients via .ini file

Open GameServer/Data/ChaosCastle/ChaosMixInfo.ini (in some builds: GameServer/Data/Etc/ChaosMix.ini):

[WingMix_Level2]
; Wing of Dragon - Dark Knight
MixType=2
NeedChaos=20
NeedBless=5
NeedSoul=5
NeedItem=ItemCode:12,13,255,0  ; Jewel of Chaos
ExtraItem=ItemCode:12,14,255,0 ; Feather of Condor (optional in some builds)
MixRate=70
ZenCost=2000000

[WingMix_Level3]
; Cape of Lord, Wing of Ruin, Wing of Dimension
MixType=22
NeedChaos=20
NeedBless=20
NeedSoul=20
ExtraItem=ItemCode:12,42,255,0 ; Condor Flame
MixRate=60
ZenCost=5000000
Atenção: The ItemCode format Category,Index,Durability,Option varies between MuServer builds. Confirm item indexes by querying the T_GS_ITEMINFO table in the database or the decoded GameServer/Data/Item/Item.bmd file. Using wrong indexes causes crafting to fail silently without any error message.

Part 3 — Wing Drop Configuration

Step 6: Configure drops via MonsterSetBase file

Edit GameServer/Data/Monster/MonsterSetBase.txt. Each line represents a monster and its possible drops:

; Format: MonsterIndex MapIndex X Y Direction SetType DropItemGroup
; DropItemGroup references groups defined in ItemDropGroup.txt

; Example: Ice Queen (Icarus map) dropping Wing of Heaven (Level 1)
095 10 121 143 0 0 WingDrop_Lv1

; Balrog (Dungeon map) dropping Wing of Dragon (Level 2)
006 01 180 022 0 0 WingDrop_Lv2

Step 7: Define drop groups in ItemDropGroup.txt

Edit GameServer/Data/Monster/ItemDropGroup.txt:

[WingDrop_Lv1]
; Wing of Elf (Category=12, Index=3)
Item=12,3,0,0,Rate=30
; Wing of Heaven (Category=12, Index=4)
Item=12,4,0,0,Rate=30
; Wing of Satan (Category=12, Index=5)
Item=12,5,0,0,Rate=30
MaxDrop=1

[WingDrop_Lv2]
; Wing of Dragon (Category=12, Index=6)
Item=12,6,0,0,Rate=20
; Wing of Darkness (Category=12, Index=7)
Item=12,7,0,0,Rate=20
; Wing of Eternal (Category=12, Index=8)
Item=12,8,0,0,Rate=20
MaxDrop=1
Dica: The Rate value is proportional — not a direct percentage. If you want a rare wing at 5% relative to others at 30%, simply use Rate=5. The system calculates the total and distributes proportionally. Set rarer wings with lower Rate values and common items with higher Rate values within the same group.

Part 4 — Wing Options and Bonuses

Step 8: Configure options via SQL

-- Check currently configured options for Level 2 Wings
USE MuOnline;
SELECT WingsType, OptionType, OptionValue, OptionRate
FROM T_GS_WINGSOPTIONINFO
WHERE WingsType = 2
ORDER BY OptionType;

To insert a new option (example: +10% damage for Wing of Dragon):

INSERT INTO MuOnline..T_GS_WINGSOPTIONINFO
(WingsType, OptionType, OptionValue, OptionRate, MaxOptionCount)
VALUES
(2, 1, 10, 100, 4);
-- WingsType=2: Level 2 wings
-- OptionType=1: Attack damage bonus
-- OptionValue=10: +10%
-- OptionRate=100: always appears when selected
-- MaxOptionCount=4: maximum options on the wing

Step 9: Configure options via file (.ini-based builds)

Edit GameServer/Data/Item/ItemOption.txt:

[WingsOption_Level2]
; Possible options for level 2 wings
Option1=AttackDamage,10,Rate:80    ; +10% Attack, 80% chance to appear
Option2=Defence,15,Rate:80         ; +15 Defence, 80% chance
Option3=AbsorbDamage,5,Rate:50     ; 5% Absorb Damage, 50% chance
Option4=IgnoreDefence,5,Rate:30    ; 5% Ignore Defence, 30% chance (rare)
MaxOption=2                        ; Maximum 2 options per wing

Part 5 — Verification and Troubleshooting

Step 10: Restart GameServer and check logs

After all changes, restart the GameServer. Monitor the log file in real time:

GameServer/Logs/GameServer_YYYYMMDD.log

Look for wing-related errors:

[ERROR] ChaosMix: ItemCode not found: 12,42 - Check ChaosMixInfo.ini
[ERROR] WingDrop: DropGroup 'WingDrop_Lv2' not defined in ItemDropGroup.txt
[WARNING] WingOption: WingsType 3 has no options configured

Step 11: Test crafting with a GM account

Use a GM account to test crafting directly:

/item 12 20 15 0    ; Spawns Jewel of Chaos +15 in inventory
/item 12 13 15 0    ; Spawns Feather of Condor
/item 6 0 15 0      ; Spawns Dark Knight armor for combination
Nota: In MuServer S6, the /item command generally uses the format /item category index level option. Confirm the exact format for your version in GameServer/Data/Commands/GMCommands.ini or by consulting the documentation for your specific build.

Step 12: Verify consistency between client and server

The MU Online client must have the corresponding wing definition files:

  • Client/Data/Item/Item.bmd — item definitions
  • Client/Data/Item/ItemOption.bmd — item options

If the server defines wings that do not exist in the client, players will see items with corrupted textures or the game will crash with an item read error.

Atenção: Never add wings with indexes that do not exist in the client's Item.bmd distributed to players. Desynchronization between server and client is the most common cause of crashes when equipping custom wings. Always test with the same client your players use.

Quick Reference: Season 6 Wing Indexes

WingClassCategoryIndex
Wing of ElfElf123
Wing of HeavenWizard124
Wing of SatanDark Knight125
Wing of DragonDark Knight126
Wing of DarknessDark Wizard127
Wing of EternalElf128
Small CapeSummoner1249
Cape of LordDark Lord1230
Wing of RuinBlade Knight1236
Wing of DimensionMuse Elf1237

Final Considerations

Wing configuration directly impacts server balance. Drop rates that are too high quickly devalue the item; craft rates that are too low frustrate players. The recommended balance point for servers with average EXP rates (50x-200x) is: Level 1 wings droppable in mid-level dungeons with MixRate of 75-85%, Level 2 wings with MixRate of 60-70% requiring a mandatory extra ingredient, and Level 3 wings restricted to boss drops with MixRate of 50-60%.

Monitor Chaos Mix logs weekly to identify abnormal patterns — many consecutive successful combinations may indicate a craft bug being exploited.

Perguntas frequentes

Wings are not dropping even after editing the drop files. What should I check?

Verify that the wing's ItemIndex is correct in GameServer/Data/Monster/MonsterSetBase.txt and that the monster level is high enough to drop that item. Also confirm the global drop rate (CommonItemDropRate) is not set to zero in the T_GS_COMMONITEM table of the MuOnline database.

How do I enable Level 3 Wings (e.g., Cape of Lord) in Season 6?

In the file GameServer/Data/WingEvolution.ini (or equivalent), make sure the line WingLv3Enable=1 is present. In the database, execute: UPDATE MuOnline..T_GS_GSINFO SET WingLv3Enable=1 WHERE ServerCode=1. Restart GameServer after the change.

The Chaos Goblin rejects wing combinations with 'Combination Failed'. How do I fix this?

Check the T_GS_CHAOSMIX table in the MuOnline database. The MixRate field defines the success rate (0-100). Low values cause frequent failures. Execute: UPDATE MuOnline..T_GS_CHAOSMIX SET MixRate=80 WHERE MixType=2 for level 2 wings. Also verify that ingredients (Feather of Condor/Lost Soul) have the correct ItemIndex in the configuration.

Can I add extra options to wings via SQL?

Yes. Wing options are controlled by the T_GS_WINGSOPTION table or the file GameServer/Data/Item/ItemOption.txt depending on server version. To add an extra option via SQL in MuServer S6: UPDATE MuOnline..T_GS_WINGSOPTIONINFO SET MaxOptionCount=4 WHERE WingsType=2. For .ini-based versions, edit the [WingsOption] block in ItemOption.txt by incrementing the MaxOption value.

VI

ViciadosMU Team

Equipe editorial do ViciadosMU — portal de MU Online no ar desde 2003.

Keep reading

Related articles