MxF Labs pre-launch mode. Customer portal and admin operations remain online.
Feature Overview | MxF Labs
MxF Factions
Feature Setup
Core Faction Rules Setup Roles, Relations, and Chat Setup Homes, Warps, Corners, and Flight Setup Roster and Alts Setup Economy, Vaults, and TNT Setup FTop and PTop Setup Mission System Setup Upgrade, Reward, and Shop Setup Timers, Grace, SOTW, and Shields Setup Raid Operations Setup KOTH Setup Outposts Setup Docs Getting Started MxF Factions Getting Started / MxF Factions
Feature Overview This page summarizes what MxF Factions provides and where each system is configured. Exact syntax is in the Command Reference.
# Feature Overview
This page summarizes what MxF Factions provides and where each system is configured. Exact syntax is in the Command Reference.
Core Factions
| System | What players can do | Main commands |
| --- | --- | --- |
| Factions and membership | Create/disband factions, invite/join/leave/kick, open/close joining, bans. | /f create,
/f invite
/f join
/f kick
/f disband
| Roles and permissions | Leader, co-leader, moderator, member/recruit roles and faction-owned action permissions. | /f promote, /f demote, /f coleader, /f perms |
| Relations and chat | Ally, truce, enemy, neutral, faction/ally chat. | /f ally, /f truce, /f enemy, /f neutral, /f chat |
| Territory | Chunk claims, fill/line/radius operations, ownership, maps and chunk visualization. | /f claim, /f unclaim, /f map, /f seechunk, /f listclaims |
| Home and warps | Faction home, named warps, passwords, configurable icons and limits. | /f home, /f sethome, /f warp, /f setwarp |
| Power and DTR | FactionsUUID power or DTR-style raidability depending on server mode. | /f power, /f dtr, /f show |
| Faction economy | Vault-backed faction balances and transfers. | /f money ... |
Faction Operations | System | Behavior | Configuration |
| TNT bank | Persistent TNT balance, deposit, withdraw, bounded dispenser fill, siphon, audit. | mxf/tnt.yml, menus/tnt.yml |
| Native vaults/chest | Faction-owned inventory storage. PlayerVaults is not required. | mxf/vaults.yml, menus/vaults.yml |
| Roster | Optional approved-member roster and ranks. | mxf/roster.yml, menus/members.yml |
| Alts | Alt invites, limits, open/closed joining, alt entities/teleport where enabled. | mxf/alts.yml, menus/members.yml |
| Settings/permissions | GUI controls for faction-owned settings and internal access. | menus/faction.yml, permissions.yml |
| Corners | Configured premium corner locations with controlled purchase/claim/teleport behavior. | mxf/corners.yml |
| Live War Center | Tactical view over active raids, alerts, shield, TNT, claims, and members. | mxf/war-center.yml, menus/war-center.yml |
Progression and Economy | System | Behavior | Learn more |
| Upgrades | YAML-defined levels, prices, requirements, and registered effects. | Custom Upgrades |
| Missions | YAML-defined objectives, filters, assignment cycles, progress, and rewards. | Custom Missions |
| Rewards | Reusable money, faction-money, Season Point, XP, item, command, and bundle actions. | Rewards |
| Shop | Configurable catalogs, multiple price providers, limits, confirmations, history, and refunds. | Shop |
| Point shop | Shop surface using Season Points where definitions are configured. | Shop |
Competitive Systems | System | Behavior | Learn more |
| FTop/PTop | Cached faction value leaderboard; PTop reports only data supported by safe tracking. | /f top, /f ptop, mxf/ftop.yml |
| Season Points | Persistent non-negative faction competitive score and cached leaderboard. | Season Points |
| Season Engine | Non-destructive lifecycle, phase policy, snapshots, freeze, archive, Hall of Fame. | Season Engine |
| Season rewards | Preview-first tiers and guarded execution workflow. | Season Rewards |
| KOTH | Cuboid objective capture, contests, schedules, rewards, persistence safeguards. | KOTH |
| Outposts | Territorial control, capture modes, interval rewards, anti-farm controls, buffs. | Outposts |
| Raid Outposts | Breach, entry, core capture, rewards, cooldown, block-snapshot reset. | Raid Outposts |
Raids and Defense | System | Behavior | Configuration |
| Grace/SOTW | Global persistent timers that can block explosions, PvP, claiming, and TNT actions. | mxf/timers.yml |
| Shields | Per-faction protection windows with cooldown, role control, lock/reset, and restrictions. | mxf/shields.yml |
| Raid sessions | Attacker/defender sessions, phases, timers, activity refresh, reservations. | mxf/raids.yml |
| Raid alerts | Persistent aggregated alerts from safe detection signals and personal preferences. | Raid Alerts |
| Raid recaps | Cached battle reports from tracked raid/audit/analytics data without world scans. | mxf/raid-recaps.yml |
Analytics and Staff Tooling | System | Purpose | Safety model |
| Analytics | Persistent counters and snapshots from existing gameplay hooks. | No expensive command-time world scan. |
| Intelligence | Cached readiness score, strengths, weaknesses, trends, and recommendations. | Decision support, not anti-cheat evidence. |
| Audit logs | Durable faction, economy, staff, event, and system actions. | View-only operations are not spam logged. |
| Competitive rules | Definitions, cases, warnings, strikes, sanctions, evidence, notes, appeals. | Automatic detections default to alerts, not destructive punishment. |
| Investigations | Unified timeline/search/export over indexed audit activity. | Staff permissions required; private notes remain private. |
| Safe rollback | Preview, actor-bound confirmation tokens, conflict handling, history, undo. | No mutation before explicit confirmation. |
See Faction Intelligence, Investigations, and Safe Rollback.
Web Dashboard The web integration provides one-time in-game account linking, sessions, faction profiles, a secured API/backend bridge, and permission-aware views. Treat the web service as a separate deployment and follow Web Integration, Authentication, and Security.
Readiness Spigot 1.8.8 is the primary live-tested target. Complex multiplayer contests, third-party integrations, event restart edge cases, and modern server versions still require staging QA for the exact server stack. Beta-safe defaults intentionally keep destructive resets, broad automatic punishments, and unreviewed reward execution disabled.