Basic AntiMicroX assignments are one-to-one: press this button, send that key. Advanced slots are where the program becomes genuinely powerful — they let a single control produce timed, sequenced and conditional behaviour, and they are the building blocks from which macros are composed. The documented slot types are Pause, Release zones, Hold zones, Cycle zones, Distance zones, Delay, Press Time and Mouse Mod. Those names look intimidating as a list, but each one answers a plain question about timing or distance, and this guide explains each in ordinary language, shows how they combine into a macro, and gives a safe working method for experimenting in version 3.6.1. You do not need all of them. Most players use two or three types regularly and ignore the rest, which is the correct relationship with a toolbox. Work from a saved copy of a working profile, as the profiles guide recommends, and add the fair-play caution from our disclaimer to anything you build for online games, because automated sequences can breach game rules there.
What an advanced slot is
A slot is one element inside a button’s assignment. A basic assignment might contain a single slot holding a single key. An advanced assignment contains a sequence of slots that AntiMicroX works through as you press, hold or release the control: send this, wait, send that, keep this active until a condition, and so on. That sequence is what makes tap-versus-hold behaviour, double-tap actions, delayed follow-ups and repeating turbo-style cycles possible within one program and one profile. The turbo feature covered in our turbo mode guide is a good example of the idea in action, since turbo works by cycling quickly through cycle zones. The mental model to keep is a recipe rather than a switch: slots execute in order, timing slots control the spaces between actions, and zone slots define stretches of behaviour based on how long or how far a control is used. When an advanced assignment misbehaves, you debug it like a recipe too — read the sequence in order and find the first step that does not match what you intended, instead of changing ingredients at random.
The timing slots: Pause, Delay and Press Time
Pause inserts a waiting period into a sequence, so actions before and after it are separated by a deliberate gap. Delay is closely related timing control used to shape when parts of an assignment take effect. Press Time concerns how long a press lasts or must last, which is the difference between a tap and a press that a game registers as a distinct, longer input. These three answer the most common macro needs in practice. A sequence that opens a menu, waits for the menu to appear, and then confirms a selection fails without a pause, because the confirmation arrives before the game is ready to receive it. A press that is too short can be missed by a game that polls input slowly, which press duration thinking fixes. The working rule is to add the smallest timing that makes the sequence reliable in the actual game, then stop: oversized pauses make controls feel sluggish, and stacking timing slots speculatively makes later debugging miserable. Test timing-sensitive sequences in a safe in-game location, because the correct pause depends on that game’s responsiveness, not on a number any guide can give you in advance.
The zone slots: Release, Hold, Cycle and Distance
Release zones define behaviour tied to letting go of a control, which enables actions that happen on release rather than on press — the release half of a tap-and-hold design. Hold zones define a stretch of behaviour while a control remains held, so a button can do one thing when tapped and sustain another while held. Cycle zones divide behaviour into repeating segments, and they are the mechanism behind turbo’s rapid repetition as well as other repeating patterns. Distance zones apply to analogue controls and divide stick travel into ranges, so the first part of a push can do one thing and a fuller push another — gentle movement versus full movement from the same stick. Together, the zones turn a control from a single trigger into a small instrument with regions. The cost is complexity: every zone boundary is a place where behaviour changes, and therefore a place where play can surprise you. Introduce one zone type at a time, label what you built in your profile notes, and play-test the boundaries deliberately — tap, hold, release, partial push, full push — until each transition does exactly what your notes say it should.
- Release zones: what happens when you let go.
- Hold zones: what continues while you keep holding.
- Cycle zones: repeating segments; the basis of turbo.
- Distance zones: different behaviour at different stick travel.
Mouse Mod and building a real macro
Mouse Mod modifies mouse-related behaviour within an assignment, and it belongs with the pointer controls discussed in our controller-as-mouse guide when you are shaping how a stick-driven pointer behaves inside a combined assignment. A macro, in AntiMicroX terms, is a sequence built from the pieces above: ordinary key and mouse slots arranged with pauses, delays, press timing and zones so that one control performs a small routine. Build macros backwards from the routine you want. Write the steps in plain words first — press, wait for the game, press, hold briefly, release — then translate each written step into a slot, then test the whole sequence and compare it against your written version step by step. Keep macros as short as the task allows. Every additional slot is another timing assumption about a game that may load slowly, lag or update its interface, and long brittle macros fail in long brittle ways. If a routine needs many steps, consider whether part of it belongs on a second control instead, splitting one fragile sequence into two reliable ones you trigger in turn.
Work safely: copies, notes and fair play
Three habits keep advanced work safe. First, experiment only in a copy of a working profile, saved under a name that says it is experimental, so a failed idea never touches the layout you actually play with. Second, keep notes beside the profile: which control carries which macro, what each zone does, and what game situation it was tuned for. Advanced assignments are invisible in play — nothing on screen announces that a button contains a sequence — so your notes are the only documentation that exists. Third, respect game rules. Macros automate sequences of inputs, and in competitive or online games that can violate the publisher’s terms with real account consequences, whatever tool performs the automation. Check the specific game’s rules, prefer permitted and single-player contexts, and read our disclaimer for the general position. Within those boundaries, advanced slots are the most creative part of AntiMicroX: start with one button, one sequence and one test, and the system that looked opaque as a list of names becomes a set of tools you reach for deliberately, one at a time.
