Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/onesoft-sudo/sudobot/llms.txt

Use this file to discover all available pages before exploring further.

Every moderation action SudoBot takes — whether triggered by a command or by an auto-moderation rule — creates an infraction record in the database. Infractions give your moderation team a permanent, searchable audit trail so you can review a member’s history, update records when context changes, and ensure consistent enforcement.

​
What creates an infraction

The following actions automatically generate an infraction:
ActionInfraction type
banBAN
Temp-ban (ban with duration)TEMP_BAN
unbanUNBAN
kickKICK
mute (Discord timeout)MUTE
unmuteUNMUTE
warnWARNING
noteNOTE
beanBEAN
shotSHOT
Mass ban (massban)MASS_BAN
Mass kick (masskick)MASS_KICK
Auto-moderation actionsVaries by action type
You can also create infraction records manually with infraction create — for example, to document an action that was taken outside of the bot.

​
Viewing infractions

1

View a single infraction

Use the numeric infraction ID shown when the action was taken, or find it via infraction list:
/infraction view id:42
The bot replies with a detailed embed showing the type, target user, moderator, reason, timestamp, and duration (if applicable).
2

List all infractions for a user

/infraction list user:@Username
The list is paginated and shows each infraction’s ID, type, reason, and date. You can also use the alias infraction ls.
3

View an attachment

Some infractions include file attachments (for example, a screenshot submitted with a report). Retrieve the attachment with:
/infraction attachment id:42
The ID format is <infraction_id> for the first attachment, or <infraction_id>!<index> for subsequent ones.

​
Editing infractions

You can update the reason or duration of an existing infraction without deleting and re-creating it. 
/infraction reason id:42 reason:Updated after review
This changes the stored reason text on infraction 42. The change is logged but does not resend any DM to the user.

​
Deleting infractions

Deleting an infraction is permanent and cannot be undone. Use this only to remove records that were created in error.
/infraction delete id:42
Alias: /infraction d 42

​
Creating infractions manually

Use infraction create to add a record without taking a live moderation action. This is useful for documenting warnings that were issued verbally or through another channel. 
/infraction create user:@Username type:WARNING reason:Verbal warning issued in voice chat
You can optionally set a duration (for record-keeping only) and choose whether to notify the user via DM.

​
Clearing all infractions for a user

/infraction clear user:@Username
This permanently removes every infraction record for the specified user. Use this when a member has a clean slate after a long period of good behavior, or when records were created in error.

​
Infraction command reference

The root command is infraction (aliases: inf, infs, infractions). The required Discord permissions are Manage Messages or View Audit Log (either one is sufficient).
SubcommandAliasDescription
infraction create—Manually create a new infraction record.
infraction view <id>—Show full details for one infraction.
infraction list <user>lsList all infractions for a user.
infraction delete <id>dPermanently delete one infraction.
infraction reason <id> <reason>—Change the reason on an infraction.
infraction duration <id> <duration>—Update the recorded duration.
infraction clear <user>—Delete all infractions for a user.
infraction attachment <id>viewfile, fileView an attached file on an infraction.
The infraction command also accepts the shorter aliases s (summary) for listing and ls as a shorthand for list. These aliases are mapped to the same underlying handler as the full subcommand names.

Build docs developers (and LLMs) love

Get started for freeTalk to us