How to create a classic MU Online server (0.97/0.99)

Classic MU Online servers (0.97 and 0.99) serve a dedicated nostalgic player base who want the original experience: 4 classes, simple maps, rare items, and PvP where every fight counts.

Classic vs Season 6: what changes

CLASSIC (0.97/0.99) VS SEASON 6 COMPARISON:

CLASSES:
→ 0.97: Dark Knight, Dark Wizard, Fairy Elf + MG (limited availability by distribution)
→ 0.99: Dark Knight, Dark Wizard, Fairy Elf, Magic Gladiator, Dark Lord
→ S6:   All 6 classes including Summoner
→ No class changes (BK, SM, HE) in the very earliest 0.97 builds

MAPS:
→ Classic: Lorencia, Noria, Devias, Dungeon, Lost Tower, Atlans, Tarkan
→ Classic does NOT have: Kalima, Kanturu, Raklion, Crywolf maps
→ S6 has all of the above plus others

EVENTS:
→ 0.97: Blood Castle, Devil Square
→ 0.99: Blood Castle, Devil Square, Chaos Castle, Castle Siege
→ S6:   All of the above + Crywolf, Kanturu, Illusion Temple

SYSTEMS ABSENT IN CLASSIC:
→ No Master Level
→ No Elements (Fire, Water, Earth, Wind)
→ No Wing Level 3 (Loch's Feather, JoCreation don't exist in classic context)
→ No Rage Fighter, no Summoner
→ No Chaos Machine beyond basic combinations in 0.97

WHAT MAKES CLASSIC UNIQUE:
→ Simpler, more focused experience
→ Items feel rare (fewer item types, limited crafting)
→ PvP kills have weight (PK system was harsher in classic)
→ Community-driven economy (basic item shop, player trading dominates)

Compatibility challenges and the VM solution

THE COMPATIBILITY PROBLEM:

WHY CLASSIC DOESN'T JUST WORK ON MODERN WINDOWS:
→ Classic MuServer files are compiled for Windows 2000/XP era
→ They depend on DLLs that Windows 10/11 removed or changed
→ SQL Server 2000 doesn't install on Windows 8+ (setup fails during compatibility check)
→ Some 0.97 executables have hardcoded assumptions about memory addresses
   that differ on modern Windows (causes crashes)

THE VIRTUAL MACHINE SOLUTION:
→ Install VirtualBox or VMware Workstation Player (both free) on your Windows 10/11 host
→ Create a virtual machine with Windows XP SP3 or Windows Server 2003 SP2
   (ISO images for these can be found through Microsoft's MSDN archive or other sources)
→ Run MuServer AND SQL Server 2000 inside the VM
→ The host handles internet connectivity; the VM handles the game server

VM CONFIGURATION:
→ RAM for VM: 512 MB - 1 GB (XP runs fine with 512 MB; Server 2003 needs 512 MB)
→ Disk: 20-40 GB virtual disk
→ Network: NAT or Bridged (Bridged lets the VM get its own IP on the local network)
→ Port forwarding: in VirtualBox, forward host ports 44405 and 55901 to the VM's same ports

SIMPLER ALTERNATIVE (if available):
→ Some VPS providers still offer Windows Server 2003 options
→ Ask before renting: "Do you offer Windows Server 2003 VPS?"
→ Running a WS2003 VPS natively avoids the VM overhead

SQL Server 2000 setup

SQL SERVER 2000 FOR CLASSIC MU:

DOWNLOAD AND VERSION:
→ SQL Server 2000 + Service Pack 4 are both required
→ SP4 is mandatory — it contains critical security and stability patches
→ Install order: SQL Server 2000 Enterprise → then SP4 (standalone installer)
→ After SP4: in SQL Query Analyzer: SELECT @@VERSION
   → Should show: 8.00.2039 (RTM.2039 = SP4)

INSTALLATION (inside Windows XP/Server 2003 VM):
1. Run SQL Server 2000 setup as Administrator
2. Instance name: leave as default (MSSQLSERVER)
3. Authentication: Mixed Mode (sa + Windows) — MANDATORY
4. sa password: set a strong one, write it down
5. After install: apply SP4 immediately before anything else

TOOLS IN SQL 2000:
→ Enterprise Manager: the graphical database manager (equivalent to SSMS in newer versions)
→ Query Analyzer: the query execution tool (equivalent to SSMS query window)
→ Both are installed with SQL 2000 and accessible from Start menu

RESTORE THE CLASSIC DATABASE:
→ Enterprise Manager → right-click Databases → All Tasks → Restore Database
→ From device → point to the .bak file → OK
→ Or use Query Analyzer:
   RESTORE DATABASE MuOnline FROM DISK = 'C:\path\to\MuOnline.bak' WITH REPLACE;

ENABLE TCP/IP:
→ SQL Server Network Utility (from Start menu)
→ Enable TCP/IP → port 1433 (or the port your distribution specifies)
→ Restart SQL Server service

Classic MuServer configuration

CONFIGURING THE CLASSIC MUSERVER:

COMPONENTS (simpler than S6):
→ ConnectServer: same role — receives initial connection
→ GameServer: all game logic (classic had fewer separate components)
→ DataServer: may be integrated differently depending on the distribution

KEY CONFIG DIFFERENCES FROM S6:
→ Port configuration: 44405 for ConnectServer, typically 55901 for GameServer
   but some classic distributions use different defaults — check the .ini files
→ Event configuration: 0.97 only has BC and DS; 0.99 adds CC and CS
→ Class configuration: only 4-5 classes, no Summoner section
→ No Master Level settings (ML doesn't exist in classic)
→ Wing crafting: basic Chaos Machine combinations only in 0.97

RATE CONFIGURATION FOR CLASSIC:
EXPMultiplier = 10        ← 10x is a good starting point for classic
DropMultiplier = 10       ← keep drops meaningful but not trivial
ZenMultiplier = 5         ← classic zen economy is important
ResetLevel = 0            ← set to 0 or disable (no resets in true classic)

EVENTS IN 0.99:
[BloodCastle]
Enable = 1
Schedule = every 2 hours  ← specific parameter depends on distribution

[ChaossCastle]
Enable = 1

[CastleSiege]
Enable = 1
Day = Saturday            ← classic CS was originally one specific day per week

Classic server philosophy and rates

THE CLASSIC EXPERIENCE: RATES AND DESIGN PRINCIPLES:

WHY LOW RATES MATTER FOR CLASSIC:
→ In a classic server, items are meant to be rare and meaningful
→ A player finding their first Ancient item after 2 weeks of farming = memorable
→ A player finding Ancient items in the first hour = boring, then they leave

RECOMMENDED RATES:
EXP: 3x to 50x
→ 3x: very classic, Lorencia feels dangerous at low level (true nostalgia crowd)
→ 10x-20x: good balance (popular classic servers cluster here)
→ 50x: still "classic feel" but faster access to later content

Drop: 5x to 20x
→ Items should feel rare — a full set of +9/+11 items is a long-term goal
→ High drop rates devalue item trading and the player economy
→ A meaningful drop rate makes item trading (between players) the primary economy

Resets: strongly consider disabling
→ Resets in classic break the experience — a resetter has meaningless stats
→ The level cap in classic is lower; reaching it is a genuine achievement
→ If you must have resets: limit to 1-2 max with minimal bonuses

PK SYSTEM:
→ In classic, PK (player killing) had real consequences (items drop on death)
→ Enable classic PK rules for authenticity
→ This creates the tense PvP the classic community values

Client configuration for classic

CLASSIC CLIENT EDITING:

FINDING THE CONNECTION IP:
→ Classic clients store the ConnectServer address differently than S6 clients
→ Common locations:
   → IP.txt or server.txt in the client folder (plain text — easiest to edit)
   → Hex-edited into Main.exe (less common in very old versions)

HEX EDITING CLASSIC MAIN.EXE:
→ If no IP.txt exists, use HxD (free hex editor)
→ Search for the old IP or "127.0.0.1" in the hex
→ Replace with your actual IP (same byte length — classic clients have the same constraint)

CLIENT COMPATIBILITY:
→ The classic client is also 15-20 years old
→ May require DirectX 8 (install DirectX End-User Runtime)
→ Visual C++ 2005 redistributable (32-bit, even on 64-bit Windows)
→ On Windows 10/11: run as Administrator + Windows XP SP3 compatibility mode

RUNNING THE CLIENT ON MODERN WINDOWS:
1. Right-click Main.exe → Properties → Compatibility
2. "Run this program in compatibility mode for: Windows XP (Service Pack 3)"
3. "Run this program as an administrator"
4. Apply → OK
→ Try launching — most classic clients work with these settings on modern Windows

Continue with the SQL Server 2000 installation tutorial (specific guide for the classic-server database), the "Windows or Linux for a MU server" tutorial (covering the VM approach for running old software), and the Season 1 server tutorial (for players wanting the season era but still early in the game's history).

Frequently asked questions