Run macros on events, on join and on a schedule
Start a macro from a game event, when an account joins, or at a clock time, and control loops, staggering, and day or night limits.
Event macros
Switch a macro to On events and it runs whenever one of the events you tick under Fires on happens on an account. Tick as many as you need; the macro fires on any of them.
| Event | Fires when |
|---|---|
| On Death, On Respawn | The account dies, or respawns after a death. |
| On Reconnect | The account joins again after it was connected before. |
| On Chat Message | A chat message contains the text in the Contains Text field. |
| On Chat Keywords | A message contains any of the comma separated Chat keywords, ignoring capitals and colours. Player and server messages count; action bars do not. Up to 20 keywords. |
| Inventory Full | Every main inventory and hotbar slot holds something. It fires once, then arms again after a slot frees up. An inventory that is already full when you activate the macro fires on the first check. |
| On Low Health, On Low Hunger | Health or food drops below the number you set (1 to 20). |
| On Full Health | Health is back to full. |
| On Disconnect, On Kicked | The account leaves the server, or is kicked with a reason. |
| On Item Pickup, On Damage Taken | The account picks up an item, or takes damage. |
| On World Change, On Server Transfer | The account changes world or dimension, or the server transfers it to another server. |
| Shard Count | DonutSMP only. Your shard count reaches Min Shards, checked every five minutes. It cannot be combined with other events. |
| Nearby Enemy | Tier 3. A player who is not on your Friends list is seen near the account, the same detection Raid Alerts uses. |
| On Day, On Night | The world time crosses into day or into night. |
Set the cooldown
Cooldown is the shortest gap between two runs on the same account, in milliseconds. The default is 5000; 0 allows back-to-back runs.
Activate it
Select the accounts and click Activate (or Save). The macro appears under Active Event Macros with an on/off switch per account, and Stop Event Macros deactivates everything.
Expect one run at a time
While an event macro is still running, the same event is ignored until it finishes. Different event macros run independently, so keep each one short.
Run a macro when an account joins
Open Settings → Behavior → Join actions and pick the macro under Join Macro. It runs once for every account each time it connects, after the Join macro delay. Turn on Loop the join macro to repeat it with its own loop count and delay, or Infinite to keep it going until the account disconnects. Join macros need Tier 1.
An account’s own settings in Overview can pick a different join macro for that account alone. Because a macro that is already running restarts instead of stacking, a join macro after a reconnect replaces the earlier run rather than doubling it. Read Run a command on join for the join command that usually comes first.
Scheduled Macros
The Scheduled Macros panel under the builder runs a saved macro at a clock time, repeating if you want, even while the dashboard is closed. Click New Schedule.
| Field | What to set |
|---|---|
| Macro, Accounts | The saved macro and the accounts to run it on, up to 100. Accounts must be connected when the schedule fires; offline ones are skipped for that run. |
| Timezone | Search by city, country, or UTC offset. Times below are read in this zone. |
| Start | A date and time, or a quick pick: in 15 minutes, 1, 6, 12, or 24 hours. The preview shows exactly when it fires. |
| Repeat every | Minutes, hours, or days, with Hourly, Every 6h, Daily, and Weekly picks. 0 runs once. |
| Total runs | A count from 1 to 1000, or Unlimited. |
| Stop macro after | How long after each start the macro is stopped, in minutes or hours. 0 lets it finish on its own. |
| No more runs after | An optional end date and time. |
Schedules fire with 30-second precision. A run missed by more than six hours, for example while the service was down, is skipped rather than fired late. Each row shows its next run in its own zone with a countdown, and has Edit, Pause or Resume, and Delete. You can keep up to 50 schedules. The assistant can fill this form in from a sentence such as “run this every day at 7pm for 2 hours”.
Loops, stagger, and day or night
| Setting | What it does |
|---|---|
| Loops, Forever | How many times the steps run per start, up to 1000, or until stopped. |
| Between loops | A pause between one loop ending and the next starting, in seconds. At least one second when Forever is on. |
| Stagger accounts | When running on several accounts, waits this many seconds between starting each one. Accounts still waiting show QUEUED under Active Macros. |
| Stop on error | Ends the run when a step fails. Off means log it and continue. |
| Stop when world turns | Checks the world time every second and stops the run the moment the world enters day or night. A run started in that phase stops right away, so Day means a night-only macro. |
| Loop alert | Sends a Discord message after every completed loop, to a webhook URL or, on Tier 3, through your bot to a channel. Leave the message empty for a default that names the account, the loop number, and the macro, or write your own with %loop% and the other tokens. A loop that was stopped or failed sends nothing. |
Combine them for a night-only routine: On events with On Night ticked, and Stop when world turns set to Day. For a manual version, put Wait For Time night as the first step instead.
Stopping, and what stays on
Each row under Active Macros has its own Stop; Stop Active Macros stops every run and cancels a stagger that is still queuing accounts. A manual macro that is running when the account disconnects pauses and carries on about thirty seconds after the account is back in the world; an Automation step does not resume. A held Sneak or Jump from a macro step stays on after the run ends, and a Disconnect step with Cancel Auto Reconnect keeps the account offline until you press Connect.
Check the troubleshooting guide or return to all guides.