ReactionBot Documentation
Supported AI Actions
Explore the ReactionBot actions currently supported through natural-language AI requests.
ReactionBot AI currently supports a focused set of Reaction Control actions. You can request these actions using normal language instead of entering the equivalent slash command and options manually.
Block an Emoji
ReactionBot AI can create a rule that blocks a specific emoji from being used as a reaction.
You can apply the rule to the current channel or across the entire server when the required Premium access is available.
Example: “Block the fire emoji in this channel.”
Example: “Block 😂 across the entire server.”
Unblock an Emoji
ReactionBot AI can remove an existing blocked-emoji rule.
Include the emoji and the scope of the rule you want to remove.
Example: “Unblock 🔥 in this channel.”
Example: “Remove the server-wide block on the puke emoji.”
Create an Allow Only Rule
Allow Only rules prevent members from using reactions other than the emojis you specify.
You can include one or several allowed emojis in the same request.
Example: “Only allow 👍 and 👎 in this channel.”
Example: “Make ✅ the only reaction members can use here.”
Clear an Allow Only Rule
ReactionBot AI can remove an existing Allow Only rule and return the affected scope to normal reaction usage.
Clearly identify whether you want to clear the rule from the current channel or across the server.
Example: “Clear the Allow Only rule in this channel.”
Example: “Let members use any emoji here again.”
Limit Reactions
ReactionBot AI can limit how many reactions each member may add to a message.
Include the maximum number of reactions and the intended channel or server-wide scope.
Example: “Limit everyone to one reaction per message in this channel.”
Example: “Set the server-wide reaction limit to three per member.”
Clear a Reaction Limit
ReactionBot AI can remove an existing reaction limit from a channel or server-wide configuration.
Example: “Remove the reaction limit from this channel.”
Example: “Clear the server-wide reaction limit.”
Restrict a Member
ReactionBot AI can prevent a specific member from adding reactions.
Include the member and the scope where the restriction should apply.
Example: “Restrict @User from reacting in this channel.”
Example: “Stop @User from reacting across the entire server.”
Timed Restrictions
ReactionBot AI can create a temporary reaction restriction when the equivalent timed restriction feature is available.
Include the member, duration, and intended scope in the request.
Example: “Restrict @User from reacting here for two hours.”
Example: “Stop @User from reacting server-wide for one day.”
Remove a Member Restriction
ReactionBot AI can remove an existing reaction restriction from a member.
Clearly identify the member and the scope of the restriction.
Example: “Unrestrict @User in this channel.”
Example: “Let @User react across the server again.”
Remove Existing Reactions
ReactionBot AI can remove matching reactions from existing messages using the ReactionBot removal system.
You can specify an emoji, channel, and supported date range to narrow the removal.
Example: “Remove all 🔥 reactions from this channel.”
Example: “Clear 😂 reactions posted today.”
Example: “Remove puke emoji reactions from the last seven days.”
Channel-Based Actions
Channel-based actions apply only to a selected channel and are useful when different areas of your server need different reaction rules.
Use wording such as “in this channel,” “here,” or mention a specific channel when supported.
Example: “Block 🔥 in #general.”
Server-Wide Actions
Server-wide actions apply across the server and may require ReactionBot Premium.
Use clear wording such as “server-wide” or “across the entire server.”
ReactionBot AI access does not bypass the Premium requirement attached to global Reaction Control features.
Multiple Emojis
Some actions can include more than one emoji in a single request.
Example: “Block 🔥, 😂, and 🤡 in this channel.”
Example: “Only allow ✅ and ❌ here.”
ReactionBot separates and validates the requested emoji changes before applying them.
Multiple Actions
You can combine different supported actions in one message.
Example: “Block 🔥 and limit members to one reaction per message in this channel.”
Example: “Unblock 😂, then only allow 👍 and 👎 here.”
Each action is checked independently for permissions, access, and required details.
Conversational Responses
ReactionBot AI can respond to normal conversation even when the same message also contains a supported action.
Example: “How are you? Also block the fire emoji here.”
The conversational response and moderation action are handled separately.
Actions Not Yet Supported
Not every ReactionBot command or dashboard feature is currently connected to ReactionBot AI.
Features outside the supported Reaction Control actions may still require their standard slash command or dashboard page.
AI support may expand as additional ReactionBot modules are integrated.
Permissions and Feature Access
Every AI action follows the same Discord permissions, role hierarchy, Free or Premium requirements, and safety checks as the equivalent command.
A correctly understood request may still fail when the user or ReactionBot lacks permission to complete it.
ReactionBot's response should explain when an action could not be performed.
Writing Reliable Requests
Include the action, emoji or member, scope, duration, limit, or date range required for the task.
A clear request such as “Restrict @User from reacting in this channel for two hours” is more reliable than “Stop them for a while.”
Always review the final response to confirm the correct changes were applied.
Next Steps
Continue to Example Prompts for ready-to-use examples covering individual actions, conversational requests, and multi-action messages.