ReactionBot Documentation

ReactionBot AI Limitations

Understand the current limitations of ReactionBot AI, including supported actions, permissions, request usage, and interpretation limits.

ReactionBot AI makes server management easier by translating natural-language requests into supported ReactionBot actions. However, it still operates within Discord permissions, ReactionBot feature availability, server configuration, and the limits of natural-language interpretation.

Supported Actions Only

ReactionBot AI can only perform actions that have been specifically connected to the AI system.

A request may describe a valid Discord moderation task but still be unavailable if ReactionBot AI does not currently support that action.

Unsupported requests will not be converted into unrelated commands or performed automatically.

Current Reaction Control Support

ReactionBot AI currently focuses on supported Reaction Control actions such as blocking emojis, unblocking emojis, configuring Allow Only rules, limiting reactions, restricting users, and removing reactions.

Additional ReactionBot modules and actions may be added to AI support over time.

Standard slash commands remain available for features that are not yet connected to ReactionBot AI.

Natural Language Can Be Ambiguous

ReactionBot AI interprets normal language, but unclear wording can produce an incomplete or uncertain request.

Prompts such as “block it,” “remove those,” or “restrict them” may not identify the correct emoji, member, channel, or scope.

Include specific details whenever possible to reduce the chance of misinterpretation.

Emoji Interpretation

ReactionBot AI can often understand an emoji by its symbol or common name, such as “fire emoji” or “puke emoji.”

Custom Discord emojis may require the actual emoji to be included in the request so ReactionBot can identify it correctly.

An uncommon nickname or vague description may not match the intended emoji.

Channel and Server Scope

ReactionBot may need to know whether an action should apply to the current channel or across the entire server.

When the scope is not clear, ReactionBot may use the current channel, ask for clarification, or refuse to perform the action.

Use wording such as “in this channel” or “server-wide” when the intended scope matters.

Premium Requirements Still Apply

ReactionBot AI does not remove the Free or Premium requirements attached to a feature.

A server-wide action that normally requires Premium will still require Premium when requested through ReactionBot AI.

AI access and Premium access are separate, so having one does not automatically unlock every feature included with the other.

Discord Permissions Still Apply

ReactionBot AI cannot bypass Discord permissions or perform actions that the requesting user is not authorized to use.

ReactionBot must also have the permissions required to complete the requested action.

A request may be understood correctly but still fail if either the user or ReactionBot is missing a required permission.

Role Hierarchy Still Applies

Actions involving another member remain subject to Discord role hierarchy.

ReactionBot cannot reliably manage a member whose highest role is positioned above the ReactionBot role.

The requesting moderator must also have the appropriate authority over the targeted member.

AI Requests Are Limited

Using ReactionBot AI may consume a request from the available AI balance or recurring allowance.

When no AI requests remain, new AI instructions cannot be processed until access renews or additional requests become available.

Standard ReactionBot slash commands continue to work according to the server's existing Free or Premium access.

One Message May Contain Multiple Actions

ReactionBot AI can separate multiple supported instructions from one message, but each action is interpreted and validated independently.

One action may succeed while another fails because of missing information, permissions, Premium access, or unsupported functionality.

Review the response carefully to see which actions were completed.

Complex Requests May Need Simplifying

Very long requests containing many conditions, exceptions, channels, members, or time periods may be harder to interpret reliably.

For complicated moderation changes, separating the request into smaller messages can make the intended result clearer.

You can also use the standard dashboard or slash commands when precise configuration is more important than conversational input.

ReactionBot Does Not Guess Sensitive Details

ReactionBot should not guess which member, emoji, channel, duration, or scope you intended when multiple possibilities exist.

When important information is missing, the request may be rejected or require a clearer follow-up message.

This helps prevent accidental server-wide rules or moderation actions against the wrong member.

Results Should Be Reviewed

Always review ReactionBot's response after submitting an AI request.

Confirm that the selected emoji, member, channel, duration, scope, and action match what you intended.

If the result is incorrect, use the appropriate command or dashboard setting to correct the configuration.

AI Availability

ReactionBot AI depends on the ReactionBot service being online and able to process AI requests.

Temporary service interruptions, Discord outages, or communication errors may prevent a request from being completed.

Retry the request later or use the equivalent slash command when available.

Next Steps

Continue to Troubleshooting for help with AI activation, missing permissions, failed actions, unclear responses, and unavailable requests.