Set up Discord webhook and bot for Bee Swarm Simulator

Revolution Macro makes it easy to monitor what’s happening without having to watch your PC directly. This guide will walk you through setting up your own Discord server, a status channel, and a webhook so that Revolution can post hourly graphs and regular updates about your macro’s activities. You can set up a bot on that same server if you want to start, pause, or stop from your phone.

Before you start

• Use the Discord desktop app or browser. You need a server which you have administrator permissions in - your own private server is enough. Keep the bot in a private channel so strangers cannot run remote commands.
• Set up the webhook first, in Discord and then in Revolution. You can set up a bot afterward only if you also want remote start, pause, or stop.
• Webhook covers status and hourly reports. Bot is optional and adds remote commands.
• Treat webhook URLs and bot tokens like passwords. Do not paste them in public chats.

Steps

Set up Discord for webhooks

Use one private server for macro reports. These steps create the channel and webhook URL you paste into Revolution later.

1. In Discord, click the + in the left server list.

   

   

2. Choose Create My Own, then For me and my friends.

   

   

3. Name the server (for example Revolution Macro) and click Create.

   

   

4. Add a text channel for macro reports. Click the + next to Text Channels (or rename the default #general channel). Name it something like status so it shows as #status.

   

   

5. Click #status so it is selected in the channel list.

   

   

6. Open that channel’s settings. Go to Integrations → Webhooks → New Webhook (or Create Webhook). Set the name and channel, then click Copy Webhook URL.

   

   

Configure Status → Webhook in Revolution

You’ve got the webhook URL on your clipboard. Paste it into Revolution and start the macro to see your first report.

1. In Revolution, open Status → Webhook. The mode selector shows Disabled, Webhook, and Bot.

   

   

2. Select Webhook. Webhook URL and Ping ID appear, each with a paste icon on the right.

   

   

3. Click the paste icon next to Webhook URL (or paste into the field) so the URL from Discord is filled in. Mask the URL if you share a screenshot.

   

   

4. Optional: with Developer Mode on in Discord, right-click your username and choose Copy User ID. Click the paste icon next to Ping ID so disconnect and error messages can mention you.

   

   

5. Start the macro. Discord shows a Revolution Macro startup embed with Macro Version, Account, and Start Time, and later posts [HH:00:00] Hourly Report with the honey or buff graph.

   

   

Add a Discord bot for remote control

Skip this section if you only need webhook reports. When you want remote start, pause, stop, or /help from Discord, create a bot app, invite it to the same private server, then paste its token and channel into Revolution. Anyone who can message the bot channel can run remote commands, so keep the bot on your private server.

1. In a browser, open the Discord Developer Portal. Click New Application, name it (for example Revolution Macro), check the Developer Terms checkbox, and click Create.

   

   

2. Open Installation. Under Default Install Settings → Guild Install, open Scopes and add bot (keep applications.commands if it is already listed).

   

   

3. In Permissions, enable View Channels, Send Messages, Read Message History, Embed Links, and Attach Files. Click Save Changes if Discord shows it.

   

   

4. Copy the Install Link on the Installation page. Open it in a new tab, choose your private macro server, and authorize the bot.

   

   

5. Back in Discord, open your server and confirm the bot appears in the member list.

   

   

6. In Discord, open User Settings → Advanced and turn on Developer Mode (you need this for Copy Channel ID in step 9).

   

   

7. On the Developer Portal Bot tab, click Reset Token, confirm, and copy the token. Never share this token. You’ll paste it into Revolution in the next step.

   

   

8. In Revolution, open Status → Webhook, select Bot, and click the paste icon next to Bot Token to paste the token while it is still on your clipboard.

   

   

9. Back in Discord, right-click #status, choose Copy Channel ID, and keep it on your clipboard for Bot Channel.

   

   

10. In Revolution, click the paste icon next to Bot Channel and paste the channel ID.

    

    

11. Click Advanced (gear) next to Bot Token. On General, leave Slash Commands on unless you prefer prefix commands.

    

    

12. Wait a moment. Discord shows Connected to Discord.

    

    

13. In that channel, run /help. The bot lists commands such as start, pause, stop, screenshot, and report.

Prefix commands instead of slash

Leave Slash Commands on under Advanced → General (default). If you turn slash off, set Command Prefix (default !) and use commands like !help. Prefix commands also need Message Content Intent on in the Discord Developer Portal Bot tab. Turn it on and click Save Changes if Discord asks you to.

Discord Developer Portal Bot tab with Message Content Intent on

Bot Advanced options

After the bot connects, open Advanced (gear) next to Bot Token when you need more than the default setup.

Separate channels for reports and errors

By default, everything lands in Bot Channel. Open Advanced → Channels when you want hourly graphs, error lines, balloon alerts, and general status in different Discord channels. For example, use #reports for graphs and #errors for failures so a busy #status feed stays readable.

Paste a channel ID into Reports, Errors, Balloons, or General. Leave a field empty to keep that traffic on Bot Channel.

Advanced Discord settings Channels tab with routing fields

Discord pings when something breaks

Open Advanced → Pings when you want Discord to @ you (or another account) on disconnects, reconnect failures, unexpected deaths, or a missing planter. That is useful when you are away from your PC and need a phone alert instead of scrolling the channel.

Set Ping User ID as the default mention. Turn on only the events you care about. Each event also has an Override ID where you can paste a different user ID for that specific event, which is handy when disconnect pings should go to you but planter alerts should go to someone else. When Override ID is empty, Ping User ID (or Ping ID on the main Status → Webhook form) is used instead.

Advanced Discord settings Pings tab with event toggles

Restrict who can run bot commands

Open Advanced → Permissions and turn on Enable Whitelist when the bot is on a shared server and you do not want every member to run /start or /stop. Add the Discord user IDs that are allowed. Everyone else is ignored.

Skip this on a private server you alone control.

Advanced Discord settings Permissions tab with Enable Whitelist

More settings

Discord

Status → Webhook

Chooses Disabled, Webhook, or Bot. Use Webhook for status graphs and alerts. Switch to Bot only when you need remote Discord commands. Paste icons next to Webhook URL, Bot Token, Bot Channel, and Ping ID read from your clipboard.

Disable Reporting

Settings → Macro → Reports

When on, hourly Discord stats reporting is skipped. Turn off if you want hourly reports in Discord.

Disable Item Tracking

Settings → Macro → Reports

When on, post-gather inventory scans and item reports are skipped. Turn off if you want item reports after long gathers. Item reports also need Webhook or Bot mode on Status → Webhook and a gather of at least about 180 seconds.

Settings Macro Reports with Disable Reporting and Disable Item Tracking

Discord Rich Presence

Settings → Macro → Misc

Updates your Discord presence with macro status such as Running, Paused, or Stopped. Status refreshes about every 15 seconds while active. Updates only after the prompt has been shown and Discord Rich Presence is turned on. Toggling it is blocked for about 6 seconds after each change.

Settings Macro Misc with Discord Rich Presence

Slash Commands

Status → Webhook → Advanced → General

Defaults on. When on, use slash commands in Discord instead of prefix commands.

Command Prefix

Status → Webhook → Advanced → General

Defaults to !. Used when Slash Commands is off (!help lists commands).

Troubleshooting

Invalid webhook URL for startup message!

Cause: Status → Webhook is set to Webhook, but the URL in Webhook URL cannot be parsed.

Fix:

1. Paste a full webhook URL into Status → Webhook → Webhook URL (from the channel’s Integrations → Webhooks). Use the paste icon next to the field if the URL is already on your clipboard.

No startup embed or hourly report

Cause: Status → Webhook is Disabled, Disable Reporting is on, or reporting stops before the hour changes.

Fix:

1. Open Status → Webhook and select Webhook or Bot.
2. Confirm Webhook URL (or Bot Token plus Bot Channel) is filled and saved.
3. Open Settings → Macro → Reports and turn Disable Reporting off if it is on.
4. Start the macro and look for the Revolution Macro startup embed with Macro Version, Account, and Start Time.
5. On Bot mode, recheck Bot Token and Bot Channel, or switch to Webhook for reports only.

No item reports after a gather

Turn Disable Item Tracking off on Settings → Macro → Reports, keep Webhook or Bot mode on Status → Webhook, and gather for at least about 3 minutes.

Bot connects but ignores commands

Cause: The bot lacks channel permissions, Slash Commands is off without Message Content Intent and a working prefix, or Enable Whitelist blocks your user ID.

Fix:

1. Prefer leaving Slash Commands on under Advanced → General and using /help.
2. If you use prefix commands, open the Bot tab in the Discord Developer Portal, turn Message Content Intent on under Privileged Gateway Intents, and save.
3. On Installation → Guild Install, confirm Scopes includes bot, and permissions include View Channels, Send Messages, Read Message History, Embed Links, and Attach Files.

More help

• Capture and diagnostics when Game Load Timeout stops the macro before it starts
• Detection problems: when Discord alerts mention detection failures or the macro can’t read the screen
• Disconnect and rejoin: disconnection pings and rejoin Status lines

Related

Capture and diagnostics

Detection problems

Disconnect and rejoin