Warnings & bans workflow
Record warnings and strikes, review escalation alerts, and manage bans.
Issuing a warning
Authorized staff can issue warnings through the moderation dashboard or /mod warn in Discord. Warning records include a timestamp and moderator attribution. Player DMs and staff notifications depend on moderation settings, available destinations, and successful delivery; recording a warning does not guarantee the player received a DM.
Escalation
The strike threshold defaults to three and is configurable. Reaching it can queue a staff alert when an alert destination is configured; it is not a documented three-warnings-in-30-days temp-ban rule. Review the record and use the appropriate ban controls. Separately enabled enforcement systems can apply automatic bans under their own rules, so REAPER does not guarantee human approval before every ban.
Audit trail
Moderation actions record attribution and audit information for staff review. Audit-log retention defaults to 365 days and can be changed by deployment configuration. Warning records, event history, and audit logs are separate records with different retention behavior; none of this promises a complete, searchable history forever.