MxF Factions is a competitive FactionsUUID fork that preserves familiar faction gameplay while adding configurable progression, events, raid tooling, seasons, analytics, staff enforcement, and a faction web panel.
Docs version
v1.0.0
Product version
1.0.0-dev
Last updated
Jul 21, 2026
# MxF Factions Documentation
MxF Factions is a competitive FactionsUUID fork that preserves familiar faction gameplay while adding configurable progression, events, raid tooling, seasons, analytics, staff enforcement, and a faction web panel.
This documentation is organized for three audiences:
**Server owners** should begin with Installation, Configuration, and Integrations.
**Players and faction leaders** should begin with the Player Guide and Commands.
**Staff** should begin with the Staff Guide, [Competitive Rules](staff-guide.md#competitive-rules-and-sanctions), and Investigations.
> **Use staging first:** Install new builds and configuration changes on a staging server before production. Back up the complete plugins/Factions/ folder, not only the JAR.
Quick Start
1. Stop the server and remove conflicting Factions JARs.
2. Put MxF-Factions.jar in plugins/.
3. Start once to generate plugins/Factions/config.yml.
4. Set license-key: "YOUR-LICENSE-KEY" and restart.
5. Confirm startup reports a valid license, loaded YAML files, detected server version, and no SEVERE errors.
6. Run /f config validate, /f compatibility, /f help, and the [first-install checklist](installation.md#first-install-checklist).
| Web | In-game account linking, secured API bridge, faction dashboard, public profiles. |
See the Feature Overview for behavior, commands, configuration ownership, and readiness notes.
Essential References
Complete command reference
Practical command guide
Complete feature setup guide
Permission nodes
Configuration file map
GUI configuration
PlaceholderAPI
Backups and runtime data
Troubleshooting
Compatibility
Support Information
When reporting a problem, include the MxF version, server software/version, Java version, dependency versions, relevant YAML, reproduction steps, and the complete exception. Never publish your license key, generated web secrets, or runtime player/faction JSON.