Skip to main content
Not every disciplinary action is the same — staff infractions are a distinct layer of accountability designed specifically for your team. The /infract command lets administrators issue formal, trackable infractions that are kept separate from standard member warns, giving you a clean and private record of staff conduct.

​
Description

The /infract command issues a formal infraction to a specified server member and logs it in Burger Bot’s infraction system. Unlike general member warns, staff infractions are administrator-only records, making them ideal for documenting policy violations, performance issues, or misconduct within your staff team. Infractions can be assigned a severity level to reflect the seriousness of the incident.

​
Usage

/infract @user [reason] [severity]

​
Parameters

​
user
@mention
required
The server member receiving the infraction. Must be an @mention of a valid server member.
​
reason
string
required
A clear description of why the infraction is being issued. This is stored in the log and visible when reviewing infraction history with /infractions.
​
severity
string
The severity level of the infraction. Accepted values are low, medium, or high. Defaults to low if not specified.
ValueUse Case
lowMinor policy violations or first-time offenses
mediumRepeated behavior or moderate misconduct
highSerious violations warranting immediate review

​
Permissions Required

RoleAccess
Administrator✅ Full access
Configured Admin Role✅ Full access
Staff (below Admin)❌ No access
Infractions are not the same as regular member warns. They exist in a separate log visible only to administrators. Do not use /infract for general community moderation — use your standard warn system for that.

​
Example Usage

/infract @Jordan Missed two consecutive staff meetings without notice. severity:medium
This logs a medium severity infraction against @Jordan with the provided reason, timestamped and attributed to the issuing admin.
Always write a descriptive, specific reason when issuing infractions. Vague entries like “bad behavior” are harder to act on during staff reviews. Clear records protect both the staff member and your leadership team.
Infractions can be reviewed at any time using the /infractions command. Administrators can view all infractions for a specific member or pull the full server infraction log.