Competitive / MxF Factions
Each Raid Outpost definition uses four main cuboid regions:
Docs version
v1.0.0
Product version
1.0.0-dev
Last updated
Jul 21, 2026
# Raid Outpost Regions
Each Raid Outpost definition uses four main cuboid regions:
outer - the full event area and default reset area.
breach - the area where block destruction counts toward breach confirmation.
entry - the area used to confirm attackers have entered the structure.
core - the final capture area factions must control.
Regions are configured in plugins/Factions/mxf/raid-outpost-definitions.yml.
Example:
raid-outposts:
fortress:
world: "world"
regions:
outer:
minimum: { x: -8, y: 60, z: -8 }
maximum: { x: 8, y: 78, z: 8 }
breach:
minimum: { x: -7, y: 60, z: -7 }
maximum: { x: 7, y: 74, z: 7 }
entry:
minimum: { x: -5, y: 60, z: -5 }
maximum: { x: 5, y: 72, z: 5 }
core:
minimum: { x: -2, y: 63, z: -2 }
maximum: { x: 2, y: 66, z: 2 }If WorldEdit is installed, select a cuboid and run:
/f raidoutpost admin setouter fortress
/f raidoutpost admin setbreach fortress
/f raidoutpost admin setentry fortress
/f raidoutpost admin setcore fortress
The definition is saved immediately and validation runs on reload/startup.
The loader normalizes min/max coordinates and skips invalid definitions. One bad definition does not disable the whole Raid Outpost system.
Recommended layout:
Keep core inside outer.
Keep breach inside or overlapping outer.
Keep regions in the same world.
Avoid very large reset regions until the block batch settings are tuned.