AION 2 Macro Guide — Setup, Delay Settings and Starter Chains

Ask the AION 2 community about macros and you will find two groups talking past each other: players who think macros removed the skill ceiling, and players whose wrists gave out five years ago. Both are talking about the same official system, and understanding what it does — and specifically what it does not do — is the difference between a macro that helps and a rotation that quietly loses damage.

What macros do in AION 2

A macro is a saved sequence of skills that fires in order from one bound key while you hold it. That is the whole mechanic. The client steps through the list, respects each slot’s delay, and repeats the sequence as long as the key stays down. Release the key and the sequence stops; press a different skill and you can rejoin the chain wherever you left your muscle memory.

What it does not do is make decisions. It will not move you out of an AoE, wait for a boss’s stagger window, hold an interrupt for the right cast, or swap targets. AION 2’s endgame encounters are built around exactly those decisions, which is why the macro system coexists with genuinely demanding raid design. The macro owns the order; you still own the timing.

Where the macro menu is and how to bind the key

Macros live in the Skill window, not in the general settings. The setup is two places, and missing the second one is the most common “my macro does nothing” report:

The chain order matters more than most players expect. AION 2’s combat runs on skill chains — certain skills open branches that others finish — and the skill points guide covers how those skills unlock. A macro that fires skills out of chain order wastes the branch bonus on every loop.

Choosing a delay that fits your ping

The default delay is 10 ms per slot, and most players should leave it there. The delay is a pause the client inserts between skills so each one registers before the next attempts to fire. Too high and your rotation gets air between skills; too low for your connection and the client starts skipping skills that never confirmed.

Community testing has converged on a ping-based table. These numbers are not official — they are measured player experience, and your own class’s chain speed may justify adjusting them:

The right way to tune it is to test, not to trust a table: take a rotation to a Training Scarecrow, run it with the analysis window open, and watch for skipped skills when you lower the delay. If the total loop time stops improving, you have found your floor.

Weaving and why macros made combat “easier”

The macro system is the answer to AION 2’s weaving problem — alternating basic attacks between skills to squeeze out extra damage. Manual weaving means pressing an auto attack in every gap between skill animations; done perfectly it is a measurable DPS gain, done all night it is a repetitive strain injury. The macro effectively performs the weaving pattern for you: it steps through skills at a steady cadence, and community guides describe the result as close to optimal for most classes.

This is the change that started the forum argument. Classes with long, rigid chains — the Gladiator is the usual example — lost much of their execution difficulty when the chain itself became a held button. Classes built around timing and positioning — Sorcerer burst windows, Cleric triage — kept their difficulty because their decisions were never about button order in the first place.

Starter chain advice per class

Start every macro with the class’s most reliable damage chain, not its biggest number. The reasoning: a chain you can land 100% of the time beats a higher-damage branch that fails off cooldown. Class-specific orders belong on the class pages; the shape of a good first macro is the same everywhere:

• Gladiator / Templar — open with the melee chain starter, keep the hold/gap-closer manual; melee needs target-position control the macro cannot give.
• Assassin / Ranger — put positional or stealth-openers outside the macro; run the sustained damage chain inside it.
• Sorcerer / Spiritmaster — macro the filler loop between burst windows; keep hard-hitting cooldowns on separate keys so they are not burned into a moving boss.
• Chanter / Cleric — macro your damage filler for solo play, but keep heals off macros entirely; healing is a decision, not a sequence.

For the reasoning behind class rankings and where each kit’s difficulty actually sits, the class tier list stays more current than any single macro file.

Charged skills, PvP and the limits of the system

Three situations break macros, and every AION 2 player learns them the same way. Charged skills need a hold that a fixed-delay macro does not naturally express — community guides recommend keeping charge abilities on manual keys. PvP is the second: human opponents feint, kite and gap-close, and a fixed sequence is free damage for them. The third is any mechanic that interrupts casting; the macro does not know the boss flew, and it will keep tapping into the void until you release the key.

None of this is hidden. The system is deliberately a chain-runner, and NCSOFT keeping it official while the game demands real execution elsewhere is the balance: macros remove fatigue, not thought.

Sources and verification

• Setup path (K → Macros, chain lines per slot) — Game8’s macro setup guide, October 2026, concordant with Sportskeeda’s setup walkthrough, October 2026
• Keybind path (Settings → Key Settings → General → Gameplay → Macro) — Sportskeeda, cross-checked with AllThings.how, October 2026
• Default 10 ms delay and ping-based delay ranges — EZG and GGWTB community testing, October 2026; multiple guides independently publish the same bands
• Weaving and animation-cancel context — MMOEXP rotation guide and community macro-testing videos, October 2026
• Charged-skill caution and class-level macro importance — community-reported across r/Aion2 and class guides; no official documentation states per-class macro values

Evidence level: Official-adjacent for the menu paths and the existence of per-slot delays (verifiable in the live client by any player); community-reported for every specific delay number and all class-specific chain advice. No official source publishes recommended delay values, and chain orders patch frequently — treat any fixed order older than your current patch as a starting point, not a prescription.