How to create a MU Online server (complete 2026 guide)

Creating a MU Online private server is a technical project that combines database administration, network configuration, and system administration. This guide explains every component and the process from zero to a running server.

The full MU server stack

WHAT A COMPLETE MU SERVER IS MADE OF:

1. SQL SERVER (the database):
   → Stores: accounts, characters, items, guilds, PK history, event data
   → Every piece of player data lives here
   → Recommended for Season 6: SQL Server 2008 R2
   → WITHOUT this: nothing else works

2. MUSERVER (the game engine):
   → Several executables: ConnectServer, JoinServer, DataServer, GameServer, EventServer
   → These programs run the game world: maps, monsters, drops, combat, events
   → WITHOUT this: there's no game to play

3. GAME CLIENT (what players install):
   → The Main.exe and supporting files that players run on their PCs
   → Must be configured to connect to YOUR server (your IP/hostname)
   → WITHOUT this: players have no way to connect

4. LAUNCHER (optional but recommended):
   → A program players run instead of Main.exe
   → Checks for and downloads updates before starting the game
   → WITHOUT this: distributing patches requires players to manually replace files

5. WEBSITE (optional for private testing, important for public):
   → Account registration, character rankings, news, download page
   → Runs separately from the game (PHP + MySQL on Apache/nginx)
   → WITHOUT this: players must create accounts directly in the database (impractical for public)

Choosing your season

SEASON SELECTION GUIDE:

CLASSIC (0.97 or 0.99):
→ For: nostalgic players, pure PvP, rare-item economy
→ Classes: 4-5 (no Summoner, no Master Level)
→ Setup difficulty: HARDER than S6 due to compatibility issues
→ SQL: SQL Server 2000 (may require a Windows XP VM)
→ Best for: experienced admin targeting nostalgia crowd

SEASON 1:
→ For: slightly more content than classic, still lean
→ Classes: 4-5 with class changes (BK, SM, HE)
→ Events: BC, DS, CC, CS (no Crywolf or Illusion Temple)
→ Setup difficulty: similar to classic, some compatibility needs
→ Best for: "early season" enthusiasts

SEASON 6 (recommended for first servers):
→ For: complete experience, most resources available
→ Classes: ALL 6 (DK, DW, Elf, MG, DL, Summoner)
→ Master Level: yes (200 levels)
→ Events: full set (BC, DS, CC, CS, Crywolf, Kanturu, IT)
→ SQL: SQL Server 2008 R2 (or newer with compatibility level 100)
→ Setup difficulty: MODERATE (most tutorials target S6)
→ Best for: first-time admins

MODERN SEASONS (S7, S9, S10+):
→ For: players who want the most current content
→ More systems: elemental damage, more classes (Rage Fighter in S9+)
→ Setup difficulty: HIGHER (less community documentation)
→ SQL: SQL Server 2014-2019 usually required
→ Best for: experienced admins or teams

Step 1 — Install and configure SQL Server

DATABASE SETUP:

RECOMMENDED FOR S6: SQL Server 2008 R2

CRITICAL INSTALLATION SETTING:
→ Authentication Mode: "Mixed Mode (SQL Server and Windows Authentication)"
→ Set a strong sa password (12+ characters: uppercase, lowercase, numbers, symbols)
→ NEVER install with Windows-only authentication — MuServer uses SQL auth

AFTER INSTALLATION:
1. Install SSMS (SQL Server Management Studio) — free download, separate from SQL
2. Restore the MuServer databases:
   → MuOnline (accounts, characters, guilds, items)
   → EventMU (event data)
   → RankingMU (ranking data)
   → LogServer (game logs)
3. Create a dedicated user: mu_server with db_owner on the 4 databases
4. Enable TCP/IP on port 1433 in SQL Server Configuration Manager
5. Create ODBC DSNs in C:\Windows\SysWOW64\odbcad32.exe (32-bit admin)
6. Test each DSN ("Test Data Source" must say "successful")

SECURITY (non-negotiable):
→ Port 1433 must NOT be open to the internet — SQL Server is internal only
→ The sa password must be strong
→ The mu_server password must be in the .ini files, not sa

Step 2 — Configure MuServer

MUSERVER SETUP:

COMPONENT STARTUP ORDER (must follow this order):
1. SQL Server service (already running as Windows service)
2. DataServer.exe — establishes the DB bridge
3. JoinServer.exe — handles account authentication
4. ConnectServer.exe — receives player connections (port 44405)
5. GameServer.exe — the game world (port 55901)
6. EventServer.exe — event management

CONFIGURE EACH COMPONENT:
→ DataServer: set ODBC DSN name, SQL user and password
→ JoinServer: set SQL connection, ConnectServer address
→ ConnectServer: set listening IP (0.0.0.0 for all interfaces), port 44405
→ GameServer: set all rates, IP, port, DataServer address

KEY RATE SETTINGS IN GAMESERVER.INI:
EXPMultiplier = 100      ← 100x experience (adjust to taste)
DropMultiplier = 100     ← 100x drop rate
ZenMultiplier = 50       ← 50x zen drop
ResetLevel = 400         ← level at which reset becomes available (S6 cap)
MLExpMultiplier = 50     ← Master Level EXP rate

FOR S6 SPECIFICALLY:
→ Enable all 6 classes
→ Configure all S6 events (BC, DS, CC, CS, Crywolf, Kanturu, IT)
→ Set Master Level limits (MaxML = 200)
→ MG has NO 1st or 2nd quest — only 3rd quest to become Duel Master

Step 3 — Configure the client

EDITING THE GAME CLIENT:

WHAT TO CONFIGURE IN THE CLIENT:
→ ConnectServer IP: the address the client connects to first
→ ConnectServer port: usually 44405 (must match GameServer.ini)
→ Game window title (optional): often has server name
→ Resolution settings: in Main.ini or setup dialog

HOW TO FIND WHERE THE IP IS STORED:
→ Look for these files in the client folder:
   IP.txt, server.ini, connect.ini, Server.txt
   → If found: edit the file in Notepad — change the IP to yours
→ If no config file: the IP is hex-edited into Main.exe
   → Use HxD (free hex editor)
   → Search for an IP-like string (e.g., "game.oldserver.com" or "192.168.x.x")
   → Replace with your IP or hostname (same byte length — pad with spaces if shorter)

FOR LOCAL TESTING:
→ Set IP to: 127.0.0.1 — connects to your own PC without network

FOR ONLINE PLAY:
→ Set IP to: your VPS's public IP, OR your home public IP (if home server), OR your No-IP hostname

Step 4 — Network configuration

MAKING THE SERVER ACCESSIBLE ONLINE:

FOR HOME SERVERS (PC with home internet):
→ YOU HAVE A DYNAMIC IP: it changes periodically
   → Solution: No-IP free account → create a hostname (yourserver.ddns.net)
   → Install No-IP DUC (Dynamic Update Client) → keeps hostname pointing to your current IP
   → Use the hostname in the game client instead of the raw IP

→ PORT FORWARDING: required so players outside your network can connect
   → Log into your router (usually 192.168.1.1 or 192.168.0.1)
   → Port Forwarding section
   → Add: TCP 44405 → to your PC's local IP (find with: ipconfig → IPv4 Address)
   → Add: TCP 55901 → to your PC's local IP
   → Save and apply

→ CGNAT PROBLEM: some ISPs use carrier-grade NAT — port forwarding won't work
   → Test: if your router's WAN IP starts with 10.x or 100.x, you have CGNAT
   → Solution: ask ISP to remove CGNAT, OR use a VPS instead of home internet

FOR VPS SERVERS:
→ The VPS has a public IP by default — no port forwarding needed
→ Configure Windows Firewall: open TCP 44405 and TCP 55901 inbound
→ The VPS provider's control panel may also have a separate firewall — allow these ports there too

Step 5 — Security before going public

SECURITY CHECKLIST — REQUIRED BEFORE OPENING TO PLAYERS:

DATABASE:
☐ sa password is strong (not "sa", not "123456", not blank)
☐ TCP 1433 is NOT reachable from the internet (internal only)
☐ MuServer configs use mu_server user, not sa
☐ Automated backup is configured (see backup tutorial)

GAME SERVER:
☐ Anti-hack is enabled in GameServer.ini
☐ GM accounts use strong passwords (not "admin123")
☐ GM accounts are CtlCode = 1 in MEMB_INFO table (admin level)

OPERATING SYSTEM (for VPS):
☐ Administrator password is strong (16+ characters)
☐ RDP port changed from 3389 to a non-standard port
☐ RDP access restricted to your admin IP only

WEBSITE:
☐ Admin panel password is strong and unique
☐ phpMyAdmin is not publicly accessible
☐ Registration requires a working email (no throwaway email creation)

Most common first-server mistakes

AVOID THESE ERRORS:

1. OPENING THE SERVER BEFORE TESTING LOCALLY:
   → Always connect locally first (127.0.0.1)
   → Validate: login, character creation, items, saves — BEFORE allowing players in

2. USING sa AS THE MUSERVER DATABASE USER:
   → Create a dedicated mu_server user
   → sa in .ini files is a security risk

3. NOT SETTING UP BACKUPS:
   → Player data loss without backups is permanent
   → Automate SQL Server backups on day 1
   → Test that the backup can be restored before needing it

4. STARTING THE SERVER WITH GAMESERVER BEFORE DATASERVER:
   → Wrong startup order causes GameServer to close instantly
   → Order: SQL Server → DataServer → JoinServer → ConnectServer → GameServer

5. PORT FORWARDING THE WRONG PORT:
   → Forwarding 1433 (SQL) to the internet is a major security error
   → Only forward 44405 (ConnectServer) and 55901 (GameServer) to the internet

6. CLIENT AND SERVER VERSION MISMATCH:
   → An S6 Ep.2 client with an Ep.3 server = connection problems
   → Verify the distribution and client are from the same source and compatible

7. EXTREME RATES FROM DAY ONE:
   → Starting at EXP 9999x / Drop 9999x depletes all content in days
   → Players leave when they've done everything and there's nothing left
   → Moderate rates (100x-500x for S6) build a longer-lasting server

Continue with the Season 6 server tutorial (the most recommended path for first-time admins), the SQL Server 2008 R2 installation tutorial (the first step in the recommended stack), the MuServer configuration tutorial (detailed .ini walkthrough), and the security tutorial (hardening the server before opening to players).

Frequently asked questions