Troubleshoot Missing Combat Alerts

A staff alert can be suppressed by recipient permissions, the viewer’s alert toggle, a target filter, or the alert cooldown. Check each setting before testing again.

When to use this guide

Use this guide when staff do not receive a combat alert that should appear.

Alert delivery checks

FairPlay sends alerts to online recipients who have fairplay.notify, or to a self-target when they have fairplay.notify.self. Alerts can also be disabled for a viewer, filtered by target, or delayed by the alert cooldown.

  • Online state: the recipient must be online when the alert is dispatched.
  • Permission branch: fairplay.notify, or self-target plus fairplay.notify.self.
  • Personal toggle: AlertsCommand manages per-viewer enable, disable, and toggle state, persisted in storage and resolved through getEffectiveAlertsEnabled against the configured default.
  • Target filter: a per-viewer alertsTarget filter can exclude the flagged player from that viewer’s alerts.
  • Alert cooldown: GlobalPunishmentsConfig declares alert-cooldown-ms with a 1,000 ms default, which throttles repeated staff messages for the same player and check.

Diagnostic sequence

  1. Confirm the affected staff member has fairplay.notify, or fairplay.notify.self when the flagged player is that staff member.
  2. Check the viewer’s alert toggle and enable alerts if needed.
  3. Review the viewer’s alertsTarget filter and clear or correct a filter that excludes the player.
  4. Wait through the configured alert-cooldown-ms (default 1,000 ms) before repeating a test.
  5. If the checks pass, run a controlled test with a cooperating player and review the server response.

Next step

If these checks do not resolve the issue, compare the installed configuration with the server’s current console output and follow the related troubleshooting guide.

Browse all documentation