Configure boss invasions and Event Board travel
An invasion combines a scheduled invasion ID with matching INVASION spawn entries. The boss’s reward is connected separately by the reward manager.
The outcome to aim for
An invasion combines a scheduled invasion ID with matching INVASION spawn entries. The boss’s reward is connected separately by the reward manager.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
Enable InvasionManagerSwitch in Event.ini for the owning role. Locate the intended invasion’s configuration and schedule sections.
- STEP 2
In each map XML, inspect INVASION Config Value: it connects a spawn template to an invasion type. Keep Class, map and rectangle valid; ordinary SPOT rows do not become scheduled invasions.
- STEP 3
Check the active map profile and MapServerInfo ownership. Put the spawn in the role that actually runs that map.
- STEP 4
Check the boss’s EventItemBagManager mapping and bag content. Update the Event Board entry’s visibility/travel settings without assuming it creates the boss.
- STEP 5
In maintenance reload monster templates and event data, then test one full invasion cycle, boss discovery, travel, kill, reward and cleanup.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →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.