⚖️ Blify Mod

Setup commands

The commands you'll use to get the bot running and tune its behavior. All of them require the Manage Server permission.

#/enable

Turn the bot on for the current server. The bot is disabled by default in every new server it joins — nothing will happen until you run this.

/enable

Idempotent — running it when already enabled gives a friendly "already on" reply.

#/disable

Turn the bot off without losing any settings. Useful for temporary maintenance or pausing during events.

/disable

Your config (channels, rules, immunity, etc.) is preserved — /enable will pick up exactly where you left off.

#/setmodchannels

Pick the channels the bot will actively moderate. Up to 3 on Free, 10 on Pro/Premium.

/setmodchannels channel1:#general channel2:#off-topic channel3:#help
  • Run with no channel arguments to clear the list. The bot then only acts when @mentioned.
  • Channels not in this list are completely ignored — no AI calls, no costs, no privacy concerns.
  • The command overwrites the existing list. If you want to add one channel, you need to re-list the existing ones too.

A confirmation prompt appears if you're significantly changing the list, to prevent accidental wipes.

#/setlogchannel

Set the channel where moderation actions are logged.

/setlogchannel channel:#mod-logs

Each log entry is an embed with:

  • The user, action taken, severity (1–5), rule broken, and the bot's reasoning
  • The first 1000 characters of the offending message
  • A Reverse button for timeouts and bans (gated by Moderate Members)

Run with no channel to disable logging. Strongly recommended you keep one set, especially in dry-run mode.

#/setrules

Manage custom rules. The bot will only enforce the rules in this list (or, if you've never customized, the default ruleset).

/setrules add title:"No alt accounts" description:"One account per person."
/setrules remove number:3
/setrules list
/setrules clear
  • Limits: 5 rules on Free, 20 on Pro/Premium.
  • Adding any custom rule replaces the default ruleset entirely. /setrules clear reverts to defaults.
  • New rules are checked against three things before being saved:
    1. Duplicate title — rejected.
    2. Multi-rule submission — if it bundles two unrelated topics (e.g. "no politics AND no spam"), it's rejected with a 30-second cooldown.
    3. Policy check — rules that would force the bot to itself break Discord's rules (e.g. "promote hate speech") are rejected. Rules banning anything are fine.

#Writing good rules

  • Specific beats vague. "No targeted insults at other members" works better than "Be nice."
  • Add a description. It's optional, but the model uses it as additional context.
  • Don't overlap. If you add "No spam" and "No flooding" as two rules, the bot may get confused about which to cite.
  • Mirror your written server rules. Most servers just translate their existing rules-channel into 5–20 entries.

#Default rules

If you never call /setrules add, the bot uses these:

  1. No harassment or hate speech
  2. No NSFW or disturbing content
  3. No spam or flooding
  4. No doxxing or personal info
  5. No unsolicited advertising
  6. No illegal content
  7. No excessive profanity or directed insults
  8. No threats or encouragement of self-harm

#/setstrictness

Cap the worst action the bot is allowed to take.

/setstrictness level:low      # warnings only
/setstrictness level:medium   # adds timeouts; never kicks/bans
/setstrictness level:high     # full ladder (default)

Strictness only ever softens decisions — it never escalates them. A "warn" decision stays a warn regardless of setting.

Set a URL the bot will include in its DM to users who get timed out or banned.

/setappeallink url:https://forms.gle/your-appeal-form
  • Must be http:// or https://.
  • Run with no URL to clear it.
  • Only shown for timeout and ban actions — warnings and deletes don't include it.

#/dryrun

Toggle dry-run (log-only) mode.

/dryrun mode:on
/dryrun mode:off

When dry-run is on, the bot still scans messages and decides what to do, but:

  • No action is applied (no delete, timeout, kick, or ban)
  • No DM is sent to the user
  • The log channel gets a 🔵 Dry Run — would have taken action entry instead

This is the recommended way to roll the bot out for the first day or two. If you turn it on without a log channel set, the bot warns you to set one — the dry-run logs are useless without somewhere to read them.

#/modconfig

Show the current configuration at a glance — status, dry-run flag, moderated channels, log channel, rule count, strictness, appeal link. Ephemeral (only you see it).

/modconfig

Use this as your first stop when "the bot isn't doing X" — most issues are visible from the output.