This is an archived community post.

This post is no longer open for new replies - but we'd still love to hear from you! Share your feedback with our team via our Feedback Form.

Need help getting started? Check out this article for step-by-step instructions on submitting feedback through the form.

Automod and Content Moderation Beta Feedback

Cleyvour
  • Edited

As the automod rolls out, it has become clear that circumventing the filter is not difficult, so the tool isn't particularly useful. However, it could be far more useful with just a little effort. I would love to see the following additional responsive actions added to the content moderation filter moving forward.

  • Ping a specific a role (I want my mods to be automatically notified when someone says a slur, and they do too)
  • Timeout the user (I don't want them trying to circumvent the filter once they know it exists)
  • Kick the user (if I get an exact detection for the n-word, I just don't want them in my server anymore)
  • Ban the user (same rationale as kicking the user)

Thank you for your consideration.

0

Comments

1 comment

Date Votes
  • Hyperion

    To add to this, the option to apply ONLY to a selected channel would be nice to better target specific channels instead of going through and whitelisting multiple channels. This would be useful as ticket channels can not be whitelisted and if I'm restricting ban talk, but I want them to be able to freely discuss their game bans in tickets that would be the prefered way to do it.

    I.e. I only apply the filters to certain public channels so I do not have to worrie about whitelisting the entire rest of the discord.

    0