How to Create and Configure MU Online Season 4 Server

Prerequisites

Before starting, make sure your machine or VPS meets the minimum requirements and that all required software is installed.

Hardware requirements:

• Windows Server 2008/2012 or Windows 7/10 (64-bit)
• Minimum 4 GB RAM (8 GB recommended)
• 20 GB disk space
• Stable network connection with a fixed IP or configured DDNS

Required software:

• SQL Server 2008 R2 (Express edition is sufficient for testing)
• SQL Server Management Studio (SSMS)
• MuServer Season 4 package (server files)
• Visual C++ Redistributable 2005/2008 (x86)
• .NET Framework 3.5

Step 1 — Install and prepare SQL Server

1.1 Install SQL Server 2008 R2 with default settings. During setup, select Mixed Mode Authentication (SQL Server and Windows) and set a strong password for the sa account.

1.2 After installation, open SQL Server Configuration Manager and ensure the SQL Server (MSSQLSERVER) service is running and set to start automatically.

1.3 Allow TCP port 1433 through the Windows Firewall:

netsh advfirewall firewall add rule name="SQL Server" protocol=TCP dir=in localport=1433 action=allow

1.4 In SSMS, create the main server database:

CREATE DATABASE MuOnline
COLLATE Latin1_General_CI_AS;
GO

USE MuOnline;
GO

1.5 Run the table creation script included in the MuServer package. It is typically located at Setup/SQL/CreateTables_MuOnline.sql. In SSMS: File → Open → run the script against the MuOnline database.

1.6 Create a dedicated SQL login for the server:

USE master;
GO
CREATE LOGIN muserver_user WITH PASSWORD = 'YourStrongPassword123!';
GO

USE MuOnline;
GO
CREATE USER muserver_user FOR LOGIN muserver_user;
GO
EXEC sp_addrolemember 'db_owner', 'muserver_user';
GO

Step 2 — Server directory structure

Extract the MuServer package to a dedicated directory, preferably at the root of a drive (e.g., D:\MuServer\). The standard Season 4 layout is:

D:\MuServer\
├── ConnectServer\
│   ├── ConnectServer.exe
│   └── ConnectServer.cfg
├── DataServer\
│   ├── DataServer.exe
│   └── DataServer.cfg
├── GameServer\
│   ├── GameServer.exe
│   ├── GameServer.cfg
│   └── Data\
│       ├── Events\
│       ├── Monster\
│       └── Maps\
└── EventServer\
    ├── EventServer.exe
    └── EventServer.cfg

Step 3 — Configure DataServer

DataServer is the bridge between GameServer and SQL Server. All database communication passes through it.

3.1 Open DataServer/DataServer.cfg and configure:

[DataServer]
ServerAddr = 127.0.0.1
ServerPort = 55557
MaxUser    = 500

[DBConfig]
DSN        = MuOnline
ID         = muserver_user
PWD        = YourStrongPassword123!
DBServer   = 127.0.0.1
DBName     = MuOnline

3.2 Set up the ODBC DSN. Open Administrative Tools → ODBC Data Sources (32-bit) and create a new System DSN:

• Driver: SQL Server
• Name: MuOnline
• Server: 127.0.0.1
• SQL Authentication: user muserver_user

Step 4 — Configure GameServer

4.1 Open GameServer/GameServer.cfg and adjust the main parameters:

[GameServer]
ServerCode    = 0
ServerName    = MyServer
ServerPort    = 55901
MaxUser       = 500
DataServerIP  = 127.0.0.1
DataServerPort= 55557

[Info]
ServerGroup   = 0
Priority      = Normal

4.2 Set experience and drop rates in the same file:

[Rate]
ExpRate       = 50
MasterExpRate = 30
ZenRate       = 5
DropRate      = 3

4.3 Configure level experience values in GameServer/Data/ExpTable.cfg. The file contains one EXP value per line, corresponding to levels 1 through the configured maximum.

Step 5 — Configure ConnectServer

ConnectServer is the client entry point. It directs players to the correct GameServer.

5.1 Edit ConnectServer/ConnectServer.cfg:

[ConnectServer]
ListenPort    = 44405
MaxUser       = 1000
ServerIP      = 0.0.0.0

[GameServer0]
ServerCode    = 0
ServerIP      = YOUR_PUBLIC_IP
ServerPort    = 55901
ServerName    = MyServer

Replace YOUR_PUBLIC_IP with the external IP address of your machine or VPS.

Step 6 — Configure main events

6.1 Blood Castle — Edit GameServer/Data/Events/BCSchedule.ini:

[BloodCastle]
Enable    = 1
Schedule1 = 00:00
Schedule2 = 02:00
Schedule3 = 04:00
Schedule4 = 06:00
Schedule5 = 08:00
Schedule6 = 10:00
Schedule7 = 12:00
Schedule8 = 14:00
Schedule9 = 16:00
Schedule10= 18:00
Schedule11= 20:00
Schedule12= 22:00

6.2 Devil Square — Edit GameServer/Data/Events/DSSchedule.ini using the same schedule format.

6.3 To enable Chaos Castle, update the event schedule table in the database:

USE MuOnline;
UPDATE EventSchedule
SET IsEnabled = 1
WHERE EventType = 'Chaoscastle';

Step 7 — Service startup order

Always start servers in this order to avoid connection errors:

DataServer → EventServer → GameServer → ConnectServer

Create a StartServer.bat file in the MuServer root to automate this:

@echo off
cd /d D:\MuServer\DataServer
start "" DataServer.exe
timeout /t 5 /nobreak > nul

cd /d D:\MuServer\EventServer
start "" EventServer.exe
timeout /t 3 /nobreak > nul

cd /d D:\MuServer\GameServer
start "" GameServer.exe
timeout /t 5 /nobreak > nul

cd /d D:\MuServer\ConnectServer
start "" ConnectServer.exe

echo All services started.
pause

Step 8 — Create a GM account and test login

8.1 Insert an admin account directly into the database:

USE MuOnline;
INSERT INTO MEMB_INFO (memb___id, memb__pwd, memb_name, mail_addr, bloc_code, ctl_code)
VALUES ('admin', '1234', 'Administrator', '[email protected]', 0, 1);

8.2 In the MU Online Season 4 client, configure main.exe or edit the connection file to point to the ConnectServer IP on port 44405.

Common Troubleshooting

GameServer closes immediately on launch: Check GameServer/Log/GameServer.log. The most common cause is a failed connection to DataServer — confirm DataServer is running and that port 55557 is reachable.

Players cannot log in: Run the following query to verify the account exists and is not blocked:

SELECT memb___id, bloc_code, ctl_code FROM MEMB_INFO WHERE memb___id = 'accountName';

If bloc_code = 1, the account is blocked. Unblock it with:

UPDATE MEMB_INFO SET bloc_code = 0 WHERE memb___id = 'accountName';

Monsters do not spawn on the map: Verify that .att and .obj files for each map are present in GameServer/Data/Maps/. Missing or corrupted map files prevent monster spawning entirely.

Perguntas frequentes