Skip to content
MOMU EMULATOR THE SERVER OWNER’S LIBRARYNeed a hand? Get support ↗
MOMUEMULATOR
简体中文
CONFIGURATION REFERENCE

015 - Blood Castle 5.xml

Map spawn file: 015 — Blood Castle 5

4.MuServer/Sub-1/Data/Monster/MonsterSetBase/015 - Blood Castle 5.xml
XML9 recorded fieldsutf-8-sigRecorded file structure
Recorded file structure

Verify the active copy and owning role before editing. Recorded structure does not prove feature activation.

APPLICATION / RELOAD/reload monster

Apply on the owning role. Startup-only settings require a restart; spawn/event reloads can reset active state.

Open full tutorial

Field reference

Names and observations come from the supplied files. “Not established” means the unit/range/enum is not verified. Keep a known working value until confirmed.

Section / parameterMeaning and verified limits
ConfigMonster/NPC class ID. In ItemDrop.xml MonsterIndex=-1 accepts any monster class.
ConfigSpawn distance parameter, not the number of monsters. Copy a working placement and test movement.
ConfigHorizontal map coordinate; validate walkable terrain at the location.
ConfigVertical map coordinate; validate walkable terrain at the location.
ConfigFacing direction; -1 is used for random facing in the documented spawn format.
ConfigSpawn element assignment; must match supported elemental monster behavior.
ConfigEvent bracket or stage identifier. Keep linked stage, monster and reward entries aligned.
ConfigEvent bracket or stage identifier. Keep linked stage, monster and reward entries aligned.
ConfigRespawn/regeneration time field for the monster or event template; confirm the unit in the owning system.

9 fields · 1 / 1

Learn how to apply a changeOpen related lab

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.