Monster Configuration

The Monster system controls all NPC and monster behavior in the game including spawning, stats, AI, and skills.

Configuration Files

Core Monster Definitions

File	Purpose
Monster.xml	Monster stats, levels, resistances, regen time

Spawn Configuration

File/Directory	Purpose
MonsterSetBase/	Directory containing per-map spawn files (e.g., 000 - Lorencia.xml, 002 - Devias.xml)
MonsterSetBaseCS/	Directory for Castle Siege server spawn files (used if GAMESERVER_TYPE ≠ 0)
KanturuMonsterSetBase.xml	Kanturu event map spawns (loaded separately by Kanturu system)

How spawns load: The server scans either MonsterSetBase/ or MonsterSetBaseCS/ directory (depending on server type) and loads ALL .xml files found. There is no master registry file - files load alphabetically.

Monster Skills

File	Purpose
MonsterSkill.xml	Assigns skills to specific monsters
MonsterSkillUnit.xml	Defines skill behaviors (targeting, scope, delay)
MonsterSkillElement.xml	Defines skill effects (damage, debuffs, buffs)

Advanced AI System

File	Purpose
MonsterAIGroup.xml	Assigns AI personalities to monster spawns
MonsterAIUnit.xml	Defines complete AI personalities (links automata to actions)
MonsterAIAutomata.xml	State machine definitions (when to change behavior)
MonsterAIElement.xml	Atomic AI actions (what to do in each state)
MonsterAIRule.xml	Global AI rules (currently unused)

AI System vs Basic Spawns: Most monsters use basic spawns from MonsterSetBase files. The AI system (MonsterAI*.xml) is only used for advanced boss mechanics and special monster behaviors.

File Location

All monster configs are in: GameServer/Data/Monster/

Basic spawn files are in: GameServer/Data/Monster/MonsterSetBase/ (directory with per-map XML files)

How spawns load: The GameServer scans MonsterSetBase/ directory and loads ALL .xml files found. Each file is named by map number and name (e.g., 000 - Lorencia.xml, 002 - Devias.xml). There is no master registry file controlling which maps load.

Workflow Overview

Adding a New Monster

1. Define stats in Monster.xml - Add <Info> entry with unique Index, stats, resistances, RegenTime

2. Assign skills (optional) in MonsterSkill.xml - Add <Monster> entry linking monster Index to skill units

3. Configure spawns - Choose one method:

   • Basic spawn: Edit appropriate map file in MonsterSetBase/ directory

   • Advanced AI spawn: Create entries in MonsterAIGroup.xml with AI personality

Modifying Monster Behavior

• Change stats - Edit Monster.xml (Level, Life, DamageMin/Max, Defense, etc.)

• Change spawn density - Edit Count attribute in map-specific MonsterSetBase/*.xml file (Type 1 or 3 only)

• Change spawn locations - Edit X/Y (and TX/TY for Type 1/3) coordinates in map-specific file

• Change respawn time - Edit RegenTime in Monster.xml (in seconds, server multiplies by 1000)

• Add/remove skills - Edit MonsterSkill.xml (add or remove <Monster> entry)

• Change AI behavior - Edit MonsterAIGroup.xml (for AI-controlled monsters only)

Creating Custom Skills

1. Define effects in MonsterSkillElement.xml - Create Element entries

2. Define behavior in MonsterSkillUnit.xml - Create Unit entry referencing Elements

3. Assign to monster in MonsterSkill.xml - Reference Unit index

Important Concepts

Spawn File Loading Behavior

The GameServer loads monster configuration files at startup in this order:

1. KanturuMonsterSetBase.xml - Kanturu event spawns

2. All MonsterAI files (Automata, Element, Group, Rule, Unit)

3. Monster.xml - Monster stat definitions

4. Either MonsterSetBase/*.xml (normal server) OR MonsterSetBaseCS/*.xml (Castle Siege server)

5. All MonsterSkill files (Element, Unit, Skill)

Spawn directory loading behavior:

• Server scans the appropriate spawn directory and loads ALL .xml files found

• Files are processed in alphabetical order by filename

• If you add a new map spawn file, just place it in the directory - no registry file needed

• No master spawn registry file exists

Server Type: Which spawn directory loads depends on the GAMESERVER_TYPE compile flag. Type 0 = Normal (uses MonsterSetBase/), Type 1+ = Castle Siege (uses MonsterSetBaseCS/).

No Master Registry: There is NO master spawn registry file. The documentation claim that "MonsterSetBase.xml references per-map files" is incorrect. The server scans the directory and loads all XML files directly.

Monster Index

Every monster has a unique Index number used throughout all configs:

• 0-99: Common monsters (Bull Fighter, Spider, etc.)

• 200-299: NPCs (Trainers, merchants, guards)

• 300+: Special monsters and bosses

Spawn Types

Type	Behavior	Use Case
0	Fixed position	NPCs, guards, bosses
1	Random within range (uses TX/TY)	Normal monster groups
2	Random spot (±3 from X/Y)	Scattered spawns
3	Event spawns (uses TX/TY)	Blood Castle, Devil Square
4	Noble monsters	Special boss spawns

Type 1 vs Type 2: Type 1 spawns require TX/TY coordinates defining a spawn area. Type 2 randomly offsets the X/Y coordinates by ±3 tiles at load time (no TX/TY needed).

Skills System

Skills are modular:

• Elements define effects (damage, stun, heal)

• Units combine Elements into a complete skill

• MonsterSkill assigns Units to monsters

A monster can have up to 6 skill unit slots.

Dependencies

Basic Monster System

Monster.xml (defines stats, RegenTime by Index)
    ↑
    | (references monster Index)
    |
MonsterSetBase/*.xml (spawns monsters at locations)

Skill System

Monster.xml (monster Index)
    ↑
    | (references monster Index)
    |
MonsterSkill.xml (assigns skill units to monsters)
    ↓ (references unit Index)
MonsterSkillUnit.xml (skill behavior)
    ↓ (references element Index)
MonsterSkillElement.xml (skill effects)

Advanced AI System

MonsterAIGroup.xml (spawns monsters with AI)
    ↓ (references StartAI, AI01-03)
MonsterAIUnit.xml (AI personality)
    ↓ (references Automata + Elements)
    |
    +→ MonsterAIAutomata.xml (state transitions)
    +→ MonsterAIElement.xml (actions in each state)

Common Tasks

Increase Monster Difficulty

1. Edit Monster.xml - Increase Level, DamageMin/Max, Defense

2. Optionally add skills in MonsterSkill.xml

Add Boss Spawn

1. Ensure boss exists in Monster.xml with proper stats

2. Add Type="0" entry in appropriate map file with fixed X/Y

3. Set high RegenTime in Monster.xml (e.g., 3600 = 1 hour)

Create Monster-Dense Zone

1. Find the appropriate map file in GameServer/Data/Monster/MonsterSetBase/ directory

2. Add multiple Type="1" entries with same Class attribute

3. Set Count attribute to desired density (e.g., Count="20" for 20 monsters per spawn point)

4. Define spawn area with X, Y, TX, TY coordinates (monsters spawn randomly within this rectangle)

Disable Monster Skills

1. Find monster Index in MonsterSkill.xml

2. Change UnitType/UnitIndex to "*" (wildcard) to disable slots

3. Or remove entire Monster entry

Next Steps

• Monster Stats Configuration - Define monster attributes

• Monster Spawning - Configure spawn locations and density

• Monster Skills - Assign and create monster skills