Skip to main content
Maintaining accountability within your staff team requires a reliable paper trail. The /infractions command gives administrators full visibility into the infraction history for any member — or the entire server — so you’re always equipped with the information needed to make fair, informed decisions.

Description

The /infractions command retrieves the infraction log stored by Burger Bot. When a user is specified, it returns every infraction on record for that member, including dates, reasons, severity levels, and the administrator who issued each one. When called without a user, it returns the complete server-wide infraction log. Access is intentionally restricted to administrators to maintain confidentiality.

Usage

/infractions [@user]

Parameters

user
@mention
The staff member whose infraction history you want to review. If omitted, Burger Bot returns the full server-wide infraction log.

Permissions Required

RoleAccess
Administrator✅ Full access
Configured Admin Role❌ No access
Staff Role❌ No access
Regular Members❌ No access
The /infractions command is restricted to Administrators only. This is intentional — infraction records are sensitive personnel data and should not be accessible to general staff members.

What the Log Shows

Each infraction entry in the log includes the following details:
  • Infraction Date — When the infraction was issued
  • Reason — The description provided at the time of the infraction
  • Severitylow, medium, or high
  • Issued By — The administrator who submitted the infraction

Example Usage

View a specific member’s infractions:
/infractions @Jordan
View the full server infraction log:
/infractions
Pulling a member’s full infraction history before a staff review or promotion decision gives you a complete picture of their conduct over time. Consistent medium or high severity entries are a strong signal worth discussing with your leadership team.
Infraction records are separate from standard member warns. If you’re looking for general moderation history, check your server’s warn log instead. Infractions are exclusively for staff conduct tracking.