Raid Outposts are temporary raid objectives that combine breach detection, entry confirmation, KOTH-style core control, rewards, and safe reset handling.
Docs version
v1.0.0
Product version
1.0.0-dev
Last updated
Jul 21, 2026
# Raid Outposts
Raid Outposts are temporary raid objectives that combine breach detection, entry confirmation, KOTH-style core control, rewards, and safe reset handling.
The system is configured through YAML:
plugins/Factions/mxf/raid-outposts.yml controls engine behavior, capture rules, breach rules, rewards, reset profiles, schedules, audit, messages, and history limits.
plugins/Factions/mxf/raid-outpost-definitions.yml controls each outpost definition.
plugins/Factions/menus/raid-outposts.yml controls the Raid Outpost GUI.
plugins/Factions/data/raid_outposts.json stores runtime state, cooldowns, and history.
Player Commands
/f raidoutpost - list configured raid outposts.
/f raidoutposts - alias for /f raidoutpost.
/f ro - short alias.
/f raidop - short alias.
/f raidoutpost list - list configured raid outposts.
/f raidoutpost status [id] - show the active state, phase, breach state, controller, progress, cooldown, and history summary.
/f raidoutpost menu - open the configured GUI.
/f raidoutpost history [id] [page] - view bounded completion history.
Staff Commands
/f raidoutpost admin create <id>
/f raidoutpost admin delete <id>
/f raidoutpost admin setouter <id>
/f raidoutpost admin setbreach <id>
/f raidoutpost admin setentry <id>
/f raidoutpost admin setcore <id>
/f raidoutpost admin setteleport <id>
/f raidoutpost admin start <id>
/f raidoutpost admin stop <id>
/f raidoutpost admin forcapture <id> <faction>
/f raidoutpost admin reset <id>
/f raidoutpost admin snapshot <id>
/f raidoutpost admin setduration <id> <seconds>
/f raidoutpost admin enable <id>
/f raidoutpost admin disable <id>
/f raidoutpost admin inspect <id>
/f raidoutpost admin reload
/f raidoutpost admin save
Lifecycle
1. The outpost starts manually or through a configured schedule.
2. A block snapshot is captured for the reset region.
3. Attackers breach the configured breach region.
4. Attackers enter the configured entry region.
5. One eligible faction controls the core region.
6. Progress reaches the configured capture duration.
7. Rewards are marked as executed before external reward handlers run.
8. The configured reset profile restores blocks safely on the main thread.
9. Cooldown and history are persisted.
Season Policy
Scheduled Raid Outposts obey the Season Engine raid feature policy. Manual staff starts can bypass the blocked phase for controlled testing and administration.
Restart Behavior
The safest default is used: active sessions are cancelled on shutdown and saved to history. Cooldowns and history persist. Rewards are not rerun after restart.
Limitations
The current reset strategy restores block type and legacy data. Container inventories, tile entities, and schematic paste resets are intentionally deferred.