On this page
- How to Tell When a Natro Macro Update Is Available
- Method 1: Update Natro Macro With the Built-In Updater
- Method 2: Update Natro Macro Manually From GitHub
- Which Folder Holds Your Natro Macro Settings
- Stable or Beta: Choosing Your Release Channel
- Clean Reinstall: When a Simple Update Is Not Enough
- How to Roll Back to an Older Natro Macro Version
- What to Check After Updating Natro Macro
- Updating With Auto-Start or Discord Remote Control
- Which Natro Macro Versions People Use Most
- Natro Macro Update Checklist
- FAQ
Keeping Natro Macro up to date matters more than with most programs. Bee Swarm Simulator changes its map and interface, Roblox changes how it launches, and Natro Team ships patches to keep up. The good news: updating is quick, and your settings come with you. This guide covers the built-in updater, a manual update from GitHub, what to carry over, a clean reinstall and how to roll back if a new version gives you trouble.
The current release is Natro Macro v1.1.2, released March 8, 2026.
How to Tell When a Natro Macro Update Is Available
Every time it starts, Natro Macro asks the GitHub releases API whether a newer version exists. You will notice two signs when one does:
- An update window titled "Natro Macro Update", saying "A newer version of Natro Macro was found! Do you want to update now?" It shows the download size and download count, plus a "Patch Notes & Updates" link.
- A red icon next to the version number in the bottom-right corner of the main window. This version-checker symbol has been there since v0.9.6.
The debug report (F6 or Misc > Debug Options > "Copy Logs") also flags an outdated version in its detected-problems list. If you are troubleshooting anything, check that first. Many "bugs" people report are already fixed in the latest release, and our Natro Macro changelog shows exactly what each version changed.
Method 1: Update Natro Macro With the Built-In Updater
The in-app updater arrived in v0.9.7 and is the easiest route for most players. When the update window appears, look at the options before clicking anything.
| Option | What it does | Our advice |
|---|---|---|
| Copy Settings | Carries your settings folder to the new version | Leave ticked |
| Copy Patterns | Carries your custom patterns over | Tick if you use trusted custom patterns |
| Copy Paths | Carries changed paths over, checked against GitHub | Usually untick, so you get the new official paths |
| Delete v<old> | Removes the old version's folder after updating | Untick if you want an easy rollback |
The buttons are Never, Dismiss (with a 120-second countdown) and Update. Click Update and the macro runs submacros\update.bat, which:
- Downloads the new release zip from GitHub.
- Extracts it and deletes the zip.
- Copies your settings, and patterns and paths if you ticked them.
- Updates the Auto-Start Manager entry if you use it, so Windows launches the new version.
- Shows "Update complete! Starting Natro Macro in 10 seconds."
Why we untick Copy Paths: path updates are one of the main things a new release fixes (v1.1.2, for example, fixed the walk-to-hive paths for Blue Flower, Bamboo and Pine Tree). Copying old paths over can bring old problems back. Only copy paths you changed yourself on purpose.
Major Updates Handle Patterns and Paths Differently
For a major version jump, the updater disables copying paths and patterns, while "your Settings are guaranteed to be transferable." That protects you from old files that no longer work, the way v1.0.0's move to AutoHotkey v2 made older path and pattern syntax obsolete.
"Unable to fetch changed paths from GitHub!"
If this appears during an update, the updater could not reach GitHub to compare paths. As the message says: "If you still want to update, disable 'Copy Paths' (and copy them manually) or try again later." More update-related errors are covered in the Natro Macro troubleshooting guide.
Method 2: Update Natro Macro Manually From GitHub
Prefer to control every step, or the updater fails on your network? A manual update takes about three minutes.
- Stop the macro with F3 and close Natro Macro completely (right-click the tray icon and choose Close).
- Download the new release. Get the zip from the latest GitHub release, or use the button below.
- Extract it to a new folder, separate from your current version. Do not extract on top of the old folder.
- Copy your settings. Copy the
settingsfolder from the old version into the new one, replacing the empty one if it exists. - Copy trusted custom patterns into the new
patternsfolder, if you use any. Leave the shipped ones as they are. - Run
START.batin the new folder and check your tabs look right.
Direct download from the official GitHub release
Keep the old folder for a few days. If anything feels off, you can switch back instantly. New to the launcher? The Natro Macro install guide covers extracting and antivirus issues in detail.
Which Folder Holds Your Natro Macro Settings
Everything you configure lives in the settings folder inside your Natro Macro folder. Back it up before any update. These are the files inside:
| File | Contents |
|---|---|
nm_config.ini | Main settings from every tab, including Discord settings |
field_config.ini | Field defaults used for quests and planters |
manual_planters.ini | Manual planter cycles |
mutations.ini | Auto-Jelly choices |
debug_log.txt | Debug log |
imported\patterns.ahk, patternHashes.ahk | Imported pattern data |
personal.ahk, personal_commands.ahk | Optional personal tweaks and custom Discord commands |
Since v0.8.4, Natro Team has described this folder as "safely transferrable between versions." Because nm_config.ini includes your Discord settings, treat backups like a password file and never share them publicly. Our Discord bot guide explains why a bot token must stay private.
Want to share just your gather setup with a friend instead of the whole folder? Use the "Copy" and "Paste" buttons on the Gather tab, which turn gather settings into a text string. See the gather settings guide.
Stable or Beta: Choosing Your Release Channel
Since v1.1.0, the Settings tab has a "Release Channel" option: Stable or Beta. The updater respects it, so on Stable you are only offered full releases. Beta builds appear earlier, and the macro warns that beta "may expose your macro to more bugs." Unless you enjoy testing and reporting issues, stay on Stable. If you do test, keep a stable copy in a separate folder with its own settings.
Clean Reinstall: When a Simple Update Is Not Enough
Sometimes carrying your settings over carries a problem over too. A clean reinstall rules that out:
- Back up your old
settingsfolder somewhere safe, such as a folder on your Desktop. - Delete the old Natro Macro folder entirely.
- Download and extract a fresh copy of the latest release.
- Run it with default settings and do a short test: Sunflower, Squares, a few minutes of gathering.
- If the test works, close the macro and copy your backed-up
settingsfolder in. If the problem returns, your settings are the cause. Use "Reset Field Defaults" or "Reset All Settings" in the Settings tab, then rebuild your setup.
A clean reinstall also fixes missing files, such as the "Folder location cannot be found" error for nm_image_assets, or an antivirus that removed AutoHotkey32.exe during the update.
How to Roll Back to an Older Natro Macro Version
New releases occasionally behave differently on a particular PC or setup. Rolling back is safe and simple, because every past version stays on GitHub.
- Pick the version from our Natro Macro download page, which lists every older release with its GitHub link.
- Extract it into its own folder.
- Copy your
settingsbackup into it. - Handle the update prompt. The older version will see the newer release on GitHub and offer to update. Click Dismiss to keep using it for now, and remember to come back to the latest version later.
Two cautions. First, older versions miss security fixes: anything before v1.1.0 has the Discord remote control vulnerability that let any Discord user perform actions through Remote Control, and the pattern code execution issue. If you use the Discord bot, do not roll back below v1.1.0. Our Natro Macro safety page explains both fixes. Second, versions before v1.0.0 run on the old AutoHotkey v1 syntax, so v2 patterns and paths will not work in them.
What to Check After Updating Natro Macro
A new version can read your old settings perfectly and still behave a little differently in game, because paths, timings and detection get tuned between releases. Before you walk away from the PC, run through this quick list:
- Version number. The bottom-right corner should show the new version, with no red icon next to it.
- Gather tab. Your fields, patterns, sizes, widths and Until values should match what you had. If a custom pattern is missing from the dropdown, it was not copied or failed to import.
- Pattern prompts. If you see "IMPORTANT!! READ THIS WHOLE MESSAGE" for a pattern, only confirm it if you know exactly where that file came from.
- Settings tab. Hive Slot, number of bees, Movement Speed and your private server link should be unchanged.
- Discord. If you use the bot, send
?helpfrom your whitelisted account and confirm it replies. - One supervised cycle. Press F1 and watch one trip out to the field, the pattern and the walk back to the hive.
If something is off, compare the new settings folder with your backup, or follow the clean reinstall steps below.
Updating With Auto-Start or Discord Remote Control
If Natro Macro runs on a dedicated PC that you manage from your phone, a couple of extra details matter. The built-in updater updates the Auto-Start Manager entry for you, so Windows launches the new folder at logon. After a manual update, open Misc > Auto-Start Manager in the new version and set it up again, or Windows will keep starting the old copy.
Updating from v1.0.x to v1.1.0 or later also changes who can control your macro: commands can be locked to a whitelisted User ID or Role ID, and you should fill it in, because an empty whitelist lets anyone who can post in the channel run commands. If your bot stops answering after an update and says "Only <@id> can use commands", add your own Discord ID in the Discord settings window. The settings and hotkeys guide covers Auto-Start in more detail.
Which Natro Macro Versions People Use Most
Download counts on GitHub give a sense of which releases players settled on. v1.0.1 is the most downloaded release by far, with over 1.7 million downloads, followed by v1.0.0.2, v1.0.0.3 and v1.0.0.1. The latest, v1.1.2, already has more than 385,000. Across all releases, Natro Macro has more than 4.6 million downloads on GitHub.
Popularity is not a reason to stay on an old build, though. v1.1.0 was a major update with two security fixes, Roblox share-link support, touchscreen and UWP warnings, petal quests and a rewritten Vicious Bee routine. v1.1.1 and v1.1.2 then fixed pattern import pop-ups, a crash with Auto Field Boost field boosters, and several hive paths.
Natro Macro Update Checklist
- Back up your
settingsfolder. - Use the updater with Copy Settings on and Copy Paths off, or update manually into a new folder.
- Keep the old version until the new one has run cleanly for a day.
- Read the patch notes via the "Patch Notes & Updates" link or our changelog.
- Only download from the official GitHub releases page or the official Discord.
- Run a short supervised test before leaving it overnight.
Follow this every time and a Natro Macro update becomes a two-minute routine. For update news as it happens, the official Natro Macro Discord is where Natro Team announces new releases.
Frequently asked questions
Will I lose my settings when I update Natro Macro?
No, as long as your settings folder comes along. The built-in updater copies it automatically when Copy Settings is ticked, and for a manual update you copy the folder into the new version yourself. Natro Team has described this folder as safely transferable between versions since v0.8.4, and major updates guarantee settings carry over.
What does the red icon next to the version number mean?
It means a newer Natro Macro release is available on GitHub. The macro checks the GitHub releases API every time it starts. You will usually also see the Natro Macro Update window with the download size, download count and a Patch Notes link. Click Update to install it, or update manually from the releases page.
Should I tick Copy Paths when updating?
Usually not. New releases often fix paths, for example v1.1.2 fixed the walk-to-hive paths for Blue Flower, Bamboo and Pine Tree. Copying your old paths can undo those fixes. Only tick Copy Paths if you deliberately edited paths yourself. For major updates, the updater disables path and pattern copying anyway.
How do I go back to an older version of Natro Macro?
Download the version you want from the GitHub releases page or our download page, extract it to its own folder and copy your settings folder in. Avoid anything older than v1.1.0 if you use Discord remote control, because earlier versions have a patched security vulnerability. Return to the latest release once your issue is solved.
Should I use the Beta release channel?
Only if you want to test new features and report bugs. The Release Channel setting in the Settings tab switches between Stable and Beta, and the macro warns that beta may expose your macro to more bugs. For unattended gathering, Stable is the better choice. Keep a separate folder if you test betas.
Keep reading



