Feature Setup / MxF Factions
Configure staff visibility, audit history, competitive rule cases, investigations, and preview-first rollback.
Docs version
v1.0.0-dev
Product version
1.0.0-dev
Last updated
Jul 21, 2026
This layer gives staff the operational visibility needed to run a competitive server: analytics, intelligence, audit logs, rule cases, investigations, and rollback.
mxf/analytics.yml
mxf/intelligence.ymlmxf/audit.yml
mxf/competitive-rules.yml
mxf/rule-definitions.yml
mxf/investigations.yml
mxf/rollback.yml
menus/analytics.yml
menus/intelligence.yml
menus/investigations.yml
menus/rollback.yml
1. Enable analytics categories that matter for your season.
2. Configure snapshot interval, retention, and intelligence scoring weights.
3. Configure audit categories and avoid logging low-value menu views.
4. Create rule definitions with categories, display text, detection mode, expiration, and staff action guidance.
5. Keep automated rule detection in alert-only mode until staff trusts the signal.
6. Configure investigation indexes, exports, and retention.
7. Configure rollback handlers, conflict policy, token expiry, and owner-only confirmations.
/f analytics
/f intelligence
/f intelligence <faction>
/f intelligence guide
/f logs
/f rules list
/f rules history
/f rules sanctions
/f investigate recent [category] [page]
/f investigate faction <faction> [page]
/f investigate player <player> [page]
/f investigate event <eventId>
/f rollback preview <eventId>
/f rollback confirm <token>Real actions should create readable history. Private staff notes should stay private. Rollback preview should never mutate data until a permitted staff member confirms the exact token.