Installation / MxF Factions
The recommended setup order for taking MxF Factions from first install to a ready server season.
Docs version
v1.0.0-dev
Product version
1.0.0-dev
Last updated
Jul 21, 2026
Set up MxF Factions in layers. Core faction behavior should work before progression, progression should work before seasonal rewards, and event regions should work before automatic schedules.
Install the JAR and dependencies.
Confirm /f version, /f compatibility, /f config status, and /f config validate.
Configure config.yml, features.yml, commands.yml, permissions.yml, and integrations.yml.
Choose power or DTR-style land control.
Configure faction limits, member limits, relation limits, protected worlds, claim costs, claim limits, and protection behavior.
Configure create, join, invite, leave, disband, homes, warps, claims, map, roster, alts, roles, and relations.
Review /f perms defaults before players create factions.
Confirm member, officer, co-leader, and leader actions are separated correctly.
Install Vault and an economy provider.
Configure faction bank access.
Configure TNT bank, fill, and siphon limits.
Configure faction chest and vault counts.
Verify balances, items, TNT, and vault contents persist after normal restart.
Configure missions and mission definitions.
Configure upgrade categories, levels, requirements, prices, and effects.
Configure reward definitions, shop entries, point shop entries, and purchase confirmations.
Keep rewards conservative until all handlers are verified.
Configure FTop and PTop cache behavior.
Configure Season Points and the Season Engine.
Configure Grace, SOTW, shields, raids, alerts, and war center views.
Configure KOTH, Outposts, and Raid Outposts after regions are selected.
Enable schedules only after manual starts and stops behave correctly.
Configure analytics, intelligence, audit logs, competitive rules, investigations, and rollback.
Assign staff permission groups carefully.
Keep destructive actions behind owner-only permissions and confirmation.
Confirm license activation.
Confirm customer portal ownership.
Confirm secure downloads are linked to the product.
Configure web dashboard linking only after the server and site are reachable from the intended network path.
Do not enable every schedule, reward, penalty, and automation on day one. Launch with the core systems stable, then open higher-risk systems one at a time.