Start, stop and diagnose the server stack
ConnectServer lists and routes subservers; JoinServer handles account login; DataServer handles persistent data. GameServer runs gameplay, and GameServerCS owns the configured siege maps. StartUp.xml is a process launch list, not a gameplay configuration file.
The outcome to aim for
ConnectServer lists and routes subservers; JoinServer handles account login; DataServer handles persistent data. GameServer runs gameplay, and GameServerCS owns the configured siege maps. StartUp.xml is a process launch list, not a gameplay configuration file.
Success check: Connect with a test account, create or load a character, relog and verify persistence. Check both normal and siege roles.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
Confirm your SQL service and database are available. Enter your own connection settings in the DataServer and JoinServer files; keep them private.
- STEP 2
Check each StartUp Process entry: Path is relative to the startup tool, Run=True starts it and Run=False skips it. Preserve Parameters; Delay is a launch delay, not a readiness check.
- STEP 3
Start DataServer, JoinServer and ConnectServer, confirm their readiness, then start GS and GSCS. Start any configured AntiServer dependency before accepting public connections.
- STEP 4
For maintenance, announce downtime and stop gameplay processes cleanly first. Allow data saves to complete before stopping DataServer and the remaining services. Do not use forced termination as the normal shutdown method.
- STEP 5
If a server does not appear, compare ServerCode, ports, ServerList.xml and map ownership. If login fails, inspect JoinServer/DataServer errors before editing gameplay files.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Configuration example
Keep the existing root/sections and unrelated rows. This example is not a complete original or a full replacement file.
<Process Run="True" Delay="300" Path="..\4.MuServer\Sub-1\GameServer\GameServer.exe" Parameters="" />Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →Verify the result in game
Connect with a test account, create or load a character, relog and verify persistence. Check both normal and siege roles.
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.