Your server, explained.
Choose a goal. Find the right file. Understand each value, rehearse the change and verify the result.
A place for every question.
Getting started
5 practical guidesInstallation & infrastructure
3 practical guidesGameplay configuration
5 practical guidesItems, shops & economy
8 practical guidesMaps, monsters & NPCs
5 practical guidesEvents & Castle Siege
4 practical guidesAdvanced & custom systems
14 practical guidesClient & tools
3 practical guidesWebsite & data integration
1 practical guidesTroubleshooting
1 practical guidesInstallation & infrastructure
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.
Open the guide 06Reload only the system you changed
The supplied command handler supports targeted reloads. The command label and permission are controlled by Command.txt (stable command index 35) and its command settings. Use a properly authorized administrator character.
Open the guide 45Connection protection, anti-dupe and anti-hack tuning
Protection settings can reject legitimate sessions or remove duplicated items. Tune with evidence from the relevant logs and a controlled test account.
Open the guideBuilt around the supplied MOMU configuration snapshot. Reference entries flag alternate copies and unconfirmed fields. Match the guide to your deployed version; archived packages and live gameplay were not audited by publishing these pages.