- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 729
- Reaction score
- 457
Tired of tunnel-visioning on your ConROC procs while missing boss mechanics?
Found a decent external tool for the Classic community that handles rotation cues via pixel detection. It is essentially an OpenCV-powered screen scraper that watches for specific spell icons and fires off keybinds. Since it does not touch game memory (no RPM/WPM), it functions independently of the WoW process, though automation always carries a risk profile.
Architecture & Implementation
The tool is built using Python and leverages the OpenCV library for template matching. You define a specific screen region, provide a reference image of the spell icon (proc), and map it to a keybind. It is a clean way to automate rotations without the heavy lifting of memory-based bots.
Setup & Configuration
Configuration is straightforward but requires a few minutes to align with your UI layout:
Security & Logic Notes
The executable is packed with PyInstaller, which is notorious for triggering heuristic flags in mediocre AV engines due to how it bundles automation libraries. Check the VirusTotal logs yourself if you are paranoid.
From a safety perspective: while it avoids the usual Warden memory scans, Blizzard can still flag accounts based on input overhead. If you use this, try to keep your setup looking human; don't run it for hours on end without breaks.
It is a solid base for anyone looking to optimize their DPS without digging into memory offsets. Anyone else have experience tweaking OpenCV thresholds for faster detection in 25-man raids?
Found a decent external tool for the Classic community that handles rotation cues via pixel detection. It is essentially an OpenCV-powered screen scraper that watches for specific spell icons and fires off keybinds. Since it does not touch game memory (no RPM/WPM), it functions independently of the WoW process, though automation always carries a risk profile.
You cant view this link please login.
Architecture & Implementation
The tool is built using Python and leverages the OpenCV library for template matching. You define a specific screen region, provide a reference image of the spell icon (proc), and map it to a keybind. It is a clean way to automate rotations without the heavy lifting of memory-based bots.
- Pixel-based detection — Zero memory footprints; it only reads what is rendered on your screen.
- Dynamic Region Selection — Choose exactly which part of the UI to monitor to save on CPU cycles.
- Threshold Control — Tweak the sensitivity to ensure the bot doesn't misfire on similar-looking icons.
- Keypress Duration — Configurable timing to manage how long a key is held down.
- Profile Management — Save and load configurations for different classes or specs.
Setup & Configuration
Configuration is straightforward but requires a few minutes to align with your UI layout:
- Launch the executable and navigate to the Detection Settings tab.
- Use the 'Select Area' tool to draw a box over the location of your rotation icons or ConROC interface.
- In the Spells tab, capture the icon of the spell you want to automate while it is visible in-game.
- Assign the corresponding in-game keybind to that icon.
- Toggle the bot using the global hotkey (Default: Ctrl+Shift+X) and verify the detection log.
Security & Logic Notes
The executable is packed with PyInstaller, which is notorious for triggering heuristic flags in mediocre AV engines due to how it bundles automation libraries. Check the VirusTotal logs yourself if you are paranoid.
From a safety perspective: while it avoids the usual Warden memory scans, Blizzard can still flag accounts based on input overhead. If you use this, try to keep your setup looking human; don't run it for hours on end without breaks.
Does this work with retail WoW?
While targeted at Classic, the OpenCV logic is engine-agnostic. If you can see it on your screen, you can map it.
Is there any memory reading involved?
None. It is strictly a screen-reading automation tool.
What happens if I change my UI scale?
You will need to re-capture your spell icons, as OpenCV relies on consistent pixel patterns.
While targeted at Classic, the OpenCV logic is engine-agnostic. If you can see it on your screen, you can map it.
Is there any memory reading involved?
None. It is strictly a screen-reading automation tool.
What happens if I change my UI scale?
You will need to re-capture your spell icons, as OpenCV relies on consistent pixel patterns.
It is a solid base for anyone looking to optimize their DPS without digging into memory offsets. Anyone else have experience tweaking OpenCV thresholds for faster detection in 25-man raids?
