Features79 min read

Macros

Automate your accounts with MinecraftAFK macros: pick the event that starts a flow, chain its steps, then run, stop and troubleshoot it from the Macros page.

If you wish to automate tasks or set up a specific join flow, this is the right place. Macros are built on a visual canvas: pick the event that starts the flow, then chain the steps it runs, left to right. A simple macro is an event and a couple of steps; a bigger one repeats a group of them, or takes one path rather than another depending on what the bot can see. Macros are what turn an account into a Minecraft bot that works through its jobs on its own.

This page is the builder's reference, every event, every step and how they fit together, followed by Running macros: the Macros page itself, how many macros your plan includes and what stops one. Macro variables covers remembering values, and the macro library has ready-made macros to add instead of building your own.

Building a flow

  1. Visit minecraftafk.com/dashboard/servers/ and open the server profile.
  2. Open its Macros page and click Create macro. The builder opens over the whole screen, with the event card at the start of the flow.
  3. Click the event card and pick what starts the macro under Runs when (see Events).
  4. Click Add step, or the plus button at the end of the flow, and pick a step (see Actions).
  5. Click Create macro at the top right to save it.

The field at the top left names the macro, up to 40 characters; left empty, the macro is called after its event, like "Join macro". The square beside it picks the item the macros table pictures it by, which is the event's own until you choose one. The account list beside them picks the accounts it runs on. With All accounts ticked it also runs on accounts you add to the profile later; with only some ticked, it stays on those.

Steps run in the order they are connected. Select any step to edit it in the side panel, where Step name renames its card and Wait before this step sets the pause before it runs. Drag steps around to arrange the canvas however you like; the connections decide the run order. A step dragged off the flow is parked rather than deleted: it reads "Not connected" and does nothing until you wire it back in.

To move a step to a different place in the run order, drag its card onto any plus button: the button lights up while you are over it, and dropping there puts the step in that slot and joins the chain back up behind it. Dropping anywhere else just moves the card, so arranging the canvas and changing the order stay two different things. A Repeat, an If or a One at a time moves as a whole region, body and all.

Right-click a card (or press and hold it on a touch screen) for Edit step, Duplicate step, Remove incoming connection, Remove outgoing connection and Delete step. The toolbar in the bottom left zooms, fits the whole flow on screen, undoes and redoes, and its keyboard button lists the shortcuts:

KeysWhat they do
Space, / or Ctrl+KAdd a step after the selected one
Ctrl+DDuplicate the selected step
DelDelete the selected step
Ctrl+Z, Ctrl+Shift+ZUndo, redo
Ctrl+EnterSave
Arrow keysMove along the flow, and between an If's branches
Enter, EscOpen the selected step's panel, and leave it

On a Mac, use Cmd where the table says Ctrl.

The header says what is wrong with the macro, one thing at a time, with a Show step button that takes you to the card. Something missing or broken, like a Chat step with no message or a Go to step aimed at nothing, is in red and keeps the save button off. A step your plan does not include keeps it off too, with a See plans button beside it. Advice, in yellow, leaves it on. A macro holds up to 100 steps.

To try a macro without waiting for its event, use Run now on its row. While a macro runs on a bot, that bot's POV controls stand down, and Take over there ends the run so you can drive the bot yourself.

Events

MacrosBuild your own advanced macros to automate any in-game action.

An event is what starts a macro. When it is detected, the flow runs.

Join, World change and Called are on every plan. Every other event needs Tier 3: it sits in the picker tagged "Tier 3", and picking it takes you to your plan rather than selecting it.

  • Join (a bot joins the server)
  • Disconnect (a bot loses its connection, or is disconnected)
  • World change (switching world or dimension)
  • Called (nothing starts it: another macro's Run macro step does, or you do)
  • Timer (repeatedly, on an interval counted from when the bot connected)
  • Schedule (at a time on the clock, once or every few hours, days or weeks)
  • Death (a bot dies)
  • Chat message (a received line matches your text or your regex)
  • Damaged (a bot takes damage)
  • Mob appears, Mob leaves (a matching mob comes into or goes out of view)
  • Player appears, Player disappears (a player comes into or goes out of view)
  • Player joins, Player leaves (a player enters or leaves the server, whether or not the bot can see them)
  • Inventory full (the last free inventory slot is taken)
  • Item appears, Item disappears (a matching item turns up, or is used up, dropped or broken)
  • Teleported (the server moves a bot a long way)
  • Window opens (a chest or menu screen opens)
  • Sign opens (the sign edit screen opens)
  • Dialog opens (the server opens a dialog)
  • Text appears on screen (a title, subtitle, action bar or boss bar shows text that matches yours)
  • Bot stops moving (a bot has held still for a moment)
  • Block in range (a block you pick is within reach)
  • Night / day (night falls, or day breaks, on the game's own clock)
  • Tool durability (the item in a slot you pick is down to a number of uses you pick)
  • Potion effect (the bot gets an effect you pick, loses it, or has only a few seconds of it left)
  • Block broken (a block near the bot is broken, by anyone)
  • Sound plays (the bot hears a sound you pick)

Timer and Schedule are the two clock-driven ones, and the difference is worth keeping straight: Timer counts an interval from whenever the bot connected, while Schedule lands on the wall clock, so 15:00 is 15:00 however long the account has been up. They are also the two that can bring an offline account online, with a Connect step.

Timer's Interval runs from one second to 24 hours, five minutes to begin with. Switch on Random beside it and it takes a range instead, waiting a new amount inside it before every pass, so the macro does not run to the same beat every time. Schedule takes a date, a time and a time zone, and its Repeat switch runs it again every so many hours, days or weeks.

Disconnect is the one event that limits what the flow can do. The bot has already gone by the time it fires, so only Discord webhook and Notify my devices steps run: there is nothing left to click, type or walk with.

Called is the odd one out: it is not an event at all. A macro on it never starts by itself (no login, no clock, no chat line) and runs only when something asks for it, which means another macro's Run macro step, or Run now on the Macros page. It is what you give a job that several macros need: build "sell everything" once, put Called on it, and have the farm macro and the mining macro both run it, instead of drawing the same twelve steps twice and keeping them in step forever.

It runs every kind of step, unlike Disconnect: the bot is connected and waiting, so a called macro can do anything a Join macro can. It also does nothing at all until something calls it, so a Called macro sitting on its own is not broken: it is waiting.

Event settings

Most of the events the bot watches for take settings, in the panel under Runs when, that narrow what sets them off. The same settings come back wherever the event is used again: in a Wait for step, in a stop condition, and in the matching If check, such as Window is open for Window opens.

EventSettings
Chat messageMessage: the text to look for
DamagedDamage or attacker: the kind of damage or what dealt it, such as zombie or fall
Mob appears, Mob leavesMobs: the mob types to watch, any mob if empty
Player appears, Player disappears, Player joins, Player leavesPlayers: the usernames to watch, any player if empty. Never fire for these players, Or names matching and Ignore my own accounts leave players out
Mob appears, Player appearsOnly within (blocks): how close one has to come, up to 32. Empty is anywhere the bot can see
Inventory fullCount the open container as well
Item appears, Item disappearsItem, picked from the game's own item list, any item if empty. Watch the open container too
TeleportedMoved at least (blocks), 16 unless you change it
Window opensWindow title or type: the title is tried first and then the menu type, so Auction House and anvil both work
Sign opensSign text
Dialog opensDialog title or text
Text appears on screenText on screen
Bot stops movingStill for at least (ms), 750 unless you change it
Block in rangeBlock (it needs one) and Within (blocks), 16 unless you change it and 32 at most
Night / dayTime of day: Nightfall or Daybreak
Tool durabilityItem in and Down to (uses left)
Potion effectEffect (it needs one), Level, any level unless you pick one, When the bot gets it, loses it or runs low on it, and for Runs low Down to (seconds left), 30 unless you change it
Block brokenBlock, any block if empty, and Within (blocks)
Sound playsThe sound, and Within (blocks)

A list of names takes one name per tag: type it and press Enter. Mobs go by their type, such as zombie or creeper, and players by username. A name matches whole, with capitals ignored, and a list holds up to 32. Ignore my own accounts is ticked to begin with, so your other bots never set the event off.

Or names matching leaves out every player whose username fits a pattern, up to 8 of them: ^Staff_ for names that start with Staff_, _alt$ for names that end in _alt. They are regular expressions, compared with capitals ignored. A pattern that could slow the bot down, such as (a+)+, or one that matches every name is refused as you add it, with the reason under the box.

Block in range fires the first time a block of that type is in range, straight away if one already is when the macro starts. It searches the chunks the bot has loaded, so a block in an unloaded chunk is not there as far as the bot is concerned.

Player appears has a Smart trigger box, ticked by default, for the times the bot is moved among players rather than approached by one. While it is ticked, the event doesn't fire for 5 seconds after the bot is teleported, or while 5 or more other players are in sight at once, which usually means the bot was sent to a hub, a lobby or spawn. Players under Never fire for these players or Or names matching don't count towards the 5, and neither do your own accounts unless you untick Ignore my own accounts. Untick Smart trigger to have it fire for every player that appears. The box is on the event that starts a macro or a webhook: a stop condition or a Wait for step on Player appears always fires.

Night / day follows the clock inside the game rather than yours. Pick Nightfall or Daybreak under Time of day: night runs from 13000 to 23000 on the game clock, the same line /time set night and /time set day draw, so a macro that sleeps or heads for shelter goes off when the monsters come out. A server that stops its clock never crosses the line, so the event never fires there. With "Also fire if it is already night" ticked, which is the default, a bot that joins after dark runs the macro straight away instead of sitting through that night.

Tool durability watches one item the bot is using: pick the slot under Item in (main hand, off hand, or one of the four armour pieces) and how many uses it should have left, ten by default. That is the first number the game shows in the tooltip with advanced tooltips on (F3+H), "Durability: X / Y". It fires once when the item gets down to that many, and again only after it has gone back above, because it was repaired or a fresh one was swapped in. If the item is already that worn when the macro starts, it fires straight away. An empty slot, or an item that does not wear out, never fires it.

Its main job is stopping a hold before the tool breaks. A bot holding right click with a fishing rod, or holding left click on a wall of stone, keeps going until you tell it to stop, and on durability it never stops by itself: a Mending rod on an XP farm is often fished right down on purpose, so where the floor sits is your call. Put a Release right click (or Release left click) step on a Tool durability macro and the hold lets go at the number you picked. As a stop condition on the macro doing the holding it does the same job: the macro stands down, and a hold with Release when the macro stops ticked lets go. There is a short delay between the event and the step that answers it, so leave a margin on a fast tool: a pickaxe tearing through stone can lose a few uses in that time.

Potion effect watches one of the bot's own effects, whether it came from a potion, a beacon, food or the server. Pick it under Effect, and under Level whether only a stronger one counts (Strength II or higher, say). Then pick when it fires:

  • Gets it fires when the bot gets the effect, and again only after the effect has worn off and come back.
  • Loses it fires when the effect ends: it ran out, milk cleared it, or the bot died.
  • Runs low fires when the effect is down to the seconds you pick, 30 by default, and again after it has been topped up. Having none of it at all counts as low, so a macro that drinks a potion on Runs low drinks as soon as it starts if the bot has none, and then again shortly before each potion ends. An effect that never runs out, such as one a server gives with a command, never runs low.

With "Also fire if" ticked, which is the default, a bot that already has the effect (or already lacks it, or is already low on it) when the macro starts runs it straight away. Glowing, Luck, Bad Luck and Dolphin's Grace don't exist on Bedrock, so they only ever fire on a Java account.

Block broken fires when a block near the bot turns to air, whoever broke it, the bot included. Pick a block to watch for one kind, or leave it empty for any block, and set how far to watch under Within (blocks), 16 blocks by default and 32 at most. It counts breaks as they happen, so a block that was already gone when the macro started never fires it. A block broken underwater turns to water rather than air, so it does not count. A bot mining a vein breaks a block every few moments, so give a Block broken macro a cooldown if you only want to hear about it once in a while.

Sound plays fires when the server plays a sound you pick where the bot can hear it, whoever or whatever made it. Pick the sound from the list, which holds the game's own names (entity.player.levelup for a level-up, block.note_block.pling for a note block), or type the id of a sound the server adds itself, like myserver:ding, and pick "Use" under it. Leave Within (blocks) empty to hear it at any distance, or set it to at most 32 blocks. It counts sounds as they arrive, so one that played before the macro started never fires it. It only hears what the server actually sends the bot: the game leaves a player's own sounds out of what it sends that player, so the bot's own footsteps and swings never count.

Sounds are named the Java way on every account. A Bedrock account hears them through Geyser's translation, and a few Java sounds share one Bedrock sound while Geyser makes some sounds up on its own (the splash of a fishing bobber, for one), so on Bedrock a similar sound can occasionally set it off. Sound plays does not work on 1.7, 1.8 or 1.9 to 1.9.2: the macro saves, but never fires there. On 1.13 and 1.13.1 it hears the game's own sounds but not ones a server adds itself.

Text appears on screen fires when a title, subtitle, action bar or boss bar shows matching text (colours removed); on Bedrock, popup and tip text counts as the action bar. It fires once while the text stays up, even as a countdown ticks, and again after it has been gone a second: give it a cooldown longer than the countdown to run it once. It never fires on 1.7 and sees boss bars from 1.9.

Also fire if, ticked by default, runs it at once for text already up when the bot joins, so match something specific like restart in. A Wait for counts text already up only if its own box is ticked.

Matching text

Every text box in the table above (Message, Damage or attacker, Window title or type, Sign text, Dialog title or text, Text on screen) has a menu beside it that sets how the text is compared: contains, the default, is exactly, starts with, ends with or regex. Left empty, the box matches anything, so a fresh Chat message macro runs on every line it receives.

Every mode but regex ignores capitals. A regex matches them exactly, and it is checked by the bot when the macro starts rather than when you save it: one that does not compile stops every event on that bot, not just the one it is on.

Also fire if it is already true

Some events describe a state as well as a change: a window being open, a full inventory, a player standing nearby. Those carry an Also fire if box, worded for the event ("Also fire if a window is already open"). It is ticked by default on Mob appears, Player appears, Inventory full, Item appears, Window opens, Sign opens, Dialog opens, Text appears on screen, Night / day and Potion effect.

Ticked, the macro also runs the moment it is armed, usually when the bot joins, if the state is already true, and then on every change after that. Unticked, it waits for a change. Player joins has the box too, unticked, since "a player joined" is news and "a player is online" is not. On a Wait for step the box starts unticked, so the wait holds for something that happens after the step begins.

Cooldown

The events in the table also take Don't run again for. After the event fires, it is ignored for that long, up to 24 hours: a firing inside the window is dropped, not saved for later. Leave it empty for no cooldown. It is the setting for an event that can fire many times a minute, like Block broken on a bot mining a vein or Chat message on a busy server. Join, the clock events and the other connection events have none, and neither does a Wait for step, a stop condition or a check.

Actions

Add steps with the plus button at the end of the flow, or with the one on the line between two steps to put a step between them; they run in the order they are connected. Each step waits before it runs, one second by default and up to an hour, and that wait takes a random range as well as a fixed number, so a flow need not run to the same beat every time.

The step picker groups the steps as below, and its search box matches a step's name, its one-line description or its group.

Communication

  • Chat (send a message or command)
  • Discord webhook (post to a Discord channel, Tier 3)
  • Notify my devices (send a push notification to your phone or computer, Tier 3)
  • Write on sign (fill in the sign edit screen the server opens)

Clicking

  • Left click once (hit a mob, mine a block, or swing at air)
  • Hold left click (keep left clicking until released)
  • Release left click (let a held left click go)
  • Right click once (place, use, or interact with what is ahead)
  • Hold right click (keep right clicking until released)
  • Release right click (stop using: fires a drawn bow, lowers a shield)
  • Start autoclicker (keep clicking a mouse button at a random rate you set, Tier 3: see The autoclicker)
  • Stop autoclicker (switch the autoclicker off)
  • Fish (cast the fishing rod in hand, and reel in when a fish bites)

Inventory

  • Use GUI (click a slot in an open container, such as a chest or a furnace, or name an item and let the bot find it)
  • Use inventory (click a slot in the bot's own inventory, or name an item)
  • Close window (close an open container or a server dialog)
  • Press dialog button (press a button on a dialog or Bedrock form the server opened, such as a server selector: see Dialogs and forms)
  • Trade (buy from the villager or wandering trader whose window is open, by the item you want)
  • Hold item (switch to a specific item, or to a hotbar slot)
  • Swap hands (swap the main hand and off hand; skipped on versions before 1.9, which have no off hand)
  • Drop (drop a specific item, one or a whole stack)
  • Drop all (drop the whole inventory, or only items matching a name)

Movement

  • Move (walk forward, back, left or right, a number of blocks)
  • Walk to (walk to a waypoint, a block you name, or the nearest block or entity, finding the way there: see Walk to in a macro)
  • Mine area (mine every block between two corners, Tier 3: see Mining and farming an area)
  • Farm area (harvest the ripe crops between two corners and replant them, Tier 3: see Mining and farming an area)
  • Gather (get a list of items however the bot can, by mining the blocks and hunting the mobs that drop them, Tier 3: see Gathering items)
  • Look (aim by dragging a head around a compass, by preset, or by typing Up/Down and Left/Right angles)
  • Look at entity (turn to a player, a mob or a named entity, wherever it happens to be)
  • Look at block (turn to the nearest block of a type you name)
  • Look at variable (turn to the block or entity a For each loop is on, Tier 3)
  • Sneak once (one crouch tap, the way tapping shift does)
  • Hold sneak (crouch, and stay crouched)
  • Release sneak (stand back up from a crouch)
  • Jump once (one hop, the way tapping space does)
  • Hold jump (keep jumping until released)
  • Release jump (let a held jump go)
  • Enable auto eat (eat from the food the bot is carrying whenever it gets hungry, Tier 2 or Tier 3)
  • Disable auto eat (switch auto eat back off)

Control

  • Wait (pause before the next step)
  • Wait for (hold until something happens, rather than for a length of time)
  • Connect (log an offline account in, as the first step of a Timer or Schedule macro)
  • Reconnect (log the account off and back on, which ends the flow)
  • Disconnect (log the account off)
  • Panic logout (look around in a panic, then log off)
  • Run macro (queue another macro on this profile, or this one again, Tier 3)

Logic

  • Set variable (remember a value for a later check, message or click: see Macro variables)
  • Repeat (run a group of steps more than once)
  • For each (run a group of steps once per player, block, entity, item or value)
  • If (send the flow one of two ways)
  • Restart macro (go back to the first step and run it all again)
  • Go to step (jump to any step, forwards or back)
  • One at a time (let only one account run a group of steps at a time)

Use GUI

Use GUI clicks in an open container, such as a chest, a furnace or a server's shop menu, and Use inventory clicks in the bot's own inventory. What to click decides how the step finds its slot:

  • A slot: pick the menu under Container type (or Custom, with its columns and rows), then click the slot in the grid.
  • Only these items, Every item except these, An item by name or An item by lore: the bot finds the item itself. The first two take one item or several from the item list: Only these items clicks any of them, and Every item except these clicks everything else, so one step can drop or sell all but your tools. What the bot wears and holds in its offhand counts as everything else too, so add those to the list to keep them.
  • An item I found earlier: the exact slot a Set variable step or a For each over items found, named under The variable that found it. The bot checks the item is still in that slot before clicking and skips the step if it is not, so a menu that has changed pages or closed costs a missed click rather than the wrong purchase. See Macro variables.

Naming an item is what you want when the slot isn't predictable (a shop menu, a chest someone else fills). The bot looks through any open container first, then its own inventory, and the step's Target setting picks the first match, the last, or every one of them. A name or a lore line matches part of the text, with capitals ignored and colour codes stripped, so type the words as they read on screen. Because the search covers both windows, a step set to an item reads as Use GUI whichever of the two you started from.

Action picks the click: Left, Right, Shift Left, Shift Right, Drop 1, Drop Stack or Move to Hotbar Slot, plus Hold Item and Right Click Held Item on a hotbar slot. In a vanilla menu both shift clicks move the whole stack across, but a server's own menu can give each one a job of its own, and its item tooltips usually say which, so pick the one the menu names.

Move to Hotbar Slot does what pressing a number key over an item does in the game: the item trades places with whatever is in the Hotbar slot you pick, numbered 0 to 8 as Hold item numbers them. Aimed at an item rather than a slot, it gets an item into the hotbar without you knowing where it is: An item by name for your sell axe, moved to hotbar slot 0, then a Hold item on slot 0. If a match is already in that hotbar slot, nothing happens. It moves one item per step, so its Target is the first match or the last.

One step can also click a whole run of slots, left and right button mixed. Click them in the grid in the order the bot should click them, right-clicking the ones it should right click, or type the run into the slot field: 13L, 14R, 13L left clicks slot 13, right clicks slot 14, then left clicks slot 13 again. A slot may appear as often as you need it to, so a run is a list of clicks rather than a set of slots. The other actions (shift left, shift right, the two drops, and the two hotbar ones) stay one per step, and Move to Hotbar Slot moves a single slot.

Wait for the window to open is ticked to begin with on Use GUI. Nothing is clicked until the window is there, so the step cannot fire into a menu that has not appeared yet; if none opens within 30 seconds, the macro carries on to the next step. On an item target, an item the bot can already reach, in its own inventory included, is clicked straight away. Untick the box and the step clicks as soon as its own wait is up. Use inventory has no such box, because the bot's own inventory is always open.

Close what you open. A Chat step closes an open menu before it sends, and so does any step that moves or acts, the way a player presses Escape. So a Chat step between two Use GUI clicks closes the menu, and the second click finds no window. A menu left open at the end stays up until something closes it, and anti-AFK pauses meanwhile. The builder flags that ("This macro leaves the GUI open"), and Add Close window in its header adds the step for you, as an ordinary card you can move or delete. It cannot see a menu that a command like /ah or a right click opened, so close those yourself.

Dialogs and forms

Some servers open a dialog rather than a chest when you use their compass or run one of their commands: a server selector, a rules screen, a shop. On Bedrock every server menu is one of these (Bedrock calls them forms), and Java servers can use them from 1.21.6 on. You can answer one yourself in the POV, and Press dialog button answers one from a macro.

Name the button by its text, the way it reads on screen. Part of it is enough, and capitals and colour codes are ignored, so one block presses a button that reads ONE BLOCK with a line of description under it. When your words fit more than one button, a button that says exactly what you typed wins, then the first one that contains them.

For a button whose words have something else between them, such as a symbol or a player count, put a * where that goes: ONE*BLOCK presses a button that reads ONE ⚔ BLOCK, and PVP*ONLINE one that reads PVP (12 online). The parts have to come in the order you typed them, and the first button they fit is pressed. A * on its own presses the first button, whatever it says.

If one of your bots has a dialog up while you edit the step, its buttons are listed under the field: clicking one fills it in, and the one your text would press is outlined in green.

The step presses whichever dialog is open, so put it after the step that opens one, such as Hold item on the compass and then Right click once. Wait for the dialog to open, ticked to begin with, gives the dialog up to 30 seconds to appear, like Use GUI's window wait. If no dialog opens, or none of its buttons match, the step is skipped and the macro carries on, and the macro log says which. A Bedrock form with fields to fill in has one button, Submit, which sends the fields as they are.

A dialog that stays up after its button, or one you want gone without pressing anything, closes with a Close window step, the same step that closes a chest. A Chat step or a step that moves or acts closes it too. When a macro ends on Press dialog button with nothing after it to close the dialog, the builder says it may leave a dialog open, and Add Close window puts the step straight after the button.

To start a macro when a dialog appears instead, use the Dialog opens event.

Signs

Placing a sign is an ordinary right click, but the game then opens its edit screen and waits for the four lines. Write on sign is the step that answers it, so a flow that puts a shop sign up is Hold item, Right click once, Write on sign.

It writes whichever sign screen is open, because that is all the game gives it: there is no way to name a sign by its coordinates, only to answer the one in front of you. Put the step after the right click that places the sign, and give that click enough of a delay for the screen to arrive. With no screen open the step is skipped and the macro carries on.

Leaving all four lines blank is a real step rather than an unfinished one. Minecraft has no cancel on that screen, so something has to answer it, and blank lines are what a sign you walk away from ends up saying anyway.

A line can hold a variable as {name}, for a server that asks for a number on a sign, such as an amount the macro worked out earlier. Each line takes fifteen characters, the game's own limit, and the name counts toward them as you type it, braces and all.

Trading

Trade buys from a villager or a wandering trader. You name the item you want, not the place it sits in the list, so one step works on any villager that sells it: the bot picks the trade that gives that item, pays from its own inventory, and takes what it bought. If a trader sells the same item two ways, tick Only the trade paid with a certain item to pick one.

Amount is either One trade, or As many as it can: the bot keeps trading until it runs out of what the trade costs, the villager sells out, or its inventory is full. Selling is trading too, so a farmer's "20 wheat for an emerald" is a step that gets emeralds.

The trading window has to be open first, the same way you would open it: point the bot at the villager with Look at entity, then Right click once. Wait for the window to open, ticked to begin with, gives the window up to 30 seconds to appear, like Use GUI's. If the villager has no such trade, is sold out, or the bot cannot pay, the step is skipped and the macro carries on, and the macro log says which. A villager restocks at its workstation; a wandering trader never does.

On Java Edition, trading needs 1.14 or newer, and on older versions the step is skipped. Bedrock accounts trade on every version. See Villager trading for every setting and every reason a trade is skipped.

Clicking

MiningMine for resources or excavate large areas.

The six click steps are the two mouse buttons, and they do exactly what those buttons do in the game. Nothing asks you what you are clicking at: the bot looks at what is in front of it and what is in its hand, and the game decides, the same way it does for you.

So a left click hits the mob in front of it, or mines the block in front of it, or swings at air. A right click places the block it is holding, opens the door in front of it, feeds the animal, eats the food, casts the rod. You do not pick which one, because a player does not either.

Nothing aims for you, so put a Look step in front of a click to point the bot at what you want. To place or use a specific item, put a Hold item step in front to switch to it first; the item has to be in one of the nine hotbar slots, since that is where a player switches from. If it may be in the main inventory, a Use GUI step's Move to Hotbar Slot puts it in the hotbar first.

Left click once and Hold left click carry two boxes, Hit entities (mobs, animals and players under the crosshair) and Break blocks (whatever block the crosshair is on). Both start ticked, which is the plain left click, and the last ticked box cannot be unticked. They matter most on a hold. With Break blocks off, a bot hitting mobs at a farm stays on mobs, and cannot start mining the floor once the one it was hitting dies. With Hit entities off, a mining bot never swings at a mob that walks past.

While Break blocks is ticked there is a third box, Switch to the best tool, off to begin with. Ticked, the bot holds whatever breaks the block fastest before it starts on it: anything on the hotbar, or a tool from its inventory when that beats everything on the hotbar, which it moves onto the hotbar first (its inventory opens for a moment to do that). A tool that gets the block's drops wins over a faster one that does not, so stone goes to a pickaxe rather than to a bare hand, and a tool with one use left is never picked, so it does not break on the next block. A held click picks again for every block it chains into, never part way through one, since changing what is in hand mid-block starts the block over. Hitting a mob and swinging at air switch nothing. It only switches in survival: a bot in creative or adventure mines with whatever it holds. Left unticked, the bot mines with whatever it is holding, so put a Hold item step in front to choose it.

A left click aimed at a block holds the flow until the block has finished breaking, so the step after it starts from a hole rather than from a block that is still there, and its own wait is counted from the break. Nothing else waits: hitting a mob and swinging at air are over the moment they happen.

Holding a button

Hold left click and Hold right click press the button and keep it pressed, which is a different thing from clicking quickly in a loop:

  • Holding left click chains from one block into the next, each block taking its own full mining time, and keeps hitting a mob at the normal swing rate.
  • Holding right click clicks at the same rate a real player's mouse does, and watches what the bot is holding so it does not interrupt itself. Food and potions are eaten one item at a time rather than restarted, and an item that charges up (a bow, a shield, a spyglass) is pressed once and stays pressed.

A hold stays on between passes, which is the point of it: an AFK macro that holds left click on join keeps mining without running again. Add the matching Release step where you want it let go part way through a flow.

The two holds need Tier 3; the single clicks and the two releases are on every plan. On a lower plan they stay in the step picker tagged "Tier 3", and picking one takes you to your plan rather than adding it, the same as the Logic steps.

Older macros may still contain Attack, Break block or Place block steps, from before the clicks were simplified. They keep working and stay editable, but they are no longer offered as new steps: the six clicks above cover what they did.

The autoclicker

Start autoclicker is the Clicking tab's Autoclicker as a step: the bot clicks a mouse button again and again at a random rate, with the card's settings. Stop autoclicker switches it off, whichever button it is clicking. Start autoclicker needs Tier 3, like the holds; Stop autoclicker is on every plan. What each click does, how it shares a button with a hold, and when it stops are on its own page: see In a macro.

Fishing

AFK fishingAutomatically fish while you are away.

Fish casts the fishing rod the bot is holding, with a right click, and the bot reels it in by itself the moment a fish bites, with a second right click, the way a player watching the bobber would. One Fish step is one cast and one catch.

The rod has to be in the bot's hand, in the selected hotbar slot. Without one the step does nothing at all, rather than right clicking with whatever else is held, and the macro log shows an error. Put a Hold item step in front of it if the rod might not be selected.

The macro carries on as soon as the line is out; it does not wait for the fish. To keep fishing, put the Fish step inside a Repeat (Tier 3). While a line is still out waiting for a bite, a Fish step leaves it alone, so the first one to run after the catch casts again.

Mining and farming an area

Mine area and Farm area hand the bot a whole box to work. You set two corners, the bot walks to the work and does all of it by itself, and the macro carries on once the job is over. Type the corners, paste a spot into any of the fields, or set Set Pos 1 and Set Pos 2 from the game menu in the POV and pick Use the POV selection on the step. An area is at most 64 blocks wide and long, and up to 384 tall.

Mine area breaks every block in the box, from the top layer down, nearest first. For each block it picks the hotbar item that breaks it fastest (a tool in the inventory too, when it is better than anything on the hotbar), and never uses a tool that has one use left. Set Blocks to mine only some blocks, or every block but some. It leaves bedrock and anything else nothing can break, blocks it has no tool to get drops from, and blocks that water or lava touches from above or the side, so a pit does not flood. A block with water or lava straight under it stays as well, so the floor the bot stands on never turns into open water. A block holding up sand or gravel that touches water or lava stays too, since the sand would drop and let the water in. Gravel and sand that fall in are mined as they land.

The bot only walks: it never builds its way up, and it never walks into water while it works. A block it cannot walk close enough to reach, such as the top of a tall tree, is left, and the job works on below it. Once a bot is down in the pit it works downward, and does not climb back up the staircase for blocks left high on the walls. The roof of a cave (a block with more than three blocks of air under it, or lava) is only broken from underneath, by a bot standing below it, and never while someone stands on that roof nearby, so nobody falls through the floor. It never breaks the block another player is standing on. A bot that ends up under water swims up to breathe, and one that water carries off its feet walks or wades back to dry ground and carries on.

Where the pit goes below the ground round the box, it leaves one block per layer along the edge of the box, a staircase it can walk back up, with a railing block beside each step on the pit's side so nobody is pushed off it. Untick Leave a staircase out of a pit to mine those too.

Several accounts can work one box at once: they spread out over it, and they all keep the same staircase. An account that holds sneak stands up while it works and crouches again when the job ends.

Farm area harvests every crop in the box that is fully grown and leaves the rest to grow: wheat, carrots, potatoes, beetroots, nether wart, cocoa, melons, pumpkins, sugar cane, cactus, bamboo and sweet berries, or the ones you tick. With Replant what it harvests on, each crop that grows from a seed gets one back from the inventory, and any bare farmland (or soul sand, for nether wart) in the box is sown too, with the crop that grows most round it. The bot plants from a spot where its aim reaches the soil past the crops around it, and it never jumps on farmland, which would trample it. Sugar cane, cactus and bamboo keep their bottom block, melons and pumpkins their stem, and sweet berries are picked off the bush.

With Pick up the drops on, the bot walks over what falls, and the step ends when the inventory is full. Follow it with the steps that empty it and a Restart macro, and the next run picks up where the last one stopped: the bot only ever works on what is still in the box.

The step waits for the job for up to an hour, then stops it and the macro carries on. The POV draws the box in gold and, through anything in the way, the block the bot is working on or walking to in white and the ripe crops a farm has lined up after it in gold, with the count in the corner. A movement key pressed in the POV stops the job, as it stops a walk. Java servers only, for now.

The block pickers on other steps (Walk to, Look at block, For each, the block events and checks) have a Growth choice for crops: Fully grown finds only crops that are ready, so a loop over wheat skips the sprouts. You can also type a block with any state the game knows, such as furnace[lit=true], and pick Use under the search.

Gathering items

Gather takes a list of items and how many of each the bot should have, and the bot gets them by itself: it picks up any of them lying nearby, mines the blocks that drop them and hunts the mobs that drop them, whichever is closest, until the inventory holds the count of every item. Like a player, it mines everything in reach of where it stands before it picks anything up, then walks over the spots it mined, which picks the drops up as it goes. A drop that another of your bots has just mined is left for that bot to pick up. Pick the items from the list on the step, which only offers items something in the game drops, and set a count beside each one, up to 2304, or press the infinity button beside it for no limit: the bot then keeps collecting that item until the inventory is full. Under each item the step says where it comes from, such as Mines coal ore or deepslate coal ore or Kills skeletons, strays or bogged. The count is what the inventory should hold, so what the bot already carries counts toward it, and a step run again only gathers what is still missing. Tick In total across all accounts to make the counts shared by every account running the step: they gather the items together, and all of them stop once they hold every count between them. The POV then shows the total for all of them.

It mines with the hotbar item that breaks a block fastest (a better tool from the inventory too), never uses a tool with one use left, and skips blocks it has no tool to get the drop from, such as coal ore without a pickaxe. It hunts with the hardest hitting weapon on its hotbar, hits at full charge, backs away from a creeper after every hit, and fights back against a hostile mob that attacks it. It does not shear, fish, craft, smelt or use Silk Touch, and it leaves mobs in the water alone. Wool comes from white sheep only, since the bot cannot tell a sheep's colour.

The bot goes only for what it has seen, like a player: a block, a dropped item or a mob counts once the bot has had a clear view of it, from where it stands or from anywhere it has been during the job. It does not dig around for ore it cannot see. When nothing it wants is in sight, it stands and looks again every second, for a drop to land, a mob to wander by or a block to come into view, and after a minute with nothing it can do the step ends. Tick Max distance to items to keep it close: only blocks, drops and mobs within that many blocks of the bot count, measured from wherever it has got to. Off, it goes for blocks up to 40 blocks away, mobs up to 32 and drops up to 16.

It only ever walks. It never breaks or places a block to get somewhere, so a block, a drop or a mob no walk gets to (behind a wall, up a cliff, across a ravine) is left alone, and the only blocks it breaks are the ones it came for. It never mines a block more than one below its feet either, since the hole that leaves is one it could not climb back out of. Like Mine area, it leaves any block that water or lava touches from above, the side or below, and any block holding up sand or gravel that touches water or lava, so the place it works never floods. If it does end up in water anyway, or on a dry patch with water all round it, it gets itself out to dry ground first, wading through the water if it has to. Gather takes whatever is nearest, so on a server without land claims it will mine blocks and kill animals that belong to other players.

The step ends once every item is gathered, when the inventory has no room for any more of them, after a minute with nothing left in reach that it can get to, or straight away when nothing in the game drops any of them. Tick Stop after a set time to end it after the time you set, in seconds or minutes up to an hour, however much it has gathered by then. With it off, and an item with no limit, the step runs until you stop the macro, for as long as it has something to gather. The POV says why a step that could not go on ended: Nothing left in reach, Trapped by water or Nothing gives these items. Follow it with the steps that empty the inventory and a Restart macro to keep it going. The POV says what it is doing and how many items it has in the corner, and shows what it is after through the ground and walls: the block it is mining or heading for, or the mob or drop it is going to, in white, and the other blocks it knows of and means to mine in gold. A movement key pressed in the POV stops the job, as it stops a walk. Java servers only, for now.

Holding a key

Sneak and jump are split the same way the mouse buttons are, three steps each: tap the key once, hold it, or let it go. There is no state to set inside the step, because the step you picked is the state.

A held key stays down between passes, so a flow that crouches on join leaves the bot crouching without running again. Add the matching Release step where you want it let go part way through a flow.

Sneak once and Jump once are the single taps: press the key and let go, the way you would tapping shift or space. Nothing is left held afterwards, so neither needs a Release step after it. Sneak once does nothing while the bot is already crouching, since there is no key left to press, and Jump once needs physics on, the same as Hold jump.

Macros built before the split keep working: a Sneak step set to start becomes Hold sneak, one set to stop becomes Release sneak, and the same for jump.

Auto eat

Enable auto eat and Disable auto eat switch auto eat on and off from inside a flow. It is the same setting as the Auto eat box on the movement page, so turning it on from a macro is exactly like ticking that box: the bot watches its hunger bar and eats from the food it is carrying, with nothing to pick in the step.

It stays on once it is on. The pass ending, the macro stopping and the account reconnecting all leave it on, so a join macro that enables it keeps the bot fed for as long as it is online. That is different from a held key or button: auto eat has no Release when the macro stops box, because a bot that keeps eating after its macro has stopped gives nothing away. Add a Disable auto eat step where you want it off, or untick it on the movement page.

Enable auto eat needs Tier 2 or Tier 3, the same plans the movement page's Auto eat box is on. On Tier 1 it stays in the step picker tagged "Tier 2", and picking it takes you to your plan rather than adding it. Disable auto eat is on every plan.

Release when the macro stops

Every hold step (Hold left click, Hold right click, Hold sneak, Hold jump) carries one checkbox: Release when the macro stops. Start autoclicker carries the same box, worded Stop clicking when the macro stops.

Stopping is not the same as the flow reaching its last step. A macro stops when one of its stop conditions fires, when a Panic logout step runs, when a Wait for step gives up with Stop the macro if it never happens ticked, when a run fails, or when you turn the macro off or delete it. Between passes the hold stays down either way, so an AFK flow that holds and never releases keeps working.

It is on by default for Hold left click, Hold right click, Hold jump and Start autoclicker. A bot still swinging, still placing, still clicking or still hopping after its macro has stopped is doing it for nobody, and leaving a button down is how an account carries on mining in front of the player who just walked up.

Hold sneak is the exception, and it is off by default. A crouch is usually a position rather than an activity: an account parked in a one-block hole, name plate hidden, unable to walk off the ledge. Standing it up because a stop condition fired would move an account you put there deliberately. Tick the box on a Hold sneak step if you would rather it stood up.

Either way, nothing brings a hold back on its own. A macro that stood down and released the button starts clean on its next trigger.

Waiting for something

Wait pauses for a length of time you pick. Wait for holds until something actually happens, which is usually what you meant: a fixed wait is a guess at how long the server will take, and a guess that comes up short is what has the next step clicking a menu that has not opened yet.

Pick what it waits for from "Wait until". It offers the events the bot watches for itself, so it can hold for a chat line, damage, a mob or a player coming into or going out of view, a player joining, the inventory filling, an item turning up or running out, a teleport, a chest or menu screen, a sign editor, a dialog, text on screen, the bot settling to a stop, a block coming into range, nightfall and daybreak, a tool wearing down, a potion effect starting, ending or running low, a block being broken, or a sound playing. Each one takes the settings it takes as an event, so a Chat message wait matches your text or your regex exactly the way the trigger does. There is no cooldown on a wait, and its Also fire if box starts unticked. A Tool durability wait on a tool that is already worn down to your number does not wait at all.

It can also wait for World change and Death, which hold until the bot next arrives in another world or dies. World change takes a World, matched against either the dimension ("overworld", "the_nether") or the server's own world name, the way the In a world check matches it, * included; leave it blank for any world. Both count a change or a death that lands in the moment between the step before and the wait starting, so a Chat step that sends /survival followed by a World change wait does not miss a fast server.

And it can wait for a Schedule: pick a time, once or every few hours, days or weeks, with the same editor the Schedule trigger uses, and the step holds until the next time it comes round. A Schedule wait has no Give up after and no Stop the macro if it never happens, because that moment is what ends it. A one-off time that has already gone by does not hold the step at all: it continues straight away.

Four are not on that list: Join, Disconnect, Timer and Called. The bot is already connected while a macro runs, so it can never see itself join; once it has disconnected there is nothing left for the steps after the wait to do; a Timer is a length of time, which a plain Wait already is; and Called is not an event at all.

One more is only on that list: Menu refreshes. It holds until the open chest or menu changes after the bot's last click in it, which is what a menu with pages does when you click its page button. Put it between that click and whatever reads the new page, such as a Repeat until an item appears: a fixed wait there is a guess at how fast the server redraws, and one that comes up short reads the old page.

  • The server putting an item back after a click it refused (the usual answer to clicking a button in a menu) does not count. The next page does.
  • A page exactly like the one before changes nothing, so the wait runs to its limit. Give it a short Give up after, two or three seconds, and leave Stop the macro if it never happens off, so the flow carries on either way.
  • A menu that animates counts as refreshed straight away, since it changes on its own.
  • A bot that cannot watch for it yet skips the step and carries on.

Menu refreshes takes no settings, and it is only a Wait for: a macro cannot start on it, a stop condition cannot watch for it, and an If cannot check it.

Every other wait has two settings that belong to the wait rather than to the thing waited for:

  • Give up after bounds it, thirty seconds by default and an hour at most. There is deliberately no "wait forever": a wait for a screen that never opens would be a pass that never ends, holding a bot no other macro on the account could then run.
  • Stop the macro if it never happens decides what a lapsed wait does. Left off, the flow carries on to the next step anyway, which is right for "give the GUI a moment, then click regardless". Turned on, the macro ends there, which is right for the step whose whole point is that nothing after it should run without it.

Wait for is on every plan, even though most of the events it can wait on need Tier 3 to start a macro with. Waiting on a chat line partway through a flow is a different thing from being allowed to start a flow from one, so a Join macro on any plan can watch for something in the middle of its run.

Panic logout

A plain Disconnect drops the connection mid-stride, which is not what a player does when they decide to leave in a hurry. Panic logout is the same log-off done the way a person does it: the bot whips its head around a few times, checking what is behind it, and then goes.

It turns the head and nothing else. The account does not take a step, so it logs off from exactly the block it was standing on, which is what makes this safe to put on an account parked somewhere on purpose.

It is one step with nothing to set. Everything about it is improvised by the bot at the moment it runs, so the same macro never leaves the same way twice: a different number of turns, different directions, a different rhythm. There is no seed to save and no pattern to spot, which is the whole point of it. The only setting it has is the one every step has, the wait before it starts.

A Panic logout also stops the macro on that account, the way a stop condition does, and the account stays off. The Macros page lists it as stopped, with a Reconnect button to bring the account back (Starting again after a stop).

Connect

Connect is the other direction: it logs an offline account in, to this profile's server, exactly as pressing Connect on the dashboard would. On an account that is already online it does nothing and the macro carries on.

Put it first in a Timer or Schedule macro. Every other event fires on an account that is already online, and every step before a Connect needs one too, so anywhere else the step finds the job done; the builder warns you when it sits somewhere it cannot act. Timer and Schedule are different: they keep counting while the account is offline, and when one comes round, Connect brings the account on and the rest of the macro runs once the bot has joined.

  • A Schedule connects the account at the time you pick, once or every few hours, days or weeks. "Every day at 08:00: Connect, then /home" is a morning routine.
  • A Timer counts its interval from when the account went offline, which is the same gap it leaves between passes while the account is on. "Every 2 hours: Connect, farm for an hour, Disconnect" repeats that session forever.

It connects the account even if you stopped it by hand, because a macro that logs the account in at 08:00 is exactly what you asked for. Pause the macro to keep the account off. An account whose login needs attention, or one your plan no longer covers, is not connected.

Reconnect

Reconnect is the third way to log an account off, and the one that arranges the trip back before it goes: the account drops and then comes back on. Reconnect after sets how long it stays off, from 5 seconds (the default) up to an hour, and it comes back even with auto reconnect switched off in the profile's settings. Like Disconnect it is on every plan.

It ends the flow. The log-off it drives is the ordinary one, so it clears everything queued on that connection, which means a step drawn after a Reconnect never runs. That is not a gap waiting to be closed; there is no pass left to carry on with once the connection it belonged to is gone. Put the Reconnect last in the flow, and put whatever should happen once the account is back into a macro of its own.

Not in a Join macro, though. The account coming back is a join, so the macro would run again and reconnect again, and the builder warns that it "will restart itself over and over". If what you want is a bot that comes back after it drops, turn on auto reconnect instead. A Reconnect that runs too often is refused, and the macro log shows Reconnect limited.

Run macro

Run macro hands the job to another macro on the same profile, or back to this one. It needs Tier 3.

The macro it starts is usually one on the Called event, which exists for exactly this: a job several macros need, built once, that should not also be going off on its own.

Pick the macro under Macro to run in the step's panel. This macro is the first entry in it, which is how you say "and then start over".

It queues that macro rather than jumping to it, and that is the one thing to get right before you build around it. An account runs one macro at a time, so the macro you picked cannot start until this pass lets the bot go: every card drawn after the Run macro step runs first, and only then does the other macro begin. If you mean "do all this, then run that", put the Run macro step last.

The macro it starts is the one you picked, not a copy of it. It runs whether or not its own trigger has fired, exactly as Run now on the Macros page does, and it keeps its own accounts and its own stop conditions rather than borrowing this macro's. A macro that is paused, or past your plan's macro limit, does not run when it is queued either; the step's panel says so when you pick one.

Pointed at this macro, it repeats forever: every pass queues the next. That is a different loop from Restart macro, and the difference is who holds the bot. Restart macro goes round inside one pass and keeps the account the whole time, so nothing else on it gets a turn. Run macro lets the pass finish, hands the bot back, and starts again from the queue, so anti-AFK and your other macros run in between. Use Restart macro for a tight loop, and this for a long one.

If the macro you picked is deleted, the step says so and the macro will not save until you pick another. A shared copy cannot carry the call either, because the macro it names is on the sender's profile: a copy made from a share link arrives with the step blank and switched off, until whoever added it picks one of their own macros. A step pointed at this macro survives sharing, since "this macro" then means the copy.

Repeat, If, Restart macro and Go to step

The Logic steps change the shape of the flow instead of doing something in the game, and every one of them needs Tier 3, the plan that includes advanced macros. On a lower plan they stay in the step picker tagged "Tier 3", and picking one takes you to your plan rather than adding it.

Repeat and If each arrive as a pair of cards, the step itself and the End repeat or End if that closes it, with the steps it covers between them. Fill that middle with the plus button on the line running between the pair; an If has one such line per branch. Deleting either card of a pair deletes both, and the steps that were inside are kept. Pairs can sit inside each other up to three levels deep.

Repeat runs the steps inside it more than once, and the first thing to pick is what ends it:

  • A set number of times, the count you type
  • Forever, for as long as the account stays connected
  • While a check passes, tested before each pass, so the steps inside may not run at all
  • Until a check passes, also tested before each pass, so the steps inside don't run at all when the check already passes

The two checked modes can also take a ceiling ("Stop after at most"), which is off by default; with one set, the loop ends on whichever comes first, the check or the ceiling. "Delay between loops" is the pause at the end of every pass before it goes round again, one second by default, so a loop can be paced without a Wait step inside it. A loop with nothing to stop it on its own, meaning Forever or a checked loop with no ceiling, runs each step inside it at most once a second however short the waits are; set longer waits for a slower loop. Nothing after a Forever loop ever runs, so put the rest of the macro before it.

A loop like that also keeps the account to itself: its card carries a Holds the account chip, because the account's other macros, its spam messages and anti-AFK all wait until it stops (One macro at a time). Restart macro and a Go to step that jumps back carry the same chip. To repeat steps and still let everything else take turns, put them in a Timer macro instead, which hands the account back between runs.

If sends the flow one of two ways. Set the check and the card gets two ways out: Yes when it passes, No when it does not. Both rejoin at the End if, so only one of them ever runs. A check the bot cannot answer, or one you have not finished filling in, counts as No.

The same check list serves both, and every one of them can be picked:

  • What the bot is carrying: Has an item (optionally some number of them), Item is gone, Inventory full, Slot holds item, Slot is empty, Tool is worn, Potion effect
  • What is on screen: Window is open, Sign is open, Dialog is open, each optionally matching its title, type or text the way the event does
  • Who else is about: Entity in view (optionally some number of them), Entity is gone, Player is online
  • The bot's own state: Health is low, Near a spot, Bot is still, Block in range, In a world, Time of day
  • What the macro remembered: A variable, which compares a value an earlier step stored (Checking a variable)

A check reads a state, which is what separates it from the event of a similar name: Item appears starts a macro at the moment one arrives, while Has an item asks whether one is there right now.

A check that is an event asked as a state (Has an item, Window is open, Player is online and the like) takes that event's settings. Has an item adds At least, counted in items rather than stacks, so two full stacks of 64 make 128. The rest have their own: Entity in view and Entity is gone take names (a mob type or a username) and Within (blocks), up to 64, and Entity in view also takes At least, how many of them have to be in range at once ("at least 3 zombies within 10 blocks"), so fewer than that counts as No. Left blank, either At least means one. Health is low passes below the number under Below, in health points where 20 is a full bar, 10 to begin with; Near a spot takes the X, Y and Z of a block and how close counts; In a world matches either the dimension (overworld, the_nether) or the server's own name for the world, so a lobby and a survival world can be told apart. The whole name has to match, unless you put a * where any text can go: on a server that gives each player a world of their own, skyblock_world_* matches every world whose name starts with skyblock_world_, whoever's island it is.

Four of the checks are the state behind a trigger that fires once on a change, and each takes that trigger's settings with the same defaults. Bot is still passes once the bot has held still for at least the time you set, 750 ms if you leave it blank; any movement starts the count again, and so does a change of world. Time of day passes while the game clock is on the side you pick, night if you leave it alone, with night running from 13000 to 23000; a bot whose server has not told it the time yet counts as No. Tool is worn passes while the item in the slot you pick (the main hand unless you change it) has that many uses left or fewer, 10 by default; an empty slot, an item that does not wear out and an unbreakable one all count as No. Potion effect asks whether the bot has the effect you pick (at the level you pick or higher), doesn't have it, or is low on it, with that many seconds left or fewer, 30 by default. Having none of it counts as low, so "If Fire Resistance is low, drink a potion" also drinks when the bot has none.

There is no "It is NOT true" switch. Swap the two branches instead, which says the same thing and reads the way the card is drawn. A macro saved with the old inverted setting still runs the way it always did, and its check shows a warning with a button to clear the inversion for good.

Restart macro sends the flow back to the first step and runs the macro again, for as long as the account stays connected. It is one card on its own rather than a pair, and nothing drawn after it ever runs, so it belongs at the end of a flow or at the end of a branch.

It overlaps with a Forever loop without being the same step. A Forever loop has to enclose everything it repeats, so repeating the whole macro means drawing a region around every card, where this says it in one. The difference that matters more is that it can be reached from inside a branch, which a loop cannot: "if the chest came back empty, start over" is a jump out of the region it sits in, and a pair of cards cannot express one. The wait on the card is the pause before it goes round, one second by default, and because nothing stops it on its own each step runs at most once a second however short the waits are.

Go to step is the same jump with the destination up to you. Pick any step in the flow and the macro carries on from there, whether that is back to an earlier one ("if the chest is empty, go back to the walk") or forwards past steps that no longer apply ("if the shop is closed, skip to the logout"). Like Restart macro it is one card on its own, and nothing drawn after it ever runs.

Two things are worth knowing before you build around it. It leaves any Repeat or If it is drawn inside: the flow picks up at the step you chose with no loop running, so it moves you around the macro rather than skipping one turn of a loop. Aim it at the Repeat card itself and that loop runs again from the top, count and all. And a jump backwards is a loop with nothing to stop it, so each step runs at most once a second however short the waits are, exactly as in a Forever loop.

If the step you aimed at is deleted, or dragged off the flow, the jump says so on its card and the macro will not save until you point it somewhere else. That is deliberate: a jump aimed at nothing does not fail, it quietly stops being a jump, and the flow runs on past it.

One at a time

A macro runs on every account it targets, and each account goes through it on its own, so fifteen bots reach the same chest, the same door or the same /kit in the same moment. One at a time is a region, like a Repeat: the steps between it and its End one at a time are the ones only one account may run at once. It needs Tier 3.

Draw it around the contended part only. A macro that walks to the base, checks the world and sorts its inventory can do all of that side by side, and only the chest needs taking in turns. A whole macro in one region would be fifteen accounts queueing for steps that were never in each other's way.

When another account is inside decides what an account does when it gets there while another has the turn:

  • Wait for its turn, the default: it queues, and the accounts go through the region one after another. Switch on Give up after to cap the wait: an account that has waited that long skips the region and carries on. Off, it waits however long the queue takes.
  • Skip these steps: it skips straight past the End one at a time and carries on. Nothing waits, so nothing runs late, but on any given firing only some of the accounts run the steps.
  • Only the first account runs them: the first account to get there runs the steps, and every other account skips them for that firing, so nothing in the region happens twice. A post that should go out once per run, rather than once per account, goes here.

A bot waiting for its turn is idle, and every other macro on that account waits behind it too. The panel works out how long the queue takes with the accounts you have ticked ("the last one starts after the other 14 have finished"), and warns when that is longer than the macro's own Timer interval, since the last account would then still be queueing when the next run is due. On the Macros page, the row carries a One at a time badge and says how many accounts are waiting their turn.

Reaching End one at a time is what hands the turn on, so nothing should leave the region without passing it. A Disconnect, Reconnect, Panic logout or Restart macro inside it, or a Go to step that jumps out of it, leaves the other accounts waiting until they time out, and the builder warns about it. A Go to step that lands inside the region skips taking the turn, so aim it at the One at a time card instead. Two shapes are refused outright: a One at a time inside another, and a loop with nothing to stop it inside one, since no other account would ever get its turn. With the macro on a single account, the builder points out that the region has nobody to take turns with.

For each

For each runs the steps inside it once for every player, block, entity, item or value it finds, and puts the one it is on in a variable the steps inside can use. Like Repeat it arrives as a pair, the step itself and an End for each, with the steps it covers between them, and it needs Tier 3.

Pick what to go through, then what to call the variable:

  • Player online: every name in the tab list, leaving this account out, and your other accounts too unless you untick Skip my own accounts. /msg {player} hi messages each of them.
  • Block nearby: every block of the type you pick within the distance you set (16 blocks unless you change it, 32 at most), nearest first.
  • Entity nearby: every player, mob or named entity matching the same filter Look at entity uses, nearest first.
  • Item in the open GUI or inventory: every item matching a name, a lore line or an item id, or every item at all with the box left blank, from an open container, the bot's own inventory, or both. The same "Only items where" rows a Set variable step has can narrow them, and a line you name can be read as a number onto each one.
  • Value in a list I type: each line, in order. Anything that reads as a number, like 20M or 6h, also compares as one.

Each value goes in the variable the loop names, {player}, {spot}, {target}, {stack} or {value} to begin with, so the steps inside can use it:

  • Look at variable turns the bot to the block or entity the loop is on. Put a Left click once after it to mine the block or hit the mob, or a Right click once to use it. "For each spawner within 16: Look at variable, Left click once" breaks every spawner in reach. Add Look at variable inside a For each and it comes already pointed at that loop's variable.
  • A Use GUI step set to An item I found earlier clicks each item in turn, after checking it is still in its slot.
  • In a chat message, a webhook or a check, the variable is the player's name, the block's coordinates, the item's name and so on. Values from a For each lists what each kind holds, and why not to call one {item} or {block}.

The list is read once, when the loop starts, and the loop goes through that list even as things change: a player who logs off partway through is still visited, and a block you have just broken is not looked for again. With nothing to go through, the steps inside do not run at all. A For each goes through at most 100 values, and Stop after at most cuts that down further ("the five nearest spawners"). The bot does not walk to anything, so it only reaches blocks and mobs within arm's length of where it stands; an entity that has gone by the time its turn comes is skipped.

Variables

A macro can remember a value and use it later. Set variable reads a price off a shop screen, an item's lore, how full a shulker box is, a number out of a chat reply or a value you type, {name} writes it into a chat message, a sign or a webhook, and an If compares it. A variable can also be kept from one run to the next, or added up across your accounts. Macro variables covers all of it; like the other Logic steps, it needs Tier 3.

Running macros

Everything after you save a macro: the list it lands in, running it by hand, what stands it down and how it starts again, how it shares an account with your other macros, spam messages and anti-AFK, and where to look when it doesn't do what you built it to do.

The macros page

  1. Visit minecraftafk.com/dashboard/servers/ and open the server profile.
  2. Open its Macros page.

Your macros lists every macro on the profile, one row each. Under it is the Macro library, with ready-made macros to add: see Macro library and sharing.

A row shows the macro's picture and name, and under the name what fires it ("Join", "Every 5 min"), followed by the author's name on a community macro. A One at a time badge beside the name means part of the macro runs on one account at a time (see One at a time). Then come its Status and, only while some macro on the profile is stood down, a Stop condition column. On a narrow screen both sit under the name instead.

Click a row to open the macro. Your own macros open in the builder, and one added from the library opens its settings. Click a column header to sort by it; a third click puts the list back in its own order, which is the order Move up and Move down change and the one your plan's macro limit counts down. Once there are two or more macros, Filter... narrows the list by name and by the line under it.

At the end of each row are the paper plane, which is Run now, the ⋮ menu, and the switch. The switch pauses a macro without deleting anything, and a paused row is dimmed.

In the ⋮ menuWhat it does
EditOpens the builder. A library macro has Configure here instead, which opens its settings.
LogsOpens the macro's log: see Logs and problems.
Move up, Move downMoves it one place. Offered while the list is in its own order and nothing is filtered out.
DuplicateAdds a second copy to this profile, with the same accounts, stop conditions and settings. A duplicate of a library macro stays linked, like the first.
Make an editable copyLibrary macros only: a copy of your own to edit. See Add a library macro.
ShareGives you a link to send. See Share a macro by link.
Publish to communityYour own macros only. See Publish a macro.
DeleteDeletes the macro, after asking.

On a phone the paper plane folds into the menu, as Run now.

The Status column says what the macro is doing right now:

  • Running on 2, with the heads of the accounts mid-run. Hover it for what set the run off, such as "Triggered by Steve, 6.2 blocks away".
  • 3 accounts are waiting their turn: the macro has fired, and those accounts are queued at a One at a time region. Beside Running on, the same queue reads "and 3 waiting".
  • Next run in 4m 32s, on a Timer macro between runs, with the head of the account that runs it next. Hover it for every account in the order they come round.
  • Tier 2 or Tier 3, with a lock: past your plan's macro limit, naming the plan that runs it. Hover it for why, such as a trigger the macro uses. See How many macros you can have.
  • Unfinished: it is missing something the builder would not save it without, such as the Discord webhook URL a shared copy arrives without, or a macro its Run macro step starts that has since been deleted. The switch won't turn it on until you open it and fill the gap.
  • Update available: the author of a community macro has published a new version for you to review. See Community macros.
  • A warning badge when the macro has run into problems: see Logs and problems.

Pausing a macro ends any run it has going, and switching it back on starts it fresh. Saving a change to its steps also stops a run in progress, and the macro starts the new steps on its next trigger. A rename, or a save that changes nothing, leaves a running macro alone.

How many macros you can have

Your plan sets how many macros each server profile holds:

PlanMacros per server profile
Tier 13
Tier 210
Tier 3No limit

The count is per profile, so on Tier 2 each of your two profiles holds ten. Macros added from the library count like any other. What does each plan include? has the whole plan table.

At the limit, Create macro and every Add in the library are greyed out, and hovering one says "Your plan includes 3 macros per server profile. Upgrade to add more." Duplicate and Make an editable copy answer with the same sentence instead of copying.

A profile can hold more macros than its plan covers, which usually happens after a downgrade. Nothing is deleted. The macros at the top of the list keep running, as many as the plan covers, and the rest are locked: still listed and still editable, but they don't run, and they can't be run by hand. Their status names the plan that would run them, Tier 2 or Tier 3. To bring one back, upgrade, or use Move up to lift it above the line, which pushes the last running macro below it. After a downgrade covers what else your plan locks.

Run now

The paper plane on a row, Run macro now, runs the macro straight away, whatever its trigger. A Join macro runs without anyone rejoining, and a Called macro, which never starts by itself, runs when you press it. It is a real run, step by step with every wait in it, on each account the macro targets that is online.

The toast says how many accounts it went to, such as "Macro sent: 2 account(s), 1 offline". With none of the macro's accounts online it says Nothing to run and sends nothing. A locked macro can't be run, and running a paused one switches it back on, so from then on it runs on its trigger as well.

An account does one thing at a time, so Run now is refused on an account that is busy. A few seconds after the press, Macro did not run says what was in the way:

  • Another macro: open the account's POV and press Take over to end that run, then press Run again.
  • A spam message or anti-AFK: they finish in a moment, so press Run again.

At the same time the row's problems are refreshed, which makes Run now the quickest way to see whether a fix worked.

Stop conditions

A stop condition stands a macro down when something happens: a player walks up, the bot is hit, a staff member speaks in chat. It needs Tier 3, and a macro can have up to eight.

  1. Visit minecraftafk.com/dashboard/servers/, open the server profile's Macros page, and click the macro to open it in the builder.
  2. Click Add stop condition on the dashed frame drawn round the flow. The new condition opens in the side panel.
  3. Under Stops when, pick what to watch for, and fill in its settings.
  4. Choose what happens after the stop (below), and save the macro.

Each condition is a chip along the top of the frame: click one to change it, or remove it with the bin in its panel. At eight, the add chip reads Stop condition limit reached (8).

Stops when offers every event the bot watches for itself (Chat message, Damaged, Player appears, Inventory full, Tool durability and the rest of the events), plus World change and Death. Join, Disconnect, Timer, Schedule and Called are not offered: none of them is something that can happen to a macro partway through. World change includes a server switch behind a proxy, such as lobby to survival, and Death doesn't count damage the bot survives.

A condition takes the same settings as its event, without a cooldown and without Smart trigger, so a safety stop never goes quiet. Conditions that describe a state, like Player appears or Inventory full, keep their Also fire if box, ticked to begin with: the condition then stands the macro down as soon as it starts watching if the thing is already true, which is when the bot joins and when you switch the macro on. Untick it to wait for a change.

Conditions are watched for as long as the macro is switched on and the bot is online, between runs as well as during them. So a Join macro that set a held click going an hour ago still lets go of it when a player walks up.

Each condition has two boxes of its own:

  • End with panic logout action: the bot looks around where it stands, then leaves the server, and auto reconnect doesn't bring it back. Off, the bot stays on the server. The macro stops on that account either way.
  • Allow macro to start again: off, the macro stays stopped on that account until you start it again. On, it starts again by itself after a wait, anywhere from 1 minute to 24 hours, 10 minutes to begin with. See Starting again after a stop.

They belong to the condition rather than the macro because the answers differ: "a staff member speaks" wants the bot gone, while "the inventory is full" wants it to stay where it is. The label on the bottom edge of the frame sums them up: Stands the macro down, Stands down, then logs out, or Stands down, logging out on some.

A stop is per account. A player walking up to one bot stands that bot down and leaves the macro running on all the others. On the stopped account, the step already sent finishes and nothing after it runs, and a button or key held with Release when the macro stops ticked lets go.

You can add stop conditions on any plan, but below Tier 3 the chips carry a lock and the builder won't save the macro: it says "Stop conditions need Tier 3. Upgrade to save this macro."

A Panic logout step in the flow stands the macro down too, like a condition that always logs out and never starts again by itself. The macros list calls it Panic logout step.

Starting again after a stop

While a macro is stood down, the list has a Stop condition column. It names the condition (or "Panic logout step", or how many conditions fired), in red when a bot was logged off and in amber when it stayed on. Click it for the details: each account it stopped, when, who or what set it off and how far away, whether it Left the server or Stayed on the server, and when it starts again. "An unnamed player (likely an NPC)" there means one of the server's own characters set it off, not a person.

The button beside it starts the macro again:

  • Start again, or Start all 3 again, when the bots stayed on the server.
  • Reconnect, or Reconnect all 3, when a panic logout took any of them off. It brings those accounts back onto the server and starts the macro again in one go.

The macro starts clean on its next trigger rather than picking the stopped run back up, so a Join macro whose bot stayed online waits for the next join. Use Run now to run it straight away.

Switching the macro off and on, editing it, or reconnecting the account yourself leaves it stopped: these buttons are the way back. On the Connect page, an account a panic logout took off reads Stopped by macro where its status would be, and clicking that does what Reconnect does (see Statuses).

With Allow macro to start again ticked, the details count down instead: "Starts again on its own in 9m 58s", or "Reconnects on its own in" when the panic logout took the bot off. A little after the countdown ends, the macro arms itself again, and an account its panic logout took off is brought back onto the server. A condition whose Also fire if box is ticked checks again as it starts watching, so a player still standing there stands the macro straight back down. The wait is fixed at the moment the condition fires, so changing it afterwards only affects the next stop. A Panic logout step never starts again by itself.

One macro at a time

An account does one thing at a time, the way a player at one keyboard does: a run of one macro, one spam message, or one anti-AFK action. Spam messages and anti-AFK take turns with your macros exactly as macros take turns with each other. A macro that comes due while the account is busy waits its turn and runs late, and its log says Waited its turn. If the account stays busy for longer than the macro's whole schedule, the run is skipped instead, logged as Skipped a turn.

A macro has the account from its first step to the last step that acts on the bot. A Wait in the middle holds it like any other step, but Waits, Discord posts, notifications, and Disconnect or Reconnect steps at the very end hold nothing. A macro that ends "Wait 1 hour, Disconnect" frees the account as soon as the step before them is done.

A loop with no end of its own keeps the account for as long as it runs, and nothing else on that account gets a turn meanwhile, anti-AFK included. The builder marks these with a Holds the account chip, and says so beside the save button:

  • a Repeat set to Forever
  • a While or Until repeat with no Stop after at most
  • a Restart macro step
  • a Go to step aimed back at an earlier step

Each has a way out that hands the account back. To repeat steps and still let everything else take turns, put them in a Timer macro: it runs them again and again, and gives the account back between runs. Give a While or Until loop a Stop after at most. In place of Restart macro, a Run macro step aimed at the macro itself repeats it too, and hands the account back between laps. If the macro already is a Timer macro, its timer is already the repeat, so the loop can come out.

When a macro like that is keeping something waiting right now, an alert above the list names it and the accounts, such as Held by "Mine forever" on Steve since 14:02, says what is waiting, and has a button that opens the macro.

Two clashes can be seen coming before anything runs, and a row's problems badge lists them under May run late:

  • A Timer macro whose interval is short next to another macro's longest run on the same accounts. It still runs, but late, every time. Give it a longer interval, or move the steps into one macro.
  • A macro that waits longer between two of its steps than your anti-AFK delay. Anti-AFK can't run while the macro has the account, so the bot can be kicked for idling during that wait.

A One at a time region is a different thing: it makes the accounts running one macro take turns with each other over part of it.

While it runs

The trigger's panel in the builder has two boxes under While it runs that change how the macro shares the bot. Both are unticked to begin with, and both are on every plan.

Keep screens open. A macro that comes due normally goes ahead, and closes whatever is open on the bot, a chest, a menu or a sign, as it works. With this on, it waits for the screen to close instead, and leaves the account free for other macros while it waits. Screens the macro opens itself are closed as usual. Use it on an account you work in by hand from its POV, so a Timer macro doesn't shut a chest under you. The log notes Waited for a screen, and after an hour of waiting the macro skips that run (Screen stayed open) and tries again at its next time.

Override other macros. A macro that comes due while another one has the bot stops that one and runs straight away, instead of waiting its turn. The macro it stopped lets go of its held buttons, as on any stop, and runs again the next time it is due: a Timer macro one interval later, any other the next time its event fires, so a Join macro's endless loop stays stopped until the next join. Two macros with the box ticked still take turns, and a macro never stops the one whose Run macro step started it. The stopped macro's log notes Overridden. It suits a short job that must not wait, like a sell run when the inventory fills, on an account that spends its time in a long loop.

Logs and problems

A macro that has run into trouble gets a badge in its Status: Failing now while a problem is happening, the number of problems (1 problem, 2 problems) otherwise, or Check setup when it only has warnings worked out from its own shape. Click it:

  • Each problem says what went wrong and on which step, which accounts it happened on, and when: Happening now, or "Last seen 3 hours ago" and how many times in all. When the macro had to wait, a line under it names what held it up: another macro, a spam message or anti-AFK.
  • The list is headed Why this macro isn't working while something is happening now, and Recent problems once nothing is. It covers the last day, and the badge turns grey once every problem in it is more than 15 minutes old.
  • Clear hides a problem until it happens again, and Clear all hides the lot. Neither fixes anything, so a problem that comes back shows again.
  • Steps that won't run lists steps placed after one that ends the run (Panic logout, Disconnect, Reconnect, Restart macro, or a Go to step that jumps back), and May run late the clashes from One macro at a time. Both are worked out from the macro itself rather than reported by the bot.

Open the macro in the builder, and each reported problem also sits on the step it happened on.

Logs, in the row's ⋮ menu, opens the macro's log (Macro logs of and its name), which keeps the history the badge lets go of:

  • Player appearances: the players who set off its Player appears trigger or stop condition, with the account and the time, newest first.
  • Errors and warnings: everything the macro has reported, each with its account, whether it is Happening now, Unresolved or Fixed, what happened, and when it started and stopped.

It reads your first 10 accounts, with the ones that have a problem right now first. Copy and Download give you the whole log as text, which is what to send support when a macro won't behave.

Still stuck?

If an account won't connect, Fix connection problems covers every status and warning. Otherwise ask in our Discord, where the team and other players answer, or email support and we will get back to you.