> For the complete documentation index, see [llms.txt](https://changelog.matrixemulator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.matrixemulator.com/welcome/server/muserver/data/monster/setbase/invasion/000-mapname.md).

# 000 - MapName

## <mark style="color:yellow;">SetBase\Invasion — Permanent Copies of Invasion Monsters</mark>

<mark style="color:green;">Defines permanent, always-present copies in the open world of the same monsters used by scheduled invasions (</mark><mark style="color:green;">`InvasionManager.dat`</mark><mark style="color:green;">)—for example, Golden Budge Dragon, Golden Derkon, and the White Wizard in Lorencia. It uses the same format as</mark> <mark style="color:green;"></mark><mark style="color:green;">`SetBase`</mark> <mark style="color:green;"></mark><mark style="color:green;">in the root folder—the only difference is the type of content stored in each file.</mark>

<mark style="color:orange;">**This is not the invasion system itself.**</mark> <mark style="color:orange;"></mark><mark style="color:orange;">The scheduled invasion that occurs periodically and broadcasts announcements to all players is controlled by</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`InvasionManager.dat`</mark><mark style="color:orange;">, which has its own internal spawn points completely independent of this file. The monsters defined here spawn and respawn continuously, regardless of whether the scheduled invasion is active. They happen to be the same monster types, but they belong to a separate population.</mark>

<mark style="color:orange;">The filename must begin with three digits followed by</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`-`</mark> <mark style="color:orange;"></mark><mark style="color:orange;">(e.g.,</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`000 - Lorencia.txt`</mark><mark style="color:orange;">). Each file contains one or more blocks, identified by a number (</mark><mark style="color:orange;">`0`</mark><mark style="color:orange;">,</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`1`</mark><mark style="color:orange;">,</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`2`</mark><mark style="color:orange;">,</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`3`</mark><mark style="color:orange;">, or</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`4`</mark><mark style="color:orange;">) on its own line and terminated by</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`end`</mark><mark style="color:orange;">.</mark>

### <mark style="color:yellow;">Section</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">`3`</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">— Multiple Monsters Within an Area (Most Common Here)</mark>

<table data-search="false"><thead><tr><th>Column</th><th>Accepted Values</th><th>Description</th></tr></thead><tbody><tr><td>Monster</td><td>Monster class number</td><td>The entity that spawns.</td></tr><tr><td>Map</td><td>Map number</td><td><strong>No effect</strong> — see notes.</td></tr><tr><td>Range</td><td>Number</td><td>Movement radius for each monster around its individual spawn point.</td></tr><tr><td>BeginPosX / BeginPosY</td><td>Coordinates</td><td>One corner of the spawn area.</td></tr><tr><td>EndPosX / EndPosY</td><td>Coordinates</td><td>Opposite corner of the spawn area—each monster spawns at a random point within the rectangle defined by both corners.</td></tr><tr><td>Direction</td><td>Number from 0 to 7, or <code>-1</code></td><td>Initial facing direction. <code>-1</code> = random.</td></tr><tr><td>Quantity</td><td>Number</td><td>Number of monsters of this type spawned throughout the area.</td></tr><tr><td>Value</td><td>Number</td><td>Additional value associated with this spawn group.</td></tr><tr><td>Comment</td><td>Text after <code>//</code></td><td>Free-form note; ignored by the game—typically the monster's name.</td></tr></tbody></table>

### <mark style="color:yellow;">Section</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">`0`</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">and Section</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">`4`</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">— Fixed Spawn at an Exact Position</mark>

| Column                | Accepted Values             | Description                                        |
| --------------------- | --------------------------- | -------------------------------------------------- |
| Monster               | Monster/NPC class number    | The entity that spawns.                            |
| Map                   | Map number                  | **No effect** — see notes.                         |
| Range                 | Number                      | Monster movement radius around its spawn point.    |
| PositionX / PositionY | Coordinates                 | Spawn location.                                    |
| Direction             | Number from 0 to 7, or `-1` | Initial facing direction. `-1` = random direction. |
| Comment               | Text after `//`             | Free-form note; ignored by the game.               |

### <mark style="color:yellow;">Section</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">`2`</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">— Fixed Spawn with Slight Random Variation</mark>

<mark style="color:orange;">Uses the same columns as blocks</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`0`</mark><mark style="color:orange;">/</mark><mark style="color:orange;">`4`</mark><mark style="color:orange;">, but the final position (</mark><mark style="color:orange;">`PositionX`</mark><mark style="color:orange;">/</mark><mark style="color:orange;">`PositionY`</mark><mark style="color:orange;">) is randomly selected within a 7x7 area around the specified point—chosen once when the server starts, and chosen again (within an even smaller area) each time the monster respawns.</mark>

### <mark style="color:yellow;">Section</mark>  <mark style="color:yellow;"></mark><mark style="color:yellow;">`1`</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">— Multiple Monsters Within an Area</mark>

<mark style="color:orange;">Uses the same columns as block</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`3`</mark> <mark style="color:orange;"></mark><mark style="color:orange;">(</mark><mark style="color:orange;">`BeginPos`</mark><mark style="color:orange;">/</mark><mark style="color:orange;">`EndPos`</mark><mark style="color:orange;">/</mark><mark style="color:orange;">`Direction`</mark><mark style="color:orange;">/</mark><mark style="color:orange;">`Count`</mark><mark style="color:orange;">), except that it does not include the additional</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`Value`</mark> <mark style="color:orange;"></mark><mark style="color:orange;">column at the end.</mark>

### <mark style="color:yellow;">Notes</mark>

* **The `Map`/`Lorencia` column inside the file has no effect whatsoever.** The actual map is determined by the three digits in the **filename**. To move a spawn group to another map, the file must be renamed or moved—editing the column inside the file changes nothing.
* These monsters are a completely separate population from the scheduled invasion. Disabling or reconfiguring `InvasionManager.dat` will not remove them from the map, because they are spawned by this file, not by the invasion system.