Advanced Macro Engine

# 🔧 macroEngine **Minecraft Java Edition 26.2 | Multiplayer-Safe | Pure Datapack** (https://github.com/runtoolkit/macroEngine/actions/workflows/ci.yml/badge.svg)](https://github.com/runtoolkit/macroEngine/actions/workflows/ci.yml) (https://img.shields.io/badge/License-MIT-green?style=for-the-badge)](LICENSE) --- > Current version: **v6.1.0** --- > **This datapack was considered safe to use as of its last release, but it no longer receives security improvements, bug fixes, or new features. There is no "up to date" version to move to.** > > **Do not copy `macroengine:input` or `macroengine:engine` into your own datapack.** It is an internal implementation detail and may change without notice between releases. > ⚠️ **Do not use v5.1.1.** That version bound `_rt_origin.mcfunction` to the load tag, causing it to run automatically on every load with no safe removal path. Fixed in later versions — always use the latest release. --- > ⚠️ A `/reload` is still required after installation or after adding the load hook below. Automatic first-join initialization is not implemented in this version — do not rely on this until verified in-game with repeated reloads. --- > 🛡️ **This is a Minecraft Datapack — it contains no executables or scripts outside of `.mcfunction` files.** > Some antivirus software may flag `.mcfunction` files as suspicious due to macro-like syntax. This is a **false positive**. The pack has been scanned on (https://www.virustotal.com) and returned clean. > **Only download from this official repository.** Do not trust redistributed or repackaged versions from third-party sources. --- ## 📦 Installation 1. Download the latest release from the (https://modrinth.com/datapack/macroengine/versions) and place the `.zip` into `<world>/datapacks/`. 2. Add the following logic to your datapack's `load` tag. Replace `<namespace>` with your own datapack's namespace (e.g. `mypack`) — this applies only to the function names, never to `macroengine:engine`, which is MacroEngine's own fixed storage and must not be changed: ```mcfunction #> <namespace>:load execute unless data storage macroengine:engine {global:{loaded:1b}} run function <namespace>:load_macroengine ``` ```mcfunction #> <namespace>:load_macroengine # Guard checks the SAME storage/path the trigger condition checks (macroengine:engine global.loaded). execute if data storage macroengine:engine {global:{loaded:1b}} run return 0 function macroengine:setup data modify storage macroengine:engine global.loaded set value 1b ``` > **v6.1.0 change:** macroEngine no longer auto-starts via `minecraft:load`. The > old `function macroengine_load:main` entry point (and the LanternMC `load:` > tag chain it depended on) is gone. Consuming packs must call > `function macroengine:setup` explicitly — either from their own manual > `<namespace>:load_macroengine` guard (as above) or once by an admin. <details> <summary>Fixed bug: duplicate load trigger (click to expand)</summary> An earlier version checked `macroengine:engine {global:{loaded:1b}}` in the trigger but set `<namespace>:engine loaded_macroengine` in the guard — two different storages, two different paths. The set never satisfied the trigger's condition, so `load_macroengine` re-ran every time the load tag fired. This doesn't crash anything, but it silently re-triggers `dl_load:load/yes` and `fork_no` on every reload, which can accumulate side effects depending on what those functions do. Both the check and the set must target `macroengine:engine global.loaded`. If you're updating from an older copy of this README, verify by reloading multiple times and confirming `load_macroengine` does NOT re-run after the first load. </details> --- ## 🏗️ Storage Architecture ``` macroengine:engine (persistent data) ├── global │ ├── version: "v6.1.0" │ ├── loaded: 1b │ └── tick: <int> ├── players │ └── Steve { coins:150, level:5, xp:2300, online:1b, ... } ├── queue │ └── ├── cooldowns │ └── Steve { fireball: 2460, dash: 1870 } ← expiry ticks └── events └── on_join: macroengine:input (sending data to a function) macroengine:output (receiving results from a function) ``` **Note:** All MacroEngine-owned state lives under the `macroengine:` namespace only. Never mix a consuming pack's own namespace into MacroEngine's load-flag logic — that mismatch was the source of the bug above. --- ## 📦 Dependencies ### Lantern Load — **removed in v6.1.0** **Repository:** https://github.com/LanternMC/load **License:** BSD 0-Clause (public domain) Previously provided deterministic load order, version tracking, and pre/load/post-load hooks via the `load:` namespace tag chain. As of v6.1.0 this dependency is gone entirely — macroEngine starts via a manual `function macroengine:setup` call instead (see the Load Guard section above). `data/load/` no