How to create a MU Online Season 1 server

Season 1 represents the beginning of the seasonal MU Online era — more organized than classic, but still lean and focused compared to the later, feature-heavy seasons.

What Season 1 is (and isn't)

SEASON 1 IN CONTEXT:

POSITION IN MU ONLINE HISTORY:
→ Released after 0.97/0.99 classic versions
→ Formalized the "season" update cycle
→ More polished than classic, less content than S4-S6

WHAT S1 HAS THAT CLASSIC (0.97/0.99) DOESN'T:
→ More formal class evolution quest system
→ More organized Blood Castle levels and event timing
→ Better guild mechanics and guild wars
→ Slightly improved item balance
→ Chaos Castle and Castle Siege (if not already in your 0.99 build)

WHAT S1 DOESN'T HAVE (compared to S6):
→ No Master Level — no post-cap progression (ML came in S4)
→ No Summoner class — Summoner arrives in S4
→ No elements (Fire/Water/Earth/Wind) — those come in S8+
→ No Illusion Temple, no Crywolf (S6 features)
→ No Wing Level 3 (Loch's Feather, JoCreation don't exist)
→ No Rage Fighter (added in S9)
→ Kanturu event may not be present depending on distribution

5 CLASSES IN SEASON 1:
→ Dark Knight → Blade Knight (→ no 3rd class in S1)
→ Dark Wizard → Soul Master (→ no 3rd class in S1)
→ Fairy Elf → Muse Elf (→ no 3rd class in S1)
→ Magic Gladiator → Duel Master (NO 1st or 2nd quest — only 3rd quest)
→ Dark Lord → Lord Emperor (uses Command stat)

Compatibility requirements

S1 COMPATIBILITY MATRIX:

SQL SERVER:
→ SQL Server 2000 SP4: if the distribution says "SQL 2000" (most common for S1)
→ SQL Server 2008 R2: may work if the distribution explicitly supports it
→ SQL Server 2014+: unlikely to work without stored procedure rewrites
→ Check the readme first — always follow the distribution's recommendation

WINDOWS:
→ Windows XP SP3 / Server 2003 SP2: most compatible for SQL 2000-era distributions
→ Windows Server 2008 R2: generally works for S1 if SQL 2008 R2 is used
→ Windows 10/11: SQL Server 2000 cannot be installed directly — needs a VM
→ Windows Server 2019: works if using SQL 2008 R2 with S1 compatibility level adjustments

THE VIRTUAL MACHINE APPROACH FOR S1 WITH SQL 2000:
→ Host: Windows 10/11 (your PC or a VPS provider that supports nested virtualization)
→ VM (VirtualBox/VMware): Windows XP SP3 or Server 2003 SP2
→ Inside VM: SQL Server 2000 SP4 + S1 MuServer
→ Port forward from host to VM: TCP 44405, TCP 55901
→ Players connect to the host's public IP → forwarded into the VM's MuServer

WHY THIS WORKS:
→ SQL Server 2000 and old S1 MuServer DLLs are native to XP/2003 environment
→ No compatibility shim needed — everything works as intended
→ The host machine handles the internet; the VM handles the game

SQL Server 2000 SP4 setup for Season 1

SQL 2000 INSTALLATION (inside Windows XP/Server 2003 VM):

DOWNLOAD WHAT YOU NEED:
→ SQL Server 2000 (Standard or Enterprise Edition)
→ SQL Server 2000 SP4 (mandatory — install immediately after SQL 2000)

INSTALLATION PROCEDURE:
1. Run SQL Server 2000 installer as Administrator
2. Local Computer installation
3. Server and Client Tools (full install)
4. Authentication: "Mixed Mode" — MANDATORY for MuServer
5. sa password: strong, written down
6. Complete installation

IMMEDIATELY AFTER: INSTALL SP4:
1. Run SP4 installer
2. Restart when prompted
3. Verify: Open Query Analyzer → SELECT @@VERSION
   → Must show: "8.00.2039" (SP4 build number)
   → If it shows 8.00.194 (RTM) or any other: SP4 didn't apply — retry

RESTORE THE S1 DATABASE:
→ Enterprise Manager → right-click Databases → All Tasks → Restore Database
→ From device → add the .bak file → OK
→ Common databases: MuOnline (main), possibly EventMU (if separate)
→ Some S1 distributions use a single database for all game data

ENABLE TCP/IP:
→ SQL Server Network Utility (from Start menu)
→ Check "TCP/IP" is listed under enabled protocols
→ Port: 1433 (or check the distribution's readme)
→ Restart SQL Server service after enabling

MuServer configuration for Season 1

S1-SPECIFIC CONFIGURATION:

COMPONENT STRUCTURE (may differ from S6):
→ Some S1 distributions use fewer components than S6 (no separate DataServer)
→ Check what executables the distribution includes
→ Common S1 structure: ConnectServer + JoinServer + GameServer
→ Some S1 builds combine DataServer functionality into GameServer

DATABASE CONNECTION:
→ In GameServer.ini or the equivalent:
   DBServer = 127.0.0.1     ← SQL Server address (localhost)
   DBName = MuOnline         ← database name
   DBUserId = sa             ← or a dedicated user
   DBPassword = [sa_password] ← the sa password you set

PORTS:
→ ConnectServer: TCP 44405 (verify in ConnectServer.ini)
→ GameServer: TCP 55901 (verify in GameServer.ini)
→ These are the only ports players need to reach

STARTUP ORDER:
1. SQL Server service (running in Windows XP/2003 VM)
2. JoinServer.exe
3. ConnectServer.exe
4. GameServer.exe

S1-SPECIFIC RATES:
EXPMultiplier = 50          ← moderate for S1 (some admins prefer 10x for nostalgia)
DropMultiplier = 30         ← items should feel rewarding but not trivial
ZenMultiplier = 20          ← zen economy matters in S1

EVENTS TO ENABLE IN S1:
→ BloodCastle: Enable = 1 (all 7 levels)
→ DevilSquare: Enable = 1 (all 7 levels)
→ ChaosCastle: Enable = 1 (all 7 levels)
→ CastleSiege: Enable = 1 (weekly event)
→ Kanturu: may not be present in S1 distributions
→ Illusion Temple: NOT in S1 (S6 feature)

Season 1 rate philosophy

RECOMMENDED APPROACH FOR S1 SERVERS:

THE S1 PLAYER BASE:
→ Players choosing S1 over S6 often want a semi-classic experience
→ They want class evolutions (unlike 0.97) but without the Master Level grind
→ The lack of post-cap progression means endgame content is: PvP, Castle Siege, economy

RATES BY PLAYER EXPECTATION:
LOW RATES (nostalgia-focused):
→ EXP: 5x-20x | Drop: 5x-15x
→ Reaching max level takes weeks
→ Item values are high (rare items are genuinely rare)
→ PvP has weight: items drop on death (classic PK rules)
→ Player retention: low initial, but very loyal community

MEDIUM RATES (popular choice):
→ EXP: 50x-200x | Drop: 30x-100x
→ Reaching max level takes days to 1-2 weeks
→ More accessible than low rates
→ Larger potential player base

HIGH RATES (S1 is the skin, not the soul):
→ EXP 500x+: everyone hits cap in hours
→ The S1 content is gone before the server gets its first week
→ Not recommended — if you want fast rates, use S6 (more content to burn through)

RESET RECOMMENDATION:
→ S1 doesn't have Master Level
→ After reaching the level cap, there's no post-cap progression
→ Resets can give players something to do, but risk making the character progression meaningless
→ If resets: keep bonuses small and max resets reasonable (5-10 max)

Client configuration for Season 1

S1 CLIENT CONFIGURATION:

FINDING THE S1 CLIENT:
→ The S1 client must match the server's S1 version exactly
→ Using an S6 client with an S1 server = connection incompatibility
→ The client typically displays "Season 1" or shows an older main screen UI

EDITING THE CONNECTION ADDRESS:
→ S1 clients often use a config file: IP.txt, server.ini, or connect.ini
→ Edit the IP to your server's address (127.0.0.1 for local test)
→ If no config file: hex edit Main.exe (same process as classic)

COMPATIBILITY ON MODERN WINDOWS:
→ Right-click Main.exe → Properties → Compatibility
→ "Windows XP (Service Pack 3)" compatibility mode
→ "Run as administrator"
→ Install dependencies if client doesn't start:
   → Visual C++ 2005 Redistributable (x86)
   → DirectX End-User Runtime (DirectX 8/9 components)

DISTRIBUTING THE CLIENT TO PLAYERS:
→ Package the entire client folder as a .zip
→ Include a README with instructions to run Main.exe as Administrator
→ A launcher that auto-patches is more player-friendly
→ Host on a file sharing service or your own web server

Continue with the "How to create a MU Online server" general tutorial (the conceptual foundation this guide builds on), the SQL Server 2000 installation tutorial (for S1 distributions requiring SQL 2000), the "Windows or Linux" tutorial (covers the virtual machine approach for running old distributions), and the Season 6 tutorial (if you decide S6 is a better fit after reading about S1's limitations).

Frequently asked questions