Removing Message Content in AutoMod Gateway Events

[shaydewael]

The entry for this change is in the documentation: https://discord.com/developers/docs/change-log#message-content-in-automod-events

⚠️ Breaking Change to AUTO_MODERATION_ACTION_EXECUTION

As you probably know, in API v10+, the MESSAGE_CONTENT (1 << 15) intent is required for your app to receive message content. In alignment with this we're making a breaking change to AutoMod, which rolled out last week.

Message content is currently being exposed in the content and matched_content fields for AUTO_MODERATION_ACTION_EXECUTION gateway events, so we're updating its behavior to match other content fields across the API. Starting next week, apps using API v10+ will start receiving empty strings for content and matched_content unless the app has the MESSAGE_CONTENT intent.

What do I need to do?

If your app depends on matched_content or content in AUTO_MODERATION_ACTION_EXECUTION events, remove that dependency OR make sure your app is using the MESSAGE_CONTENT (1 << 15) intent.

When will the change go in effect?

The change will rollout next Monday, June 27. While we technically consider this a bug fix (as no message content should be exposed in API v10+), we realize it's also a breaking change so we're going to hold off deployment of the change until next week.

[UnbelievablyNoah]

swag :)

[seailz]

meow

[erkinalp]

Alternative: Make MESSAGE_CONTENT a precondition for automod policy execution intents.

[Zoddo]

There are use cases to receive automod execution events without the Message Content Intent. For example, to integrate Automod actions into a bot warning system.

[erkinalp]

@Zoddo AutoMod rejections leak information about message content, namely that the rejected message includes content unwanted in that channel.

[Zoddo]

You may know that the message contained, for example, a slur (you don't even know which one) but this won't let you know what the message was about (which is the point of the Message Content Intent).