For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Shared game content loaded by every GameServer instance

Shared game content. One copy exists per installation at the release root (Data/). Every GameServer process reads from this folder in addition to its own per-server Data/ identity folder.

File Location

Data/
├── Command.xml
├── Effect.xml
├── EventItemBagManager.xml
├── MapManager.xml
├── MapServerInfo.xml
├── Message.xml
├── ShopManager.xml
├── CashShop/
├── Character/
├── Custom/
├── Event/
├── EventItemBag/
├── Hack/
├── Item/
├── Monster/
├── Move/
├── Plugins/
│   ├── Characters/
│   ├── Events/
│   ├── Items/
│   ├── Social/
│   └── World/
├── Quest/
├── QuestWorld/
├── Shop/
├── Skill/
├── Terrain/         (binary map attributes, not admin-editable)
└── Util/

Shared vs Per-Server

Root
Scope
Contents

Data/ at release root (this section)

One per installation

Items, monsters, events, skills, shops, plugins, quests, messages, maps

GameServer/Data/

One per GameServer instance

Per-server identity .dat files, documented under the GameServer section

Running multiple GameServers on one machine means multiple GameServer/Data/ folders (each with a unique ServerCode and LicenseKey) but a single shared Data/ folder that every instance reads.

Sections

Root files

File
Purpose

Command.xml

NPC-triggered chat commands and dialogs

Effect.xml

Buff and debuff effect definitions

EventItemBagManager.xml

Registry of event loot bags

MapManager.xml

Per-map properties, PK zones, restrictions

MapServerInfo.xml

Multi-server map ownership

Message.xml

System message strings

NPC-to-shop mapping

Subfolders

Subfolder
Contents

CashShop/

Cash shop products (CashShop.xml)

Character/

Per-class defaults (DefaultClassInfo.txt)

Custom/

Custom server features (CustomDeathMessage.txt and similar)

Event/

One .dat per event (Blood Castle, Chaos Castle, Crywolf, Devil Square, Kanturu, Raklion, Illusion Temple, Imperial Guardian, Double Goer, Moss Merchant, Bonus Manager, Castle Deep, Rei Do Mu, and Mu Castle). Castle Siege configuration lives in the per-server GameServer identity files, not here

EventItemBag/

Per-bag loot tables referenced by EventItemBagManager.xml

Hack/

Packet validation rules (HackPacketCheck.txt) and binary anti-hack blobs (Dec1.dat, Enc2.dat)

Master item database, option tables, drop rules, set and socket definitions

Monster stats, spawn locations, AI, skills

Move/

Teleport destinations and gate definitions (Move.txt, Gate.txt, MoveSummon.txt)

Modular features: ResetSystem, VIP, ChaosMix, PostCommand, plugin extensions

Quest/

Classic quest system (Quest.txt, QuestObjective.txt, QuestReward.txt)

QuestWorld/

World-quest rework (QuestWorld.txt, QuestWorldObjective.txt, QuestWorldReward.txt)

Per-NPC shop inventories registered in ShopManager.xml

Skill/

Master skill tree, damage curves, skill definitions (Skill.txt, MasterSkillTree.txt, SkillDamage.txt, SkillElect.hit)

Util/

Experience table, chat filter, rename filter, GM list, notices (ExperienceTable.txt, Filter.txt, FilterRename.txt, GameMaster.xml, Notice.xml)

Overlays

A GameServer can layer a second folder on top of the shared Data/ folder to override specific files without editing the shared copy. See Data Overlays.

Game Data Sync

Many files here are pushed from the server to the client at login (skills, item definitions, custom visuals, chaos mix recipes, and more). Edits to those files take effect after the next relog per player, not instantly. See Game Data Sync for the full list and effect-timing rules.

Reload vs Restart

  • Restart required for nearly every file under Data/. Loaders run once at GameServer startup.

  • Hot reload supported by a few plugins (ResetSystem, SkillSpeedScale, ChaosMix, CustomCombo, CustomStartItem, MuHelperPickup, and a few others). Each plugin page documents its own reload trigger.

  • Synced files also require each player's next login to see the new data, even after GameServer restart - see Game Data Sync.

When in doubt, restart.

Where to Start

New admins usually want these first:

  1. Item/ - item database, drops, options

  2. Monster/ - stats and spawns

  3. Shop System - NPC shop contents

  4. Plugins/ - feature toggles

  5. Specific Event/ pages for the events you run

Last updated