Skip to content

3.1.0 — Moderation logging, native command permissions, and fixes

Choose a tag to compare

@badBlackShark badBlackShark released this 11 Jul 23:32
ef7bba4

Added

  • Member timeouts, kicks and bans are logged to the activity log, as toggleable events under a new Moderation group on the logging page. Each entry shows the affected user, the moderator, and the reason (via the guild audit log). (#126)
  • Server Shield can apply a distinct, harsher punishment to images matching a scam confirmed on your own server, overriding the general image-scan punishment. Defaults to reusing the general punishment. (#135)
  • Per-server "Ping staff on alerts" toggle on the Server Shield page. On by default; when off, alerts still post to the log channel without pinging. (#134)
  • The moderation page warns when the configured staff role lacks Manage Messages, which would silently hide staff commands from its members. (#129)

Changed

  • Command permissions now defer to Discord's native permission system. A Server Settings → Integrations override granting a role access to a command is respected at runtime, instead of being vetoed. (#128)
  • The server switcher now appears on every plugin config page, not just the dashboard. (#133)

Fixed

  • Guild commands (/ping, the "Report as scam" context menu) now register on real servers, filtered by each server's enabled plugins. Previously they only registered on the dev test server, so no guild command existed in production. (#127)
  • Inviting shrkbot from the website now grants its permissions and creates its managed role, deferring to the app's configured install settings. (#125)
  • Config changes saved on the website no longer fail during a Redis outage, and the bot resubscribes to the config bus automatically after Redis drops. (#131)
  • Fixed the vertical alignment of the "within" connector between the spam-guard number steppers. (#130)

Full changelog: CHANGELOG.md