Start with one stage and one purpose
Open ASBuilder, choose the class you want to plan and give the build a recognisable name. Begin in Early Game, choose a short spell priority and keep a copy of the build code before making larger changes. The planner is a separate tool: opening it does not replace the build currently equipped in Azeroth Survivors.
The useful first question is what your next attempt needs. Is the opening wave difficult, does a boss survive too long, or does the plan rely on gear you have not collected? Put that objective in your stage notes. A finished late-game loadout is less helpful if it hides how to reach the first workable stage.
Early, Mid, End and Endless are different checkpoints
The inspected web planner separates a build into four stages. Use Early Game for an opening you can realistically assemble. In Mid Game, note the replacements or upgrades that make the plan coherent. Reserve End Game and Endless for later targets rather than treating every slot as an immediate requirement.
Spell slots are ordered by priority. Arrange the spells so the first choice reflects what you actually want to take next, then inspect the alternatives for jewellery. Banish choices are deliberate exclusions, not spare priority slots. Record why a spell is excluded: an old version of a build can otherwise leave an unexplained choice that you keep copying.
Use the talent view to plan a reachable next step
The web tool has separate Loadout, Talents, Armory and Notes & stats views. Its help describes left-clicking a talent to add a rank and right-clicking to remove one, with a Leveling path option to record an order. A planned talent is not a talent point earned in the game. Compare the current game’s available points, prerequisites and version before following the plan.
On a phone, confirm that the planner exposes the control you need; a desktop right-click instruction is not a complete touch workflow. Keep a short text note of the next milestone if you cannot edit comfortably on that device. The game’s live tooltip takes priority over an older exported code or screenshot.
Copy a build code before sharing or replacing a plan
The current web UI separates Copy code, Import code, Copy whole profile and Share publicly. A single-build code is the focused way to keep or exchange one plan; a whole-profile copy has a broader scope. Keep the source code unchanged before importing an unfamiliar example and check the selected class and stage after the import.
Public sharing makes a different decision from keeping a local draft. Use a neutral build name and leave personal notes out of anything you choose to publish. You can learn the planner without publishing a build. This guide does not upload your code or inspect your saved game.
The web planner and the addon have different jobs
The Cadoky ASBuilder repository describes a planner and in-run tracker addon for the WoW 1.12.1 / benilla client. The website links to that repository’s releases. A browser draft is not proof that the addon is installed or that the original browser game will automatically synchronise it.
If you choose the addon route, follow the current author instructions for the exact client you use. Do not assume a generic browser-extension installer or a normal World of Warcraft addon folder is the right destination. The repository documents a build-code import flow; verify the result in that client rather than interpreting a successful clipboard copy as an applied build.
Make one comparison you can learn from
Keep map, difficulty and equipment similar while trying one meaningful change. Write down the version and the stage at which the plan stopped working. Several changes made together can produce a better run without telling you which choice helped.
Use the Shaman milestone guide for a checked class example, or the class finder when the class itself is undecided. Export a game backup through the original save menu before moving environments: an ASBuilder code describes a plan, not a restorable character save.
Primary sources: ASBuilder live interface and How it works · Cadoky’s addon README
