These numbers are not build-specific—they are hardcoded into the macro creation package:

The creation panel is opened by pressing the shortcut ALT+R Or through the settings - "Macro." The available number is shown in the upper right corner of the window.

The "Add" button creates a new macro. The acronym is the same four characters that appear directly on the icon:

You can select an icon from a color set using the magnifying glass button:

Editing and deleting are two buttons in the lower right corner:

The commands in the macro are divided into two unequal groups, and this explains most of the discrepancies between projects.

Customer — the game client itself parses them. It turns the command into a standard action: press a skill, take a target, wait. The server knows nothing about the command itself; it only receives the result. Such commands work the same everywhere because they depend only on the client.

Серверные — the client sends them by number, and the server makes the decision. That's where they differ: some can be disabled, others behave differently.

A good example is - /delayThis is a purely client-side pause; there's no such command on the server. Therefore, the delay isn't guaranteed: if the skill hasn't had time to recharge, the macro will simply continue.

The main set that makes up the body of the macro:

/evaluate - Is issuing a recommendation to the selected target, not a reset of recommendations. It works from level 10, but only for another player (you can't do the same thing twice), and the number of recommendations per period is limited.

The three lists of wars are different. They are constantly confused, although in the game these are three independent lists:

/ nick - he can change his title only nobles, and only by indicating your own name. Everyone else gets the title from the clan leader, and it only works within the clan. Level 3 or higher.

They are processed by the server, and all of them can be easily placed into a macro:

A separate layer is for commands that begin with a dot: .online, .ping, .whoami, .cfg, .relog, .offline, .deposit and the like. Technically, these aren't commands, but rather a regular chat message—the server intercepts it and performs the action.

Two things follow from this. Firstly, such commands work from a macro a simple text string. Secondly, their set depends entirely on the project: they are server add-ons, not part of the game, and the list varies from project to project, sometimes even being completely absent.

A line starting with a channel sign is sent to the chat. This is the simplest type of macro—for example, a one-click sales announcement:

Our team /useshortcut takes two numbers: the panel page and the cell number. Pages twenty (zero through nineteen), each with twelve slots. Each slot can hold an item, skill, action, recipe, teleportation bookmark—and even the macro itself.

Now about the trap that most often causes macros to break. Macros are stored on the character as a whole, and the panel is separate for each profession. The main class and each subclass have their own cell layout, but the list of macros is the same for all.

Hence the consequence: a macro compiled on the main class through /useshortcut, after changing to the subclass will click completely different buttons — those that reside in the same cells of the subclass. The macro appears intact, produces no errors, and simply does something wrong. If the macro needs to work for multiple professions, the cell layout will have to be repeated manually for each.

Any action you take interrupts execution. Stepping aside, turning on the charger, opening a window, or sending a chat message—the macro stops at the current line. This isn't a bug, but by design: the macro shouldn't work without player input.

A macro cannot be nested within a macro. A line with a reference to another macro simply will not be executed.

Dragging things between cells breaks the finished macro. It remembers the cell number, not what's in it. Two things were swapped, and the macro started doing something else.

Commas and semicolons disappear. The server strips them from each line, so the ad text will have to be written without them.

The most popular macro is to hit the same thing as your partner:

For the spoiler, the skill itself and the pause before collection are added:

Change the kit with one button. First, all the parts are placed on the panel, each in its own cell:

Then each part is dragged from the panel into a separate line of the macro:

The finished macro is placed on the panel like a regular skill and works with one click:

Weapon buffs. The principle is the same: a weapon with the required properties is placed on the panel.

The weapon is moved to the macro line, then equipped, and the buff itself is moved from the list of active skills to the next line. Each weapon must be followed by its skill: