Anime Ascendants Record and Replay Routes

A macro in Anime Ascendants is a recorded sequence of placements and upgrades that the client can play back on the same kind of stage. The live game includes this on purpose: open the macro panel, start recording, play the match as you would by hand, stop, save, load, and playback. Pair it with Auto Start and Auto Replay in settings and you have a farm route without TinyTask.

Community hubs add import/export, lobby auto-join, and webhook pings on top of the same idea. Those extras are the auto farm layer and they carry the account risk spelled out on the Scripts Hub. This page stays on the recording itself — official or otherwise — because a bad recording fails whether a GUI or the native button plays it.

If you cannot clear the node with the units you will record, stop. Macros copy your hands. They do not buff your roster. Fix the roster with the team builder, best units, and how to evolve first.

Recording a route that actually wins

1. Enter the exact map and difficulty you intend to farm. Story act, Infinite, and Challenge are different bindings. A recording labeled for one world will throw an invalid-map style rejection on another.
2. Set the camera the way you will always see it. Max zoom-out is the usual advice so clicks land on tiles, not on the skybox. Mobile players should lock landscape before hitting record.
3. Start record, then play for real. Place the farm unit first. Wait through the upgrade clicks; do not toggle a separate auto-upgrade and immediately stop the recording. The native recorder stores what you wait for.
4. Place support so its aura actually covers the carry tile. Then place the carry. Upgrade in the same order you will need on replay.
5. Finish the clear (or hit your Infinite target wave). Stop recording. Save to a named slot (story-curse-academy-act1, not slot1).
6. Load that slot on a fresh run of the same node. Hit playback. Watch the entire first replay. If a unit drops on the wrong tile, delete the take. Do not Auto Replay a crooked first save.

Sell-and-replace tests are useful: if you sell the farm and playback still puts it back on the original tile, the recording has real coordinates. If playback does nothing, you loaded the wrong slot or the wrong map.

Solo macro on an Anime Ascendants event map

Delay settings, and why they exist

Playback is a timeline, not a brain. Delay (sometimes labeled interval, wait, or click gap on third-party GUIs) is the fudge factor between “I clicked upgrade” and “the money existed.”

Symptom	Likely delay / record problem	Fix
Unit never appears	Click fired before the tile UI existed, or wrong map slot	Re-record on the bound stage; wait for match start
Farm places, upgrades skipped	You ended record before upgrade animations / cash ticked	Wait through each upgrade while recording
Carry places too early and you go broke	Timeline is faster than the income curve	Longer delay, or record extra farm upgrades first
Perfect on Story, instant leak on legend	Different HP and leak path; same clicks are not enough	Separate recording; usually a better unit or trait
Works in solo, fails in public	Tiles already taken by other players in a 16-player server	Do not play macros in random publics

If you are using only the official recorder, you do not get a giant delay slider. You get whatever timing you actually waited during the take. That is a feature. Pad the original recording with the same pauses you need on a slightly laggy night, not the fastest possible perfect ping.

Third-party playback that lets you crank speed will desync first on upgrade-heavy Infinite routes. Faster is not higher Gems per hour if every run dies on wave 12.

Story vs Infinite vs Challenge recordings

Story. One recording per act per difficulty. Act 1 does not belong on act 6. Legend nodes on the same world still need their own take. These are the best candidates for Auto Replay because the HP budget is known.

Infinite. Record the farm-first curve, not a Story dump of your whole bench on wave 1. Your Infinite take should look slow and greedy: farm, farm upgrade, buffer, carry, then a stop rule. Infinite recordings that try to be heroic until wave 999 are how people AFK into a leak and call the macro broken. Set a target wave you can actually hold. Farm and support is the team chapter for this.

Challenge. Record after you read the modifier. A cash-down modifier means extra farm upgrades in the take. A HP-up modifier may mean the Story carry is no longer legal for playback. Daily modifiers make “one Challenge macro” a fantasy. Bind per challenge type, or skip the tool and play the day by hand.

Raids and limited events follow the Challenge rule: new boss, new take. Importing a friend’s raid file without their units is how you watch a ghost place towers you do not own.

Why legend stages eat bad macros

Legend (and other high-HP follow-ups) fail recordings for boring reasons:

• DPS gate. The Story take never needed max upgrades on the carry. Legend does. Playback stops at the Story upgrade count and the boss walks.
• Tile precision. A farm that was “close enough” on normal leaks when enemies are faster or tankier. The click was always sloppy; normal mode hid it.
• One-placement traits. If your carry is on a one-place trait, you cannot panic-drop a second copy when the macro is late. The traits tier list is part of why a copied route is brittle.
• Support range. Buffers that barely touched the carry on Story miss it after a path change.
• No eyes. Legend is where you should watch the leak, not webhook it. If the first two legend attempts die at the same corner, fix the team — evolve, reroll, or swap — instead of looping the same file. How to evolve and how to reroll traits are the real patch.

A legend macro that works is almost always a fresh recording made on legend with the exact loadout you will keep using, including the farm unit’s Golden (or equivalent) trait and the carry’s actual trait. Copying a Story file and hoping is the failure mode this heading is about.

Loadouts, sharing, and the official ceiling

Name slots after the map and the team, not the date. When you reroll a trait or replace Bolma-style income, re-record. Playback cannot notice that your farm now makes less money.

Sharing recordings only works if the importer owns the same units with similar stats. A file that places a Secret you do not have will skip or drop a placeholder. Build the team in the team builder until the names match, then record your own take.

The official macro will not auto-join a different mode from the lobby. It will not skip you through a campaign you have not unlocked. It will not spend codes or reroll traits. That ceiling is healthy. The moment a tool offers those extras, you are back on the Scripts Hub risk list.

Keep recordings for maps you already understand. Use Auto Replay while you are still at the desk. When an update ships, assume every file is guilty until you watch one replay. That habit beats any imported “100% win rate” pack from a stranger’s Discord.