Admin Guide

• Silencing a false positive for one player: /ff exempt <player> check:<id> 30m "reason" (player must be online). Use category:MOVEMENT or a wider scope only when several related checks are all firing on the same legitimate behavior.
• A check is too sensitive server-wide: edit its parameters in checks.yml (see the Tuning Guide) and /ff reload — no restart needed. Invalid YAML or an out-of-range value disables only that one check with a logged reason; the rest of the snapshot still loads.
• A check keeps producing findings you disagree with, permanently: /ff check <id> disable. This is instant and doesn't require editing a file, but doesn't survive a /ff reload/restart unless you also update checks.yml — the file is the durable source of truth.
• A check is crashing: FlagForge automatically disables any check after 5 consecutive internal exceptions and logs it at SEVERE (/ff checks shows DISABLED (repeated internal errors) next to it) — this is a bug, please report it. /ff reload or re-enabling the check gives it a fresh start once the underlying issue is fixed.
• Emergency stop: /ff enforcement off "reason" disables every preventable response server-wide immediately, without touching detection/alerting/checks.yml. Detection keeps running so you don't lose evidence while investigating.
• Clearing a bad decision: /ff vl <player> clear check:<id> "reason" (or category:<name> or all) resets accumulated violation level without touching stored history.