Reaction Control Limitations

ReactionBot can only moderate reactions in channels where it has the required Discord permissions.

If View Channels, Read Message History, or Manage Messages are missing, Reaction Control may not function correctly.

ReactionBot cannot moderate reactions in channels it cannot access.

If the bot cannot view a private channel, it will be unable to monitor or remove reactions there.

Discord allows permissions to be overridden on individual channels.

Even if ReactionBot has the correct permissions at the server level, a channel-specific override can prevent moderation from working in that channel.

ReactionBot only moderates reactions that match your configured rules.

If no Block, Allow Only, Limit Reaction, or Restrict User rule applies, the reaction will be left unchanged.

Global Rules apply across your server unless a channel has Ignore Global enabled.

Channels using Ignore Global rely only on their own Channel Rules.

Reaction Control evaluates reactions as they are added.

Existing reactions that were placed before a rule was created are not automatically removed.

If needed, existing reactions can be removed using the appropriate moderation tools.

ReactionBot relies on Discord's API to receive reaction events.

During Discord outages or temporary API issues, reaction moderation may be delayed until services return to normal.

Test new rules after creating them to ensure they behave as expected.

Keep ReactionBot's permissions consistent across your server to avoid unexpected behavior.

Use Global Rules for common moderation and Channel Rules only where different behavior is required.

If Reaction Control is not behaving as expected, first verify that the required permissions are present.

Next, confirm that the appropriate rules exist for the affected channel.

Finally, run /diagnose to identify common configuration or permission issues.