Find the correct configuration: GS, GSCS and fallback files
There are two different Data locations for each GameServer role. Most gameplay tables are in Sub-1/Data. GameServerInfo - *.ini files are in Sub-1/GameServer/Data. Mixing these locations is a common reason for edits having no effect.
The outcome to aim for
There are two different Data locations for each GameServer role. Most gameplay tables are in Sub-1/Data. GameServerInfo - *.ini files are in Sub-1/GameServer/Data. Mixing these locations is a common reason for edits having no effect.
Success check: After applying a change, verify it in the same subserver you edited, then verify the other role if you changed both.
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
GS means the normal GameServer under 4.MuServer; GSCS means the Castle Siege role under 8.MuServerCS. Identify which role owns the map or event you are changing.
- STEP 2
For a rule intended to be identical on both roles, edit the equivalent files in both locations. Keep role-specific ServerCode, ports, map ownership and siege settings distinct.
- STEP 3
For custom tables, the loader first requests Data/MOMU/<filename>. Only when that requested file is absent does it try Data/Custom/<filename>. If both exist, edit the requested MOMU copy.
- STEP 4
MapManager.txt is always the file directly under Sub-1/Data. A MapManager.txt inside Move/Profiles/621 is not the active global drop configuration in this version.
- STEP 5
Do not choose a Data/Data folder or an old GameServerCs directory merely because its filenames look familiar. Confirm the running executable path and startup entry.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
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
After applying a change, verify it in the same subserver you edited, then verify the other role if you changed both.
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.