ReactionBot Documentation
Example AI Prompts
Explore example prompts you can use to control ReactionBot, manage reactions, and combine multiple actions using natural language.
ReactionBot AI allows you to describe what you want in normal language instead of memorizing exact slash commands. Your prompt can be short and direct, conversational, or contain multiple supported actions in the same message.
Blocking Emojis
Use a simple prompt to prevent an emoji from being used as a reaction in a channel or across your server.
Example: “Block the fire emoji in this channel.”
Example: “Stop people from using 😂 as a reaction here.”
Example: “Block the puke emoji across the entire server.”
Unblocking Emojis
You can ask ReactionBot AI to remove an existing blocked-emoji rule without remembering the exact unblock command.
Example: “Unblock the fire emoji in this channel.”
Example: “Allow people to use 😂 again.”
Example: “Remove the server-wide block on the puke emoji.”
Allowing Only Certain Emojis
Allow Only rules restrict reactions so members can use only the emojis you specify.
Example: “Only allow 👍 and 👎 in this channel.”
Example: “Make this channel voting reactions only.”
Example: “Only let members react with the green checkmark.”
Limiting Reactions
Use ReactionBot AI to limit how many reactions a member can add to a message.
Example: “Limit everyone to one reaction per message in this channel.”
Example: “Only allow two reactions per person here.”
Example: “Set a server-wide reaction limit of three per user.”
Restricting Members
ReactionBot AI can restrict a member from adding reactions when you provide the member and the intended scope.
Example: “Stop @User from reacting in this channel.”
Example: “Restrict @User from adding reactions across the server.”
Example: “Prevent @User from reacting here for two hours.”
Removing Reactions
You can ask ReactionBot AI to remove matching reactions from messages using normal language.
Example: “Remove all fire reactions from this channel.”
Example: “Clear 😂 reactions posted today.”
Example: “Remove the puke emoji reactions from the last seven days.”
Conversational Prompts
Your request does not need to sound like a command. ReactionBot can understand conversational wording when the intended action is clear.
Example: “People keep spamming the fire emoji. Can you block it here?”
Example: “I only want members choosing yes or no on these messages.”
Example: “Can you stop @User from reacting in this channel for a while?”
Multi-Action Prompts
ReactionBot AI can understand prompts that contain more than one supported request. It can also respond conversationally while completing an action.
Example: “What’s up? Block the puke emoji in this channel.”
Example: “Block 🔥 and limit everyone to one reaction per message.”
Example: “Unblock 😂, then only allow 👍 and 👎 here.”
Example: “Say hello, block the fire emoji, and restrict @User from reacting for one hour.”
Adding Useful Details
Clear prompts produce the most reliable results. Include the emoji, member, channel, duration, date range, or server-wide scope when those details matter.
Instead of saying “Block that emoji,” say “Block the fire emoji in this channel.”
Instead of saying “Restrict them,” say “Restrict @User from reacting here for two hours.”
Instead of saying “Remove reactions,” say “Remove all 😂 reactions from this channel posted today.”
When ReactionBot Needs More Information
ReactionBot may ask a follow-up question when your prompt does not include enough information to safely perform the action.
For example, a request such as “Restrict him” may be unclear if no member or duration was provided.
Reply with the missing detail, or resend the request with the member, emoji, channel, duration, or scope included.
Important Notes
ReactionBot AI follows the same permissions, Premium requirements, role hierarchy, and feature limitations as the equivalent ReactionBot commands.
Using different wording does not allow a user to bypass server permissions or access features that are unavailable on the server’s current plan.
Always review ReactionBot’s confirmation message to make sure the correct action and scope were applied.
Next Steps
Continue to Multi-Action Requests to learn how ReactionBot separates, validates, and performs multiple instructions from one message.