Add, 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.
The outcome to aim for
- Choose SPOT population versus one exact MONSTER point.
- Use exclusive rectangle ends and a registered class.
- Check profile, role ownership, terrain and actual population.
Before you start
Select the map XML used by the active profile and a valid class. Coordinate bounds are not proof that terrain is walkable.
Files you need
Understand the fields
| Field | Meaning & dependencies |
|---|---|
Class | An existing monster definition ID. |
BeginPosX/Y → EndPosX/Y | Two corners of the walkable spawn rectangle, within map bounds. |
Quantity | Number of monsters generated by this Config. Duplicate rows add more. |
Range | Distance parameter; it does not set population. |
Direction | Facing direction; -1 is random facing in this layout. |
Element | Elemental assignment; leave a working value unless changing elemental behavior. |
One step at a time
- STEP 1
Choose the owning role and map file, for example 000 - Lorencia.xml. Modern map 112 uses the 621 profile folder. Confirm that the selected profile allows the map.
- STEP 2
Find a valid monster Class in Monster.txt or the loaded modern monster extension. Choose walkable coordinates away from town safe areas, walls, exits and quest NPCs.
- STEP 3
Add the sample Config inside the existing SPOT element. BeginPosX/Y and EndPosX/Y define the rectangle; Quantity is the number spawned. Range is the spawn’s distance parameter, not its population.
- STEP 4
For a fixed-position normal monster, use a Config under MONSTER with PositionX and PositionY. Use NPC only for NPC placements; EVENT and INVASION are controlled by their event logic.
- STEP 5
To remove a spot, remove or comment the entire Config element after backing it up. To move it, update both rectangle corners. Coordinates must stay within 0..255 and point to usable terrain.
- STEP 6
Apply /reload monster in maintenance or restart the owning GameServer. Visit the location, count monsters, test respawn after kills and verify players are not trapped.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Configuration example
Keep the existing root/sections and unrelated rows. This example is not a complete original or a full replacement file.
<Config Class="3" Range="2" BeginPosX="193" BeginPosY="128" EndPosX="198" EndPosY="133" Direction="-1" Quantity="8" Element="0" />What changed?
The default rectangle stays X=193–197 and Y=128–132; Quantity changes from 4 to 8. This configures twice as many spawn entries, not a terrain-aware guarantee that every placement succeeds.
The lab names changed fields and keeps the example separate from your real configuration.
Open this demonstrationApply the real change
Merge Config into the matching <SPOT> or <MONSTER> under the existing MonsterSetBase root in the selected three-digit map XML. Use /reload monster during maintenance on the owning role.
Verify the result in game
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.
If something goes wrong
Population differs
Duplicate Config rows add creatures. Terrain placement can fail, and event templates are separate.
Legacy TXT edit has no effect
The per-map XML folder takes priority when present. Check active profile and GS versus GSCS.
Dependencies & important details
The example reproduces an existing Lorencia spot. Edit that row or use a different area; appending it again at the same position duplicates the population. Minimap marker edits do not create monsters.
SPOT end coordinates are exclusive: 193→198 covers 193–197. Use Begin<End. MONSTER is an exact point with one spawn, not a quantity rectangle.