Moderation Guide
Cases, commands, and when to use sushii vs. native Discord moderation
sushii keeps a running log of every moderation action in your server — whether you use sushii's commands or Discord's built-in tools. Every ban, kick, and timeout gets logged as a numbered case you can reference, edit, and pull up in a member's history.
Setup
Before anything else, point sushii at a private moderation log channel via
/settings → Logging → Mod Log Channel. Once set, every case will be
posted there automatically.
Native Discord actions are also logged
If you use Discord's built-in timeout, kick, or ban — and you added a reason in the audit log — sushii will pick up that reason automatically and log it as a case. Your existing moderation workflow keeps working and still gets tracked.
How cases work
Every action creates a case with a sequential number (e.g. "case #42"), posted to your mod log channel. Cases give you a permanent, searchable record of what happened and why.
/history— full moderation history for a member/reason— edit a reason after the fact; you can also click Edit Reason directly in the mod log entry/note— private mod note, never shown to the member or mentioned in any DM/uncase— permanently removes a case from a member's history
Uncase is permanent
/uncase cannot be undone. Use it only to remove cases that were created in
error, not to clean up a member's history before a ban appeal.
When to use native Discord vs. sushii commands
Both approaches log to the same place. Reach for sushii commands when:
- You need to act on multiple members at once (up to 25 in a single command)
- You want to DM the member a reason before kicking or banning them
- You need a ban that lifts automatically (
/tempban) - You're banning someone who's no longer in the server (
/banaccepts user IDs)
Otherwise, Discord's built-in tools work fine — sushii will pick up the action and log it as a case either way.
Taking action
Most commands accept multiple users in the users field (up to 25 at once).
Warnings and timeouts
/warn DMs the member by default — if the DM fails because they have DMs
closed, it's noted in the mod log. For single-user timeouts, Discord's native
tool works just as well since sushii logs it either way; use /timeout when
you need to act on multiple members at once.
Kicks and bans
sushii doesn't DM members for kicks or bans by default — add dm_reason:true
to notify the member with the reason before the action is taken. /ban accepts
user IDs for members who are no longer in the server. Use /tempban when you
want the ban to lift automatically; check active temporary bans with
/tempban-list.
Cross-server ban lookup
Checks whether a user ID appears in ban lists shared by other servers using sushii. Useful when vetting new members or checking if someone has been actioned elsewhere.
The command is available to servers that are Discord-discoverable with 1,000+ members, or that are Discord-partnered or verified.
Sharing is opt-in
By default, your server's name and ban reasons are hidden when other servers
run /lookup. To share them, enable /settings → Lookup → Lookup Data
Sharing. Both servers need to have this enabled before either can see the
other's details — if one hasn't, the entry shows as anonymous.
Cleanup
/prune deletes recent messages in the current channel — filter to a specific
user to clear a raider or spammer without removing everyone else's messages.
/slowmode sets or clears channel slowmode without going into channel
settings; pass 0 to disable.