Macro library and sharing

You don't have to build every macro yourself. The Macro library, under your own macros on every profile's Macros page, holds ready-made ones in a single list: ours, marked Official, and the ones other players have published. Each card shows what the macro does in a line, who made it, how many profiles have it, the share of its votes that are thumbs up, and the servers it was built for. Click a name to open the macro's own page.

Type in Filter... to search the names, the one-line descriptions and the authors, and pick an order with the sort button beside it: Official first, the default, which also puts community macros built for this profile's server ahead of the rest, Most added, Best rated, Newest or Just updated. The list shows 24 macros a page.

A macro's own page shows its version, how many profiles have it, its trigger and the servers it was built for (or Works on any server), with thumbs up and down and a Share button. Its Overview tab says what it does and what to arrange first, Changelog lists its versions, and Forum holds questions and answers about it.

Add a library macro

1. Visit minecraftafk.com/dashboard/servers/, open the server profile, and open its Macros page.
2. Find the macro in the Macro library and click Add, or Add macro on its page.
3. Under Settings, tick the accounts it Runs on, and fill in the settings its author left open, such as the sell command or the players to ignore.
4. Click Next. Review shows What it does, step by step with your values in, and Before it runs, the things you have to arrange yourself.
5. Click Add macro.

It lands at the bottom of your list, switched on and named after the macro, and its library card reads Added.

A library macro stays linked to where it came from. Its row's menu says Configure instead of Edit, and clicking the row opens the same settings rather than the builder: the steps are its author's, which is what lets them be updated for you. To change the steps themselves, pick Make an editable copy in the row's menu. You get a copy of your own, switched off and open in the builder, while the original keeps running until you switch it off. The copy is yours from then on and never receives an update. Duplicate is the other way round: a second linked copy, configured and updated like the first.

Library macros count towards your plan's macro limit like any other.

Official macros

We write and test these ourselves:

Sell axe and Sell menu also stand down and log out when the account is hit, or when a player you haven't listed comes into view; each of those is a setting you can switch off. Sell axe, Sell menu and Spawner protect are built for DonutSMP and HugoSMP, and the seven spawner farms for HugoSMP, since they list on its /order market. On Tier 3, a DonutSMP or HugoSMP profile made with its ready-made setup already has them, switched off. Read Before it runs when you add one: a spawner farm needs the account parked in front of its spawner, and Spawner protect really does break your spawners.

Every official macro uses something from Tier 3: an event trigger, a loop, a held button or stop conditions. On Tier 1 and Tier 2, each card carries a Tier 3 badge naming what it needs, and the macro can't be added.

When we improve one, the copies follow by themselves. The next time you open the Macros page, a linked copy is brought up to the new version with its settings, accounts, name, switch and place in the list kept, and a message such as "Sell axe was updated" says what changed. There is nothing to accept. Each version's notes are on the macro's Changelog tab. An editable copy is never updated.

Community macros

Community macros are made by other players, and any plan can add them, as long as the plan includes what the macro uses: the add dialog says when it doesn't. Nobody at MinecraftAFK checks one before it is published, so the review step says so: "This macro was made by a community member, not by MinecraftAFK. Check the steps below carefully before you add it." Read What it does before you click Add macro, because those steps run on your accounts.

Its author can publish new versions, and none of them reaches your copy until you have looked at it. When one is out, the row shows Update available in its Status. Click it to see Your version beside After the update, with the changed steps marked, and a line for anything the steps alone don't show, such as a new trigger or new stop conditions. Update takes it and keeps your settings; Not now leaves your copy as it is. The author's notes for each version are on the Changelog tab.

On a macro's page you can give it a thumbs up or down (one vote, which you can change), and its Forum tab is where to start a thread, reply, and mark a useful post Helpful. The author's posts carry an Author badge. If you have no username yet, your first post asks for one. Our macros have a forum too.

For a macro that is harmful or breaks the rules, open the ⋮ button on its page and pick Report macro. Choose a reason (Harmful or malicious, Doesn't do what it says, Spam or advertising, Offensive content, Copied from someone else, or Something else), add any details, and click Send report. The team reviews every report. A macro that simply doesn't work is better answered with a vote, or a question in its forum.

If its author deletes it, the macro leaves the library, along with its page and its forum. Copies already added keep working, but get no more new versions.

Publish a macro

Any macro of your own can be published, on every plan. One added from the library can't, since its steps are somebody else's.

1. Visit minecraftafk.com/dashboard/servers/, open the server profile's Macros page, and pick Publish to community in the macro's ⋮ menu.
2. Under Details, fill in what its card will say:
   • Your username, asked only the first time: the name on everything you publish and post. Don't use one of your bots' names, since a public link between you and a bot can get it banned.
   • Name, at least 3 characters, with the item that pictures it beside it.
   • What it does, in one line, at least 10 characters: the words someone would search for.
   • More about it, if there is more to say.
   • Built for: pick a server, or type any address. Left empty, it shows as working on any server.
   • Before it runs: what has to be true that no setting can arrange, one per line.
3. Under What it does, check the steps as they will be published, and what was left out of them.
4. Under Settings, tick the values people adding it may change, such as a command, an item or an ignore list, and name each one the way it should read when they add it.
5. Click Publish.

It is live straight away, and you land on its page. Publishing doesn't change the macro on your profile. To change your username later, see Username.

A published macro goes to everyone, so it carries less than your own copy does:

• Passwords in chat steps are removed: /login hunter2 goes out as /login.
• Discord webhook URLs are left out. Each channel your posts go to becomes a setting that stays ticked, and everyone who adds the macro pastes their own URL. Left empty, those posts are left out of their copy, unless the macro can't run without them, in which case the URL is required.
• The members and roles your posts ping are left out, since they mean nothing in someone else's Discord. The @everyone and @here switches stay.
• Ignore lists, their names and their patterns alike, on the trigger and on every stop condition, are emptied, since they name your alts. They start ticked as settings, so whoever adds the macro can fill in their own, and their own accounts are skipped automatically.
• Steps parked off the flow are left out.

A Notify my devices step goes out as it is, and notifies whoever added the macro, on their own devices.

Not ready to publish means the macro would arrive unable to run: it has a Run macro step that starts another of your macros, which nobody else has, or a step that is unfinished. A Run macro step that starts the macro itself is fine.

On the macro's page, the Manage menu is yours alone:

• Edit details changes what its card and page say. What it does only changes with a new version.
• Publish new version: pick which of your macros on this profile it comes from, say What changed, then check the same two steps as before. Everyone who added it reviews the version before it replaces their steps, and keeps their settings. Open the page from the profile the macro is on, since a version is published from a macro there.
• Delete takes it out of the library. Everyone who added it keeps their copy, which gets no more versions.

Share a macro by link

To send one macro to one person, share it by link. It works on every plan.

1. Visit minecraftafk.com/dashboard/servers/, open the server profile's Macros page, and pick Share in the macro's ⋮ menu.
2. Read the password check. Login commands it finds, like /login or /register, are hidden to begin with: the command stays in the macro, and what you typed after it is removed. Hide passwords in the link turns that off.
3. Click Copy link and send it. On a phone the button is Share link, which opens the share sheet.

The link is a copy of the macro as it is now. Edit the macro later and the link still gives the old version, so share again for a new link. Turn off link, in the same dialog, stops the link working for everyone who has it. A link made before your last edit is a separate one, and keeps working.

A link carries the macro's trigger, steps, stop conditions, name and picture. It leaves out:

• the accounts it runs on, which are yours;
• Discord webhook URLs, though the posts' text, pictures and pings all travel;
• which macro a Run macro step starts, since that macro is in your account;
• the waypoint a Walk to step names. The step keeps its coordinates, so it walks to the same spot.

For a macro you added from the library, Share copies a link to its library page instead, and so does Share on any macro's own page. That link is the same for everyone, and on a phone it opens the share sheet.

Whoever opens a link signs in and picks Which server profile is it for?, with profiles on the server it was built for first; with one profile it opens there straight away, and with none they add one first.

The Shared macro page shows what it does, and under Before you add it what to fill in: their own password after a login command, their own Discord webhook URL, which of their macros a Run macro step should start. Add macro asks which accounts it runs on and shows the steps again, with a reminder that nobody at MinecraftAFK has checked a macro sent by link.

Once added, the macro is theirs: they can edit its steps, and nothing the sender changes reaches it. It arrives switched off if something is still missing, until they fill it in, and also if it was off when it was shared.

A whole server profile, with its settings, macros and spam messages, is shared by link the same way: see Share a profile by link.