Notes

System & Client

• Windows x64 only (Windows 10 or later).
• Both retail (Midnight) and Classic are supported. The game’s built-in Assisted Combat recommendation is retail-only — on Classic, write your own property logic or use the Hekili addon for recommendations. With multiple clients installed, the addon goes into whichever client is the current keystroke target — play on that one.
• Detection is built in for Wow.exe (retail), WowClassic.exe (Classic) and WowB.exe (beta); no configuration is needed, and other executable names are not detected.
• After first install or updating a module, type /reload in game to load the latest content; when the status bar shows “module updated … press F12,” press F12 to reload.
• The in-game addon’s name can be customized in settings. After renaming, fully quit and restart the game client once — a /reload alone may not load everything.

Capture and Troubleshooting

The capture setting chooses which image WA1 reads:

• Window: reads the game window’s own image, so covering it with another window does not directly change the sample. A minimized or non-rendering game may provide no frames. After a resize, the client recalibrates and recovers capture.
• Screen: reads the game’s region of the desktop. Other windows covering the strip affect recognition. Try this mode where window capture is unavailable, such as some remote sessions or virtual displays.
• Auto: prefers window capture and falls back only when that path is unavailable; a brief gap between frames does not switch the source.

For alternating success and failure, note the capture mode and check minimization, strip visibility and game/display scaling. After saving or updating a module, wait for addon installation before /reload; do not create an empty replacement module to “fix” a loading state.

Automatic Diagnostics

1. Enable Debug: automatically save failure diagnostics in system settings and reproduce the issue.
2. Open the directory shown in that setting’s help text. A failure latches state and available game pixels immediately; a background worker writes at most once per second and keeps the latest 10 records. Queued failures survive recovery; a full queue skips new samples.
3. Zip the relevant dump-… folders in full. Include the client version, capture mode, whether you resized the game, and the approximate time. Turn diagnostics off when finished.

Each folder contains state and failure details in state.json, recent logs in recent.log, and game pixels in frame.bmp when available. If no new image exists, the record may use the last game capture with its source and age identified. If no game image has been captured, it records why the image is missing; it does not substitute a screenshot of WA1. Brief failures are recorded promptly, but no matching image can be guaranteed when the queue is full or the game supplies no frames.

Account & Security

• One session per account: logging in on a new device immediately kicks the previous one off (macros stop).
• Forgot password: message us on Discord and we’ll reset it — your cloud modules are unaffected.
• Ban risk: automating a rotation is against Blizzard’s Terms of Use, so some risk always exists and you use WA1 at your own risk. WA1 never injects or reads memory and sends keys at a human pace, but that does not make it permitted.
• Owned modules are encrypted and synchronized to the cloud. Editable modules can be exported as readable .wa1 files. Export and clone permissions depend on the source; redeemed modules are always read-only.

Tip

For modules that matter to you, the editor’s “Export Module” saves a local .wa1 copy — no login needed. “Import Module” replaces the current module’s contents with a .wa1 file; the module keeps its Id and saving publishes the next version.

Updates

• If a new version is found at launch, the app updates first and then starts; while running it also downloads and verifies the next version ahead of time, with progress shown on the main bar, so the next launch is up to date — no manual download.
• To disable auto-update, drop an empty noupgrade.txt into the program folder.

About “Protected Values”

Retail (Midnight) marks some combat-related values (unit health, aura timing, etc.) as “protected” for addons, so they can’t be used in arithmetic directly. This has no effect on normal use; but if you write custom module code you must follow the corresponding rules — see Scripts and Runtime.