Staff Commands#

/ff (alias /flagforge):

Command Permission Purpose
/ff status flagforge.command.status Plugin, storage, packet adapter, queue, and Discord status, and whether a newer FlagForge release is out
/ff checks [category] flagforge.command.status List registered checks: category, evidence class, EXPERIMENTAL flag, and whether repeated internal errors auto-disabled it
/ff check <id> <enable\|disable> flagforge.command.reload Toggle one check at runtime without a full reload (see the Check Parameter Reference for every check ID)
/ff alerts [on\|off] flagforge.alerts Toggle your personal in-game staff alerts
/ff inspect <player> flagforge.command.inspect Live profile: game mode, world, exemptions, violation state
/ff history <player> [page] flagforge.command.history Persisted finding history for a player
/ff finding <id> flagforge.command.history Full structured evidence for one finding (see Data Model § ff_findings for every field)
/ff reload flagforge.command.reload Atomically reload checks.yml/actions.yml; last-valid config stays active on error
/ff exempt <player> <check:id\|category:name\|type:name> <duration> <reason> flagforge.command.exempt Grant a temporary, scoped exemption (player must be online)
/ff unexempt <player> <check:id\|category:name\|type:name> flagforge.command.exempt Revoke a matching active exemption early
/ff vl <player> clear <check:id\|category:name\|all> <reason> flagforge.command.vl Clear accumulated violation level
/ff enforcement <on\|off> <reason> flagforge.command.enforcement Toggle the global enforcement circuit breaker live
/ff purge player <name> confirm / /ff purge before <ISO-8601> confirm flagforge.command.purge Permanently delete stored findings (two-step confirmation)
/ff discord status / /ff discord test flagforge.command.discord Discord routing/queue status, and a labeled test alert
/ff correlations flagforge.command.correlations List configured correlation rules, their thresholds, and whether a command is set (never the command text); flags rules whose confidence requirement is currently unreachable (see Configuration § actions.yml for the rule shape)

Every mutating command writes an audit-log entry (who, what, when, target, and outcome) to the database's ff_audit_log table — see Data Model § ff_audit_log.

Permissions#

  • flagforge.admin (default: op) grants every command above except check bypass.
  • flagforge.alerts and flagforge.alerts.<category> (default: op) gate in-game alert delivery, overall and per category (economy/inventory/movement/combat/world/packet).
  • flagforge.notify.update (default: op) shows a chat line on join when a newer FlagForge release is available (see Configuration § Update check).
  • flagforge.bypass and flagforge.bypass.<category> (default: false, never granted implicitly — not even to operators) exempt the holder from all/one category of checks. Grant these only to accounts that genuinely need to bypass detection (e.g. a build-team alt), never as a side effect of flagforge.admin.