# Natro Macro is one batch file, five folders, and a script that drives your input

> NatroTeam/NatroMacro is a GPL licensed AutoHotkey script that automates a Windows game, published as a numbered release zip rather than as an application. Its structure is unusually legible once you know what an automation script is, and the project is careful about fake download sites and vague about whether running it against a live game is safe.

**NatroTeam/NatroMacro** — A Bee Swarm Simulator macro for Windows

- Repository: https://github.com/NatroTeam/NatroMacro
- Website: https://discord.gg/natromacro
- Stars: 2,423 · Forks: 233
- Language: AutoHotkey
- License: GPL-3.0
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/natroteam-natromacro

## The distribution warning appears twice, once hidden and once rendered

The first thing in the file is a large HTML comment containing ASCII art, a thank you, a pointer to the launcher, and an invitation to the project's chat server. Buried in the same comment is an instruction that the reader should only download from an official source, followed by a two-item list of what counts as official. None of that is visible on a rendered page. Then the rendered document opens with a callout saying the project does not have a website, and that the only official places are this repository and the chat server. The duplication is not accidental redundancy: the callout exists so that a reader who copies the rendered page still sees the warning, and the comment is labelled as such in the source. For a project whose name is easy to imitate and whose downloads are a zip file, that is a considered response rather than a stock disclaimer, and it is the most careful thing in the repository.

## The entire project is one batch file and five directories

The top level has eleven entries and five of them are directories. A batch file at the root is the launcher. Then a directory of macro code, a directory of sub-macros, a directory of patterns, a directory of paths, and a directory of image assets. That decomposition is the architecture, and it explains everything else about how the project is distributed. Code and data are separated, so the paths and patterns that define what the script does can be swapped without touching the logic, which is why the chat server offers custom patterns, paths, and themes as downloadable content rather than as forks. The image asset directory implies the script identifies state by looking at the screen rather than by reading anything the game exposes, which is the usual approach for this class of automation on Windows. The declared language is the automation scripting dialect that does exactly that, and it is the only dependency that matters.

## Windows is the only target, and the questions in the wild are about other platforms

The project's own one-line summary names the platform: a macro for one Windows game. Everything in the repository agrees. The language is a Windows automation dialect, the launcher is a Windows batch file, and the release artifact is a zip that expands to a folder containing that file. There is no macOS path, no Linux path, no browser version, and no mobile version, because none of those could run the launcher. That is worth stating plainly because the questions the project fields are dominated by other platforms, the most repeated being how to run it on a Mac, on a Chromebook, on a phone, and whether it works with the monitor off or in the background. Four of those five are answerable with one word. The fifth, running in the background, is the one that is a genuine engineering question rather than a platform mismatch, and the answer depends on the game rather than on this repository.

## Three patch releases in six days, then nothing tagged for seven months

The release history is three entries and they are close together: a one point one point zero, then a one point one point one five days later, then a one point one point two three days after that, all in the first week of March 2026. Nothing has been tagged since. The last commit to the repository is dated 2026-04-27, so the source tree carries roughly seven weeks of work that no release zip corresponds to, and about five months of that is unaccounted for by any artefact. The release naming is also unusual: the distributed file is named for the release with literal placeholders in the instruction, so the file name a user holds encodes the version they installed, which is a good habit that costs nothing. The release page carries a total download count badge, which means the project's own reach is a public number.

## Bug reports, credits, guidelines, and the source all live somewhere else

Four destinations and none of them is this repository. Bugs and suggestions go through two issue templates on this repository, each pre-labelled with a needs-triage marker, so the templates are configured rather than free text. The contributing guidelines and the credits list both live in the organisation's shared configuration repository rather than here. The development tree for the macro is in a separate repository, named in the contributing section as the place to go if you want to build features. And the chat server is described as the main platform for troubleshooting and for update news. So what this repository actually contains is a distribution artifact plus a signpost set, which is a reasonable structure for a project whose contributor base arrives through a chat server rather than through pull requests, and it does mean that reading this repository tells you almost nothing about how the macro is built.

## The license section is nested inside an anchor that closes too early

The license is not a section here, it is a collapsed block, and the markup around it is wrong. An anchor element with the name of the section is opened, a details element and its summary are placed inside it, and then the closing anchor tag appears immediately after the summary while the details element is still open. The license text and the closing details tag come after that. So the anchor that a link would jump to wraps the disclosure triangle rather than the license, and the two elements interleave. It renders, so nobody noticed. The same file has two other small defects of the kind that come from copying between documents: a stars section contains a fragment of inline mathematical markup for a coloured word, which renders as literal punctuation on the page, and the logo block carries a comment marking a dark theme variant with no second image element under it, so the dark-theme logo is described but not present.

## Conclusion

Read this before anything else: a macro like this drives your mouse and keyboard and reads the screen, so running it against an account that matters is a decision about someone else's terms of service and about your own risk, and the project never claims the game permits it. Treat this repository as an interesting example of how a small Windows automation project is packaged rather than as something to deploy. Check four things. Where the code actually is, because the public repository holds a launcher and five folders while the development tree sits in a separate repository. Whether your platform is supported at all, because the language and the launcher are both Windows-only and most of the questions the project receives are about other platforms. What you are downloading, given that the project states twice that it has no website and that unofficial mirrors exist. And what your pattern and path files are, because those are the part people share on the project's chat server and the part that defines what the script does.

## FAQ

### Is Natro Macro safe to use?

The project does not make that claim. It states that it has no website, that only the repository and its chat server are official download sources, and it asks users to verify where they got the file. It does not say that automating the game is permitted, so whether using it against an account you care about is safe is a question for the game's terms, not for this repository.

### What language is Natro Macro written in?

AutoHotkey, the Windows automation scripting language, which is what lets the macro move the mouse, press keys, and read the screen. The launcher is a Windows batch file and there is no version for any other platform.

### What is in the Natro Macro repository?

A launcher batch file and five directories: macro code, sub-macros, patterns, paths, and image assets. The development tree is in a separate repository, and the contributing guidelines and credits live in the organisation's shared configuration repository.

### Can I run Natro Macro on a Mac or a Chromebook?

No. The declared language is a Windows automation dialect and the entry point is a Windows batch file, so neither platform can run it. The project's own summary scopes it to Windows and the repository offers no cross-platform path.

### How do I get extra patterns and paths for Natro Macro?

Through the project's chat server, which the community section describes as the place for guides, help channels, and downloadable custom patterns, paths, and themes. Those are data folders in the repository rather than code, which is why they can be shared without forking the project.

## Sources

- [License: GPL-3.0](https://github.com/NatroTeam/NatroMacro/blob/main/LICENSE)
- [NatroTeam/NatroMacro on GitHub](https://github.com/NatroTeam/NatroMacro)
- [Project website](https://discord.gg/natromacro)
- [README](https://github.com/NatroTeam/NatroMacro/blob/main/README.md)
- [Releases](https://github.com/NatroTeam/NatroMacro/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/natroteam-natromacro