⚖️ Blify Mod

Moderation tools (modlogs)

Commands for reviewing what the bot has done.

#/modlogs

View a user's AI moderation history in this server.

/modlogs user:@SomeMember

Requires Moderate Members. Returns up to the last 10 entries, with:

  • When the action happened (relative timestamp)
  • The action taken and (for timeouts) the duration
  • The severity (1–5)
  • The rule that was broken and the bot's reasoning
  • Whether the action was reversed, and by whom

Below the list, a footer shows the total count — if the user has more than 10 entries, only the most recent 10 are displayed.

#Reversing actions from log embeds

Every moderation log entry for a timeout or a ban has a Reverse button at the bottom of the embed. Clicking it requires the Moderate Members permission.

Reversing:

  • Timeout — removes the timeout immediately.
  • Ban — unbans the user.

The log embed turns green with a "Reversed by @X" line, and the entry in /modlogs is annotated with (reversed by @X) for future reference.

delete, warn, and kick actions are not reversible from the embed:

  • A deleted message can't be un-deleted.
  • A warning was a one-shot public ping.
  • A kicked user just needs to be re-invited; the bot can't do that for you (and Discord wouldn't allow auto-rejoining anyway).

#When the log embed shows "Failed"

If the bot decided on an action but couldn't apply it, the embed is orange and shows Failed: <reason>. The most common reason is Missing Permissions — the bot's role is below the offender's. See Troubleshooting.