Find the next useful answer.
Search tasks, configuration files, field explanations and game identifiers. Every result keeps its context.
Tutorials
49 matchesRead this first: how to use your server manual
This manual describes the files supplied with this MOMU server installation. Start with the task you want to perform, follow its file paths, and use the File Reference for the exact keys or columns. All paths begin inside your Mu Server folder. Values shown in examples are training examples, not replacement configuration files.
Matched task steps, paths or system keywordsTutorialsFind 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.
Matched task steps, paths or system keywordsTutorialsMake a change, apply it and roll it back
Use this procedure for every edit. It separates a text edit from a successful gameplay change and gives you a reliable way back.
Matched task steps, paths or system keywordsTutorialsEdit INI, XML and section tables correctly
A parser reads structure, not the visual alignment of a file. Keep each file’s original syntax and encoding. Do not translate technical names such as MapNumber, Enable or Index.
Matched task steps, paths or system keywordsTutorialsStart, 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.
Matched task steps, paths or system keywordsTutorialsReload 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.
Matched task steps, paths or system keywordsTutorialsUnderstand the four different drop controls
Choose the correct layer before changing a number. There is no single universal “drop percentage” for the entire server.
Matched task steps, paths or system keywordsTutorialsChange drops, EXP and restrictions on one map
Each row is one map. Edit the active Data/MapManager.txt for the owning role, regardless of whether profile 603 or 621 is selected.
Matched task steps, paths or system keywordsTutorialsCreate an item drop rule for a map or monster
Use ItemDrop.xml when the goal names a specific item, monster or monster-level range. Item category and index identify the item; they are not a shop number or monster ID.
Matched task steps, paths or system keywordsTutorialsEdit box, boss and event rewards
The manager connects an item, monster or special event value to a numbered reward bag. Editing a similarly named bag without checking this connection may change the wrong reward.
Matched task steps, paths or system keywordsTutorialsReward bag section 0: quantity, Zen and quality rolls
The outer bag configuration is applied before the weighted candidate pool. Its rate scales differ from ItemDrop.xml and MapManager.
Matched task steps, paths or system keywordsTutorialsAdd, move or remove a monster hunting spot
The supplied server loads per-map XML spawns when the XML folder is present. The first three filename digits identify the map. Profile 621 adds modern-map XML files on top of the base set.
Matched task steps, paths or system keywordsShowing the highest-ranked matches. Add a filename, field name or role filter to narrow the results.
Configuration files
1204 matchesConnectServer.ini
1.ConnectServer/ConnectServer.ini
ini · Recorded file structureConfiguration filesServerList.xml
1.ConnectServer/ServerList.xml
xml · Recorded file structureConfiguration filesAllowableIpList.txt
2.DataServer/AllowableIpList.txt
xml · Recorded file structureConfiguration filesBadSyntax.txt
2.DataServer/BadSyntax.txt
text · Recorded file structureConfiguration filesDataServer.ini
2.DataServer/DataServer.ini
ini · Recorded file structureConfiguration filesAllowableIpList.txt
3.JoinServer/AllowableIpList.txt
xml · Recorded file structureConfiguration filesJoinServer.ini
3.JoinServer/JoinServer.ini
xml · Recorded file structureConfiguration filesBlackList.txt
4.MuServer/Sub-1/Data/BlackList.txt
section-table · Recorded file structureConfiguration filesCashShopPackage.txt
4.MuServer/Sub-1/Data/CashShop/CashShopPackage.txt
text · Recorded file structureConfiguration filesCashShopProduct.txt
4.MuServer/Sub-1/Data/CashShop/CashShopProduct.txt
section-table · Recorded file structureConfiguration filesDefaultClassInfo.txt
4.MuServer/Sub-1/Data/Character/DefaultClassInfo.txt
text · Recorded file structureConfiguration filesCommand.txt
4.MuServer/Sub-1/Data/Command.txt
text · Recorded file structureShowing the highest-ranked matches. Add a filename, field name or role filter to narrow the results.
Built 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.