Natro Macro: a Windows AutoHotkey macro for Bee Swarm Simulator

What Natro Macro solves for Bee Swarm Simulator players

Bee Swarm Simulator is a Roblox game built around repetitive collection loops: moving between fields, gathering pollen, returning to the hive, and repeating. Natro Macro exists to run that loop for you on Windows. The README describes it plainly as "An open-source Bee Swarm Simulator macro written in AutoHotkey", and the repository topics list bss, macro, natro, roblox and windows. The audience is narrow and clearly defined: Windows players of that one game who want the repetitive parts handled by a script rather than by hand.

The project is not a general-purpose automation framework. It ships game-specific content in the repository root, including paths/, patterns/, submacros/ and nm_image_assets/, which tells you the automation is organised around named routes and pattern files rather than a generic recorder. The README points to Discord for "custom patterns, paths, and themes", so those directories are the extension surface. If you are looking for a tool to automate a different game or a desktop workflow, this is not it.

How the AutoHotkey macro is structured

The launcher is START.bat, a Windows batch file at the repository root. The README's installation section ends with "Run START.bat and wait for the macro to load", which means the batch file is the entry point and the AutoHotkey runtime is what actually drives the game. The primary language listed for the repository is AutoHotkey, so the automation logic lives in .ahk scripts rather than in a compiled executable you cannot read.

The repository layout separates concerns in a way that matters if you plan to modify it. submacros/ holds the individual routines, paths/ holds route definitions, patterns/ holds pattern files, and lib/ holds shared code. nm_image_assets/ is image data, which strongly suggests screen recognition is part of how the macro decides what to do, though the README does not document the matching method. The README also links a separate development repository at NatroTeam/NatroMacroDev for people who want to develop features, so the main repository is positioned as the distribution and release channel, not the working tree for contributors.

One design consequence: because the macro is written in AutoHotkey and driven from a batch file, it is tied to the Windows desktop session. There is no server component, no headless mode, and no daemon described anywhere in the README.

Installing Natro Macro on Windows

The README gives three numbered steps and nothing else. You download the release archive, open it, and run the batch file. There is no package manager, no installer, and no configuration step documented before first launch.

The first step is to get the archive from the latest release. The README names the file pattern Natro_Macro_v#.#.#.zip, and the most recent release listed is v1.1.2, published on 2026-03-08.

# Download Natro_Macro_v#.#.#.zip from the latest release page
# https://github.com/NatroTeam/NatroMacro/releases/latest

Step two is to extract it. The README says to open the archive and double-click the folder inside, which is worth reading literally: the archive contains a folder, and the macro expects to run from inside it rather than from the archive view.

# Extract the zip, then open the folder inside
# Natro_Macro_v#.#.#/

Step three is the launch. Run START.bat and wait. The README says to "wait for the macro to load", so a delay before the interface appears is expected behaviour, not a failure.

START.bat

Before any of this, read the warning the README places above everything else. The project states it does not have a website, and that the only official sources are the GitHub repository and the Discord server at discord.gg/natromacro. Any other download page is not from the project.

Where Natro Macro stops: platform limits and thin documentation

The most concrete limitation is the platform. The repository topics include windows, the launcher is a .bat file, and the implementation language is AutoHotkey. Nothing in the README describes a macOS, Linux, mobile or Chromebook build. Searches for running Natro Macro on those platforms are common, but the documentation does not support any of them. If you are not on Windows, this project does not have an answer for you.

The second limitation is documentation depth. The README is a landing page: installation, community, contributing, credits, a request for stars, and the licence. It does not document the settings surface, the pattern file format, the path file format, or how the macro detects game state. The README explicitly redirects troubleshooting to Discord, calling it "our main platform for troubleshooting and update news". That is a real trade-off. You get a readable AutoHotkey codebase, but you do not get a written manual, and answers to specific configuration questions live in a chat server rather than in versioned files.

The third limitation is that the README does not document rollback. If a release breaks your setup, there is no described procedure for reverting to an earlier version beyond downloading a different release archive yourself. The release history lists v1.1.0, v1.1.1 and v1.1.2 within a week of each other in March 2026, which suggests releases can arrive in quick succession, so keeping an older archive is a reasonable precaution that the project does not itself describe.

How Natro Macro compares with Revolution

The comparison that comes up most often is with Revolution, another Bee Swarm Simulator macro. This repository does not describe Revolution's internals, so the honest comparison is at the level of what is verifiable about Natro Macro: it is open source under GPL-3.0, it is written in AutoHotkey, its source is readable in this repository, and it distributes through GitHub releases plus a Discord server.

That gives you a specific way to choose. If you want to read and modify the automation logic, AutoHotkey scripts in a GPL-3.0 repository are inspectable in a way that a closed binary is not. If you want a written manual, a support forum with searchable history, or a documented configuration reference, this project's README does not provide one and points you to Discord instead. The decision is less about which macro performs better, which this page cannot establish, and more about whether an inspectable AutoHotkey codebase with chat-based support matches how you work.

Licence and upgrade cost

Natro Macro is licensed under GNU GPL v3.0, per the README and the LICENSE.md file at the repository root. The practical implication is the usual copyleft one: if you redistribute the macro or a modified version, the GPL's terms travel with it. That matters more here than for a typical application, because the repository is designed for modification. The README directs contributors to a separate development repository at NatroTeam/NatroMacroDev, and the main repository is where releases are published. If you fork the macro, add patterns, and hand the result to other people, you are distributing a GPL-3.0 work, not a set of loose scripts. Read LICENSE.md for the actual terms; this is a description of the licence identifier, not legal advice.

The upgrade cost is low in mechanical terms and uncertain in practical terms. Upgrading means downloading a newer release archive and running START.bat from it. There is no migration tool, no config schema version documented in the README, and no stated compatibility guarantee between releases. The last push to the repository was on 2026-04-27, and the latest release is v1.1.2 from 2026-03-08. Because custom patterns, paths and themes are distributed through Discord rather than bundled, an upgrade can leave you reconciling your own files against a new release with no documented procedure for doing so.

Should you run Natro Macro?

Run it if you play Bee Swarm Simulator on Windows and you want an automation layer you can open in an editor. The AutoHotkey source, the GPL-3.0 licence, and the separation of paths/, patterns/ and submacros/ mean the project is set up for people who want to see how the macro works and adjust it. The install is genuinely short: download the release zip, extract the folder, run START.bat.

Do not run it if you are on macOS, mobile or a Chromebook. Do not run it if you need a written manual for settings or file formats, because the README does not contain one and points to Discord. Do not run it if you are unwilling to verify the download source yourself, given the README's explicit warning that the GitHub repository and discord.gg/natromacro are the only official places to get it.

Before you commit, check three things. Confirm the current release on the GitHub releases page and read its notes, since v1.1.0 through v1.1.2 shipped within a week in March 2026 and the README does not describe rollback. Keep the previous archive so you can revert by hand. And read LICENSE.md if you intend to redistribute the macro or a modified version, because GPL-3.0 attaches obligations to that distribution.

Editorial conclusion

Adopt Natro Macro if you play Bee Swarm Simulator on Windows, want an open source AutoHotkey macro you can inspect, and are comfortable getting support through the project's Discord rather than a documentation site. Do not adopt it if you need macOS, mobile or Chromebook support, or if you expect a formal manual: the README is a short download-and-run guide and the repository does not document rollback, so verify the release notes for v1.1.2 on the GitHub releases page and read the LICENSE.md before you redistribute anything.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. NatroTeam/NatroMacro on GitHub
3. Project website
4. README
5. Releases