How to Create a Modern MU Online Server (S13+) — Overview Guide

Understanding the Modern MU Server Architecture

Season 13 and later seasons of MU Online introduced layered system complexity that did not exist in classic emulators. Before writing a single configuration file, you need to understand the multi-process architecture that all modern private server projects share.

A typical Season 13+ server stack consists of at least four separate processes:

• ConnectServer — the entry point. Every client connection arrives here first. It resolves which GameServer channel the client should join and redirects accordingly.
• GameServer — the core process. Handles all in-game logic: character movement, combat, items, events, quests, and map instances.
• DataServer — the bridge between GameServer and the SQL database. All character reads and writes go through this layer.
• EventChipServer / JoinServer — optional but often required by newer season packages. These handle multi-channel coordination and event-instance queues.

Understanding this flow is essential: if ConnectServer is offline, players cannot log in regardless of whether GameServer is running perfectly.

Server Hardware and Operating System Requirements

Minimum Specifications for a Development Server

For local development and testing, the following baseline is workable:

• CPU: 4-core processor at 2.5 GHz or higher
• RAM: 8 GB (4 GB for OS + processes, 4 GB headroom for SQL Server)
• Storage: 60 GB SSD (OS) + 30 GB HDD (database and logs)
• Network: 100 Mbps symmetric — sufficient for up to ~50 concurrent players in testing

Production Considerations

For a server you intend to open publicly, storage I/O becomes the primary bottleneck. SQL Server performance degrades sharply on spinning disks when character saves spike during large events like Castle Siege or Blood Castle. Place your database data files and log files on separate SSD volumes whenever possible.

> [!WARNING] > Do not use the same machine to host your web panel, SQL Server, and all GameServer processes in production without a performance baseline. Run stress tests with simulated concurrent logins before opening. Unexpected auto-saves during peak hours can spike CPU to 100% and disconnect all players simultaneously.

Operating system: Windows Server 2019 Standard (64-bit) is the recommended baseline. Enable only the roles you need — at minimum: .NET Framework 3.5 and 4.8 (many emulators depend on both), DirectX runtime (some GameServer builds reference it), and Windows Firewall with the correct port exceptions.

Database Installation and Schema Initialization

All modern MU emulators store account, character, item, and guild data in Microsoft SQL Server. The setup order matters.

Install SQL Server before extracting any server files. Create a dedicated SQL login (avoid using sa for daily operations):

-- Create a dedicated database login for the server processes
-- Replace <PASSWORD> with a strong random string (min 16 chars)

CREATE LOGIN MuServerUser WITH PASSWORD = '<PASSWORD>';
GO

-- After the emulator has created the MuOnline database:
USE MuOnline;
GO

CREATE USER MuServerUser FOR LOGIN MuServerUser;
GO

-- Grant the minimum permissions required
EXEC sp_addrolemember 'db_datareader', 'MuServerUser';
EXEC sp_addrolemember 'db_datawriter', 'MuServerUser';
EXEC sp_addrolemember 'db_ddladmin',   'MuServerUser';  -- needed for schema migration scripts
GO

-- Verify effective permissions
SELECT dp.name AS principal, p.permission_name, p.state_desc
FROM sys.database_permissions p
JOIN sys.database_principals dp ON p.grantee_principal_id = dp.principal_id
WHERE dp.name = 'MuServerUser';

After SQL Server is configured, run the emulator's schema scripts in the order documented by the project. Modern packages typically ship three script categories:

1. create_tables.sql → base schema
2. stored_procedures.sql → all SP definitions used by DataServer
3. default_data.sql → NPC positions, shop items, monster spawns

Run each in order within a single database session. If any script fails midway, drop the database and restart from a clean state rather than attempting partial repairs.

ConnectServer and Network Configuration

The ConnectServer configuration file (commonly ConnectServer.ini or CSConfig.xml depending on the emulator project) controls which GameServer channels are advertised to clients and on which IP/port the entry point listens.

Key parameters to set correctly:

[Network]
ListenIP        → 0.0.0.0          ; bind to all interfaces, or specify one NIC
ListenPort      → 44405            ; default CS port — must match client's connect.ini
MaxConnections  → 10000            ; cap simultaneous TCP connections

[ServerList]
; Each entry registers one GameServer channel
; Format: ChannelID → PublicIP:GameServerPort → DisplayName → MaxPlayers
Server00 → 203.0.113.10:55901 → Lorencia #1 → 1000
Server01 → 203.0.113.10:55902 → Lorencia #2 → 1000

[Timeouts]
LoginTimeout    → 30               ; seconds before an idle login attempt is dropped
HeartbeatInterval → 10            ; CS↔GS keepalive interval in seconds

> [!TIP] > During local testing, replace the PublicIP values with 127.0.0.1. When moving to a VPS or dedicated machine, switch to the actual public IPv4 address. Never use a private 192.168.x.x address in the ServerList if players will be connecting from outside your LAN — the client will attempt to connect directly to that IP and fail.

Open the following ports in Windows Firewall for both inbound TCP rules:

• 44405 — ConnectServer client listener
• 55901–55910 — GameServer channels (one per channel you run)
• 1433 — SQL Server (loopback only; never expose this port to the internet)

GameServer Core Configuration

The GameServer configuration is the most expansive part of any modern emulator setup. Modern Season 13+ packages split settings across multiple files organized by subsystem. Common file layout:

GameServer/
  Config/
    GameServerInfo.ini   → server identity, DB credentials, port bindings
    GameOptions.ini      → rates (EXP, drop, Zen), reset system, PK settings
    ItemBag.ini          → drop table overrides
    Events/
      BloodCastle.ini
      ChaosCastle.ini
      CastleSiege.ini
      IllusionTemple.ini
    MasterSystem.ini     → Master Level skill tree unlock rules
    RuudSystem.ini       → Season 12+ Ruud currency rates

The most impactful settings for a new server operator are inside GameOptions.ini:

[ExpSystem]
BaseExpRate        → 30x           ; multiplier applied to all EXP gain
MasterExpRate      → 10x           ; separate rate for Master Level EXP
PartyExpBonus      → 1.2           ; 20% bonus when in a party

[DropSystem]
BaseDropRate       → 40            ; percent chance an eligible monster drops anything
ExcellentItemRate  → 15            ; percent of drops that are excellent-option items
AncientItemRate    → 3             ; percent of drops that are ancient set items
JewelDropRate      → 25            ; percent of drops that are jewels

[ResetSystem]
EnableResets       → 1
MaxResets          → 100
ResetLevel         → 400           ; character must reach this level to reset
ResetRequireStats  → 0             ; 1 = require max stats before reset allowed
StatPointsPerReset → 500          ; bonus stat points awarded on each reset

Master Level and Season-Specific Systems

Season 13 introduced significant structural changes to the Master Level system that differ substantially from Season 9 configurations. The ML skill tree in S13+ is class-specific and references skill IDs that do not exist in older databases. If you are migrating a database from an older season, missing ML skill entries will cause GameServer to crash on character load.

Verify the following before opening your server:

1. All character classes present in your database have corresponding entries in the Master Level skill tree table (T_ML_SkillTree or equivalent).
2. The MasterSystem.ini MaxMasterLevel value matches what your client UI was compiled to display — a mismatch causes the client to show incorrect ML point caps.
3. The Ruud shop NPC positions are correctly defined in your spawn table. Missing NPC entries do not crash the server but leave players unable to spend Ruud currency, which is a core Season 12+ progression mechanic.

Post-Installation Checklist and First Boot

Before starting all processes for the first time, work through this checklist:

• SQL Server service is running and the MuOnline database is fully initialized
• MuServerUser login can connect using the same credentials written in GameServerInfo.ini
• Windows Firewall rules are in place for all required ports
• ConnectServer ServerList entries point to the correct IP (127.0.0.1 for local testing)
• GameOptions.ini rates are set to test-friendly values (high EXP, high drop) so you can verify gameplay systems quickly
• At least one GM account exists in the database (AccountCharacter table, Authority column set to the GM flag value for your emulator)

Start processes in order: DataServer first → GameServer → ConnectServer. Each process should print a "listening" or "ready" status line within 10–20 seconds. If GameServer exits immediately after start, the most common causes are a failed SQL connection (wrong credentials or port) or a missing stored procedure (schema script ran incompletely).

Once all three are running, launch the game client, point it at your ConnectServer IP, create a test account, and verify that character creation, basic movement, and item pickup all function before adjusting any further configuration.

Perguntas frequentes