Guide WoW — External Pixel-Based Rotation Bot via AHK

[byte_corvus]

External solutions are increasingly the only way to stay off the radar in World of Warcraft. While injection-based scripts are getting clapped in every ban wave, a well-tuned pixel-reader is practically invisible to Warden because it doesn't touch the game memory. This method relies on simple logic: an addon suggests a spell, the script sees it, and the script presses the button.

Technical Foundation
This setup works on Retail, Classic, and WotLK. Since we are using AutoHotkey (AHK) to read pixel data from the screen, the risk of detection is extremely low compared to internal cheats. There is no memory hooks, no DLL injection—just pure screen scraping and input simulation.

Core Setup & Logic

1. Initial Tools — Grab the latest AutoHotkey build. It's the standard for automation.
2. Addon Integration — You need a priority helper to tell the script what to do. Use Hekili for Retail or WeakAuras for Classic/WotLK. The goal is to have a single icon on the screen that changes based on the next recommended spell.
3. Frame Strata — This is crucial. Set your addon's display frame to TOOLTIP strata. This ensures that UI elements like BNet notifications or low-health red pulses don't overlap with the pixel the script is trying to read.

Spoiler: The Pixel Calibration Process

To make the script work, you need to identify the exact BGR (Blue-Green-Red) color values of the icons your addon displays.

1. Position your suggestion icon in a fixed spot where it won't be moved.
2. Use a pixel-picking tool (many AHK-based ones exist on GitHub) to find the X/Y coordinates and the 0x hex color code of a unique pixel within that spell icon.
3. Repeat this for every spell in your rotation. Note that some icons share similar colors, so aim for a unique pixel (like a specific highlight or shadow).

The Script Architecture
Your AHK script follows a standard "if-then" loop. Below is the logic used to bind the rotation to a specific key (in this case, the '2' key).

#ifWinActive World of Warcraft

$2::
While GetKeyState("2","p"){

; --- Firebolt Logic ---
PixelGetColor, color, 2498, 396
If (color = 0x37376B){
    Send, {6}
    Sleep 20
}

; --- Next Spell Add Here ---

}
return

Key Definitions:

1. #ifWinActive — Safety check. The script only fires when WoW is the focused window.
2. GetKeyState — The loop continues as long as you hold the hotkey down.
3. PixelGetColor — Reads the BGR value at the X/Y coordinates you calibrated.
4. Send — Simulates the keystroke for that specific spell slot on your action bar.
5. Sleep — Prevents the CPU from maxing out and keeps the inputs looking (somewhat) human.

Operational Requirements
Always RUN AS ADMINISTRATOR. If AHK doesn't have admin privileges, it frequently fails to send inputs to the WoW game client. If the script throws a syntax error on launch, usually it's a missing curly brace or a malformed hex code.

Spoiler: Notes for Advanced Users

If you want to get fancy with modifiers like Shift or Ctrl, you can use the following syntax in the Send command:

Send, {Shift down}{6}{Shift up}

This allows you to keep your main action bar clean and hide the automated spells on hidden bars.

For those running Retail, Hekili is basically cheating out of the box once you link it to a script like this. Just keep an eye on your AoE toggles—if the addon is suggesting Multi-Shot while you're in a single-target fight, your script is going to follow it blindly.

Anyone else using custom WeakAuras to feed colors to their AHK scripts, or are most of you still sticking to Hekili?