Skip to main content
Keep your server’s disciplinary records clean and consistent with /warn. Every warning Burger Bot issues is permanently logged against a member’s profile, giving your moderation team a clear, auditable history before escalating to timeouts, kicks, or bans.

​
Description

The /warn command issues a formal warning to a server member and records it in Burger Bot’s moderation log. Warnings are visible to any moderator via /warnings and persist on the member’s record until manually cleared with /clearwarn. You can configure Burger Bot to automatically apply escalating punishments — such as a timeout or kick — when a member accumulates a set number of warnings.

​
Usage

/warn @username Spamming in general

​
Parameters

​
user
@mention
required
The server member you want to warn. Must be an @mention of a current member of your server.
​
reason
string
A brief explanation of why the warning is being issued. Recorded in the warning log and visible to other moderators. While optional, providing a reason is strongly recommended for a clean audit trail.

​
Permissions Required

RoleAccess
Moderator or higher✅ Can issue warnings
Regular members❌ No access

​
Example Usage

Warn a member for spamming: 
/warn @ChaosGremlin Spamming in #general
Warn a member without a reason: 
/warn @ChaosGremlin
Warn a member for inappropriate content: 
/warn @ChaosGremlin Posting NSFW content in non-NSFW channels
Always include a reason when issuing a warning — it helps other moderators understand the context of a member’s record at a glance, and ensures consistency if your team ever reviews past moderation actions.
Warnings accumulate on a member’s record over time. If you’ve set up warning threshold auto-actions in Burger Bot’s configuration, reaching a defined number of warnings will automatically trigger the next punishment level (e.g., timeout at 3 warnings, kick at 5). Review your server’s auto-action settings to make sure thresholds are tuned to your community.