Natro Macro logoNatro MacroDownload

Fixes

Natro Macro Not Working? Fix Every Common Error

Every real Natro Macro error message, grouped by where it appears, with the cause and the exact fix for each one.

Fixing Natro Macro errors on a Windows PC running Bee Swarm Simulator
On this page
  1. Start Here: Get a Natro Macro Debug Report
  2. Quick Five-Point Check Before You Dig In
  3. Natro Macro Won't Start: Launcher and Folder Errors
  4. Display and Roblox Detection Errors
  5. Gathering Problems: Drift, Walking Out of Fields, Wrong Paths
  6. Pattern and Path Errors
  7. Reconnect and Private Server Errors
  8. Freezes, Restarts and Timeout Messages
  9. Planter and Sticker Status Errors
  10. Update, Internet and OCR Errors
  11. Discord and Remote Control Errors
  12. Hotkey Errors and Hotkeys Not Working
  13. When Nothing Here Fixes Natro Macro
  14. FAQ

When Natro Macro stops working, it nearly always tells you why. The macro has dozens of built-in checks, and each one shows a specific message. The trick is knowing what that message really means. This page collects the real error text from the Natro Macro source code, grouped by where it shows up, with the cause and the fix for each one.

Use your browser's find (Ctrl+F) and paste a few words from your error to jump to the right section. If your problem has no message at all, start with the first section on the debug report, because it often reveals the cause before you even look.

Start Here: Get a Natro Macro Debug Report

Since v1.1.0, Natro Macro includes debug logs that point out common issues automatically. Press F6, choose "Copy Logs" from the tray menu, or open Misc > Debug Options > "Copy Logs". You will see "Copied Debug report to your clipboard."

Paste it into Notepad and read the detected problems list. The macro checks for:

  • Display scale other than 100%
  • Roblox not found, or a custom install
  • A custom bootstrapper (e.g. Bloxstrap)
  • "Low screen resolution" (height 600 or less, or width 1300 or less)
  • A recent GUI y-offset failure
  • An outdated Natro Macro version
  • Remote Desktop being minimized (which breaks the macro)
  • Touchscreen enabled
  • UWP (Microsoft Store) Roblox
  • Error hiding switched off

The report also includes your OS, resolution and scale, CPU, RAM, AutoHotkey versions, Natro Macro version, install path, Roblox path and type, plus recent errors from settings\debug_log.txt. It is exactly what helpers on Discord ask for.

Quick Five-Point Check Before You Dig In

In our experience, these five checks solve the majority of "Natro Macro not working" reports before anyone needs to read an error message:

  1. Windows display scale is exactly 100%, and Roblox was restarted after changing it.
  2. Roblox is the standard player from the Roblox website, not the Microsoft Store app.
  3. Roblox graphics are Manual and lowest, Experience Language is English, and nothing covers the top of the window.
  4. The macro folder was fully extracted to Downloads or Desktop, and submacros\AutoHotkey32.exe exists.
  5. You are on the latest release, v1.1.2.

If all five are true and the problem continues, find your message below.

Natro Macro Won't Start: Launcher and Folder Errors

These appear before the Natro Macro window opens, or right as it starts loading.

"Could not find submacros\AutoHotkey32.exe!"

Cause: The bundled AutoHotkey interpreter is missing. The launcher's full message explains: "This is most likely due to a third-party antivirus deleting the file."

Fix: Disable the third-party antivirus or add the Natro Macro folder as an exception, re-extract the macro, check that AutoHotkey32.exe exists in the submacros folder and run START.bat again. The message ends with "Note: Both Natro Macro and AutoHotkey are safe and work fine with Microsoft Defender!" Our page on Natro Macro antivirus false positives explains why this happens.

"Unable to automatically extract Natro Macro!"

Cause: You ran START.bat from inside the zip, and the launcher could not find the zip in Downloads, Desktop, Documents or their OneDrive equivalents. Or the folder is extracted but files are missing.

Fix: Follow the message: "If you have already extracted, you are missing important files, please re-extract. If you have not extracted, you may have to manually extract the zipped folder." Right-click the zip, choose Extract All, and run START.bat from the extracted folder. Full details are in the Natro Macro install guide.

"Couldn't find the 32-bit version of Autohotkey in: ..."

Cause: Natro Macro always runs on the 32-bit interpreter and reloads itself with AutoHotkey32.exe if started another way. This error means that file is not where it should be, usually because of antivirus or an incomplete extract.

Fix: Same as above: exclude the folder, extract a fresh copy, and launch with START.bat rather than double-clicking natro_macro.ahk with another AutoHotkey install.

"You must run Natro Macro as administrator in this folder!"

Cause: The macro cannot write to the folder it is in, typically Program Files or another protected location.

Fix: The message itself gives the better option: "If you don't want to do this, move the macro to a different folder (e.g. Downloads, Desktop)". Move the whole folder and launch again.

"You cannot run Natro Macro in this folder!" and "Could not create the settings directory!"

Cause: Same family of problem. The macro needs to create a settings folder next to itself and is not allowed to.

Fix: Move the macro to a normal user folder such as Downloads or Desktop. Avoid running it from a zip, a network drive or a synced folder that locks files.

"Folder location cannot be found: ...\nm_image_assets\"

Cause: The nm_image_assets folder holds the images the macro uses to recognize the game. It is missing, which points to a broken extract or files moved out of the folder.

Fix: Extract a fresh copy from the official release. Keep the folder structure exactly as it comes in the zip.

Display and Roblox Detection Errors

These are the most common Natro Macro problems overall. Most are fixed in one sitting with our Roblox and Windows settings guide.

"Your Display Scale seems to be a value other than 100%."

Cause: Windows scaling is above or below 100%, so screen images do not match the macro's references. The message continues: "This means the macro will NOT work correctly!"

Fix: Right-click your desktop, click Display Settings, set Scale under Scale & Layout to 100%, then close and restart Roblox before starting the macro.

"This macro requires a display-scale of 100%"

Cause: Thrown by the Auto-Jelly tool in the Misc tab, which is strict about scale.

Fix: Same fix as above.

"UWP Roblox installation is detected, Natro Macro currently does not support it."

Cause: You have the Microsoft Store version of Roblox. The current Natro Macro does not support it.

Fix: Uninstall the Store app and install Roblox from https://www.roblox.com/download, as the message says.

"Unable to detect a Roblox installation." / "Incorrect Roblox Configuration"

Cause: The macro found no Roblox install it recognizes. The window title is "Roblox Not Found", and the status log shows "Incorrect Roblox Configuration".

Fix: Install the standard Roblox Player from the Roblox website. In the Settings tab, check "Detected Roblox:" and press Refresh.

"Incorrect Roblox Settings Detected"

Cause: Natro Macro read your Roblox settings file and found values it does not expect.

Fix: Apply what the window lists: Manual graphics at the lowest quality, lowest Text Size, Shift Lock on, Inverted Camera off, Microprofiler off, Camera Mode Classic and Movement Mode Keyboard. Once done, "You can safely ignore this message if you have already changed them."

"Unable to detect in-game GUI offset!"

Cause: The macro could not find where the game interface sits in the window. The message names three reasons: "Incorrect graphics settings", "Your 'Experience Language' is not set to English", and "Something is covering the top of your Roblox window."

Fix: Set graphics to manual and lowest, switch Experience Language to English, move overlays and other windows (including Natro Macro itself if set to Always On Top) away from the top of Roblox, and confirm display scale is 100%. The message also points to a Knowledge Base post on the official Discord.

"Your Roblox window is run as admin, but the macro is not!"

Cause: Windows blocks a normal program from sending keys to an admin program. The note warns that "this issue also causes hotkeys to not work while Roblox is active."

Fix: Stop the macro, then either reinstall Roblox without administrative rights or run Natro Macro as admin.

"It seems like you have Touchscreen enabled."

Cause: A touchscreen is active, and "the macro will NOT reset your character properly!"

Fix: Press Win+S, open Device Manager, right-click "HID-compliant touch screen" under Human Interface Devices, select Disable Device, and restart your PC.

"You must have Bee Swarm Simulator open to use this!"

Cause: You opened a tool (such as one from the Misc tab) that needs the game running.

Fix: Join Bee Swarm Simulator first, then use the tool.

Gathering Problems: Drift, Walking Out of Fields, Wrong Paths

"You have Field Drift Compensation enabled ... However, you do not have supreme saturator as your sprinkler type set in settings"

Cause: Drift Comp re-aligns you by searching for the neon blue pixel of the Supreme Saturator. Without it, the help text warns, "you will drift more."

Fix: If you own the Supreme Saturator, set Sprinkler Type to Supreme in the Settings tab. If you do not, untick "Drift Comp" for that gather slot.

Character walks out of the field or misses the hive (no error)

Cause: Usually a wrong "Movement Speed (WITHOUT HASTE)" value, the wrong Hive Slot, or camera and movement settings in Roblox.

Fix: Enter your exact BSS movement speed (default 28, decimals allowed, e.g. 33.6), keep "MoveSpeed Correction" on, confirm your Hive Slot, and recheck Classic camera and Keyboard movement. Smaller pattern sizes help in narrow fields. The gather settings guide and pattern guide go deeper.

Pattern and Path Errors

Custom patterns and paths are the second biggest source of trouble, and since v1.1.0 they are also a security topic.

"IMPORTANT!! READ THIS WHOLE MESSAGE"

Cause: You added a new or unknown pattern. Natro Macro warns that "Pattern files can execute any AutoHotkey code, including potentially malicious code," then asks "Do you FULLY trust the pattern X and want to import it?"

Fix: Only say yes for patterns from the official Discord's #patterns channel or the verified Paths-Patterns repository. The message is blunt: "you should not download a pattern from a stranger telling you to test out their pattern."

"Pattern 'X' seems to be deprecated!"

Cause: The pattern uses old syntax. Since v1.0.0, paths and patterns must use pure AutoHotkey v2 syntax. "This means the pattern will NOT work!"

Fix: "Check for an updated version of the pattern or ask the creator to update it." Or switch to one of the 12 built-in patterns.

"Unable to import 'X' pattern!"

Cause: The pattern failed the macro's syntax check.

Fix: Click OK to keep loading without it, then remove or replace the file in the patterns folder.

"Path 'k-v' seems to be deprecated!" and "Could not find the 'k-v' path!"

Cause: A path file in the paths folder is outdated, or missing entirely.

Fix: "Make sure the path exists in the 'paths' folder and redownload if it doesn't!" The safest fix is a fresh copy of the latest release, then re-adding only trusted custom paths.

Reconnect and Private Server Errors

These show up in the Status box while Natro Macro tries to get you back into the game.

"No Roblox Found Retry: N"

Cause: Roblox did not open after a reconnect attempt.

Fix: Use the "Test" button under Reconnect in the Settings tab. Keep "Join Method" on Deeplink (the default; Browser is "not recommended"), and make sure Roblox launches normally on its own.

"No BSS Found Retry: N" and "BSS Load Timeout Retry: N"

Cause: Roblox opened but Bee Swarm Simulator was not found, or took too long to load. Server or connection problems are the usual reason.

Fix: Let it retry. Keep "Fallback to Public Server" on so the macro can "revert to attempting to join a Public Server if your Server Link failed three times." You can also add up to three backup private servers in the hidden Advanced tab.

Cause: The link is incomplete or not a Bee Swarm Simulator server. The message reads "Make sure your link is: copied correctly and completely; for Bee Swarm Simulator by Onett".

Fix: Copy the full link again. Accepted forms are roblox.com/games/1537690962/...?privateServerLinkCode=... and the newer roblox.com/share?code=...&type=Server.

Cause: For share links, the macro fetches the page to confirm it is BSS. "Invalid Share Code" means "Your link is not for Bee Swarm Simulator by Onett." "Failed to fetch link" means the check could not reach Roblox.

Fix: Generate a new share link from your BSS private server, check your internet connection and try again.

Freezes, Restarts and Timeout Messages

Natro Macro runs a heartbeat that restarts things when a part of the macro stops responding.

MessageMeaningWhat to do
"Macro Unresponsive Timeout!"The main macro stopped respondingUsually recovers on its own; if it repeats, lower graphics, close heavy programs, check the debug log
"Background Script Timeout!"The background checker (death, night, backpack) stalledSame as above; update to the latest version
"Status Script Timeout!"The Discord/status script stalled for 120 secondsCheck Discord settings and your connection
"No Roblox Window Timeout!"No Roblox window for 600 secondsCheck reconnect settings and your private server link

If the Roblox window itself keeps freezing, try the FPS editor in the Misc tab (Roblox must be closed while you edit) and keep graphics at the lowest setting.

Planter and Sticker Status Errors

These appear in the Status log and, if enabled, in your Discord reports.

  • "3 Planters already placed! MaxAllowedPlanters has been reduced." The game already has three of your planters out, usually ones you placed by hand. The macro lowers its own limit to match. Harvest your manual planters and set "Max Planters" again on the Planters tab.
  • "Failed to place planter in 10 tries!" The placement did not succeed after ten attempts. Check that the planter is actually in your inventory, the field is reachable for your bee count, and your Roblox settings are correct.
  • "No Eggs left in inventory! Sticker Printer has been disabled." Buy or collect more of the egg type selected for the Sticker Printer, then re-enable it on the Boost tab.
  • "No Stickers left to stack!" and "No Tickets left to use!" Your Sticker Stack item choice (Tickets, Sticker or Sticker+Tickets) has run out. Pick a different item or refill.
  • "Unable to detect Stack Boost time!" The macro could not read the Sticker Stack timer. Use a custom timer (900 to 86,400 seconds) instead of Detect.
  • "Yes/No appeared too many times!" A Yes/No confirmation prompt kept showing up during a Sticker action, and the macro gave up on it. Do the action once by hand in game to see what the prompt is asking, then check your Sticker Stack item and skin choices.

Update, Internet and OCR Errors

"Unable to fetch changed paths from GitHub!"

Cause: During an in-app update with "Copy Paths" ticked, the macro could not reach GitHub to compare paths.

Fix: "If you still want to update, disable 'Copy Paths' (and copy them manually) or try again later." See how to update Natro Macro.

"Could not fetch Beesmas data from GitHub!"

Cause: The macro checks GitHub to see if Beesmas is active and could not connect.

Fix: Check your internet and reload the macro. Since v1.1.0 you can also enable Beesmas manually for 1 to 90 days.

"No OCR supporting languages are installed on your system!"

Cause: Windows OCR, used to read honey for the hourly graphs, has no supported language.

Fix: Install a supported language as a secondary Windows language, as the Knowledge Base guide describes. Without it, the macro runs fine but "Honey Graphs will be empty."

Discord and Remote Control Errors

  • "Invalid Channel ID!" and "Invalid User ID!" Discord IDs are long numbers. Turn on Developer Mode in Discord, right-click the channel or your profile, and copy the ID, not the name.
  • "Only <@id> can use commands": since v1.1.0, when a User ID or Role ID is whitelisted, only that user or role can run commands. Add your own ID in the Discord settings window.
  • "`?x` is not a valid command! Use `?help` for a list of commonly used commands." A typo or a command that does not exist. Run ?help, or ?help advanced for the full list.

Our Natro Macro Discord bot guide covers webhook and bot setup from scratch.

Hotkey Errors and Hotkeys Not Working

"That hotkey cannot be used! The key is already used elsewhere in the macro." Pick a different key in Misc > Change Hotkeys. A variant says the key "will be required to use your hotbar slots", meaning number keys are reserved for the Boost tab. "Restore Defaults" brings back F1 to F6.

If hotkeys do nothing while Roblox is focused, the admin mismatch described above is the likely cause. See the settings and hotkeys guide for every default.

When Nothing Here Fixes Natro Macro

  1. Update. Make sure you are on v1.1.2. The debug report flags outdated versions, and many old bugs are already fixed.
  2. Clean install. Download a fresh copy, extract it, and test with default settings before moving your old settings folder over.
  3. Ask on Discord. The official Natro Macro Discord is the main place for troubleshooting. Paste your debug report.
  4. Report a bug. Use Misc > "Report Bugs" or the GitHub issues page. The form asks what happened, steps to reproduce, expected behavior and your Natro Macro version.

The bug template reminds everyone that "Natro Macro is maintained by volunteers. Please be patient when waiting for a response." A clear report with your debug log gets fixed faster.

Frequently asked questions

Why is Natro Macro not working after a Roblox or BSS update?

Game updates can move map features or change the interface, which breaks paths and image detection. Natro Team usually responds with a patch, as with v1.0.0.2 after BSS map changes. Check that you are on the latest release, read the patch notes, and ask on the official Discord, which is the main channel for update news.

What does Unable to detect in-game GUI offset mean?

Natro Macro could not locate the game interface inside the Roblox window. The macro names three causes: incorrect graphics settings, an Experience Language other than English, and something covering the top of the Roblox window. Fix those, confirm 100% display scale, and restart Roblox.

Why does my antivirus delete AutoHotkey32.exe?

Some third-party antivirus programs flag AutoHotkey executables because the language can automate input. START.bat then says it could not find submacros\AutoHotkey32.exe. Add the Natro Macro folder as an exception, re-extract the official zip and run START.bat again. Natro Team notes it works fine with Microsoft Defender.

Why do my Natro Macro hotkeys not work?

The most common reason is that Roblox runs as administrator while the macro does not, so Windows blocks the key presses. The macro warns about this directly. Reinstall Roblox normally or run the macro as admin. Also check Misc, Change Hotkeys, in case a key was changed or conflicts with another program.

How do I send a debug report for Natro Macro?

Press F6, use Copy Logs in the tray menu, or go to Misc, Debug Options, Copy Logs. The macro copies a full report to your clipboard with your system details, Roblox type, detected problems and recent errors. Paste it in a help channel on the official Natro Macro Discord or into a GitHub bug report.

Why does Natro Macro keep reconnecting or show No BSS Found?

Roblox opened but Bee Swarm Simulator did not load in time, often due to server or connection issues. Use the Test button under Reconnect, keep Join Method on Deeplink, check your private server link, and leave Fallback to Public Server on. Backup private servers can be added in the hidden Advanced tab.

Keep reading