Macro Introduction

Our macro system allows you to create advanced automations without any coding requirements, by using a drag-and-drop editor.

These macros can then be ran on a bot or a group of bots at any point in the future.

Firstly we need to open the macro editor. You can open a new macro editor by clicking on the Macros page, and then clicking "Open Macro Builder":

In the Macro Builder window, you can now drag and drop components that you want to run, and create connections between them. The macro will always start at the "Macro Entry Point" component, from which you should create a connection to your first component in your macro.

Once you are done building your macro, you can save it by clicking the Save button at the top, or by using the CTRL + S shortcut. This will create a new instance of your macro, which you can see on the macros page:

Note: you can then edit this macro instance, or create copies of it by expanding (the above seen) instance, and clicking the "Edit Macro" button.

To run a macro, you must select the bots that it will run on, which can be done in the "Run On" dropdown:

Once the bots that will run the macro are executed, you can then click the "Resume" button:

Note: you can then stop, the macro by clicking the "Pause" button, which will appear instead of the "Resume" button while the macro is active.

Note: macros that are enabled will automatically start on selected bots, once the bot joins a server.

Once the macro is active, and the macro instance is expanded, a panel will popup that will show the macro's status for each bot:

These statuses include delays between components, the currently ran component, which component the macro stopped at, and when will the macro be restarted.

Macro variables can be defined in the Macro's Settings dropdown (top middle panel). These variables can then be quickly changes from the macro instance view (without opening the editor):

These variables can then be linked to macro component variables, by clicking the chain icon ().

In the event category, you can find macro components that are event based. This means that you do not have to connect anything to this component for it to start waiting for events. These events get registered at the same time as the Macro Entry Point, and will wait until an event occurs, and then it will call it's Output.

Macro event listening gets paused while it's Output is actively running, i.e.: Damage Received Event -> Chat -> Wait (for 5 seconds) -> Chat will pause the Damage Received Event listening for 5 seconds, until it completes, and then listening will resume.