Warnings
Key features
Moderator warning cases
Moderators can issue warnings with /warnings issue, including strike
value, reason, evidence, notes, and an optional moderation action.
Dashboard review and cleanup
Admins can page through warning history, filter by user, clear a single case, clear all warnings for a user, and edit warning policy from the web app.
Automatic strike policy
Warning config can require evidence, set maximum strikes, and trigger timeout, kick, or ban policy when strike thresholds are reached.
Join and leave behaviour
Nox can alert when a returning member has active strikes and can delete stored warnings when a member leaves if that policy is enabled.
Best for
Communities that need a consistent warning record before escalating moderation.
Staff teams that want warning cases available in both Discord commands and the dashboard.
Servers that want returning-member context instead of losing moderation history when someone leaves.
How it works
Admins configure warning policy
Staff set thresholds, evidence requirements, action channel behaviour, timeout duration, and optional automatic kick or ban thresholds.
A moderator issues a warning
/warnings issue opens a Discord modal. On submit, Nox validates the target,
strike, reason, evidence, notes, and selected action before creating the case.
Nox applies side effects
After the warning is stored, Nox calculates total strikes, executes the selected or automatic action, posts configured warning messages, sends audit alerts, and records activity or Errors-page entries.
Staff review or remove cases
Dashboard admins and Discord moderators can list, clear, or delete warning records. Member join and leave events apply the configured returning-member and leave-cleanup policy.
Setup checklist
Decide maximum strikes and whether evidence is required for every warning.
Configure the action channel if Nox should post warning report embeds or create warning threads.
Check auto-kick and auto-ban thresholds: kick must be lower than ban when both are enabled.
Confirm moderators have Administrator or Manage Messages permission for the warning commands and modal.
Grant the bot the moderation permissions needed for any selected timeout, kick, or ban actions.
Important notes
Warnings do not use scheduled jobs. Moderation actions run inline when a warning is issued.
If a timeout, kick, or ban fails, the warning can still be stored with an execution error and an Errors-page entry for staff to inspect.
Warning report messages and threads are optional Discord outputs. Clearing a warning deletes the stored record but does not clean up old Discord posts.
/warnings clearremoves all warnings for a user, while/warnings deleteremoves one case by case id.Join-with-strikes alerts skip bots and only fire when stored strikes exist for the returning non-bot member.
Troubleshooting
A moderator cannot use /warnings
Confirm the command is being used in a guild and the actor has Administrator or Manage Messages permission.
The warning was created but the action failed
Check bot role hierarchy and permissions for timeout, kick, or ban. The case can persist even when the Discord moderation action records an error.
Warning posts or threads are missing
Check the configured action channel, send/embed permissions, and thread permissions. Missing Discord messages do not prevent the warning record from existing.
Commands
The live slash-command reference from Discord, including options and default permissions.
/warnings clear
Clear all warnings for a member or raw user ID.
/warnings delete
Delete a single warning by case ID.
/warnings issue
Open the warning modal.
/warnings list
List warnings for a member or raw user ID.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
