- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 805
- Reaction score
- 457
Dealing with Blizzard's anti-cheat in Overwatch 2 is always a game of cat and mouse. If you are moving from internal to external, you are trading ease of development for a different set of detection vectors. KDMapper is basically a giant 'kick me' sign if you aren't clearing traces or handling the IOCTLs properly.
Driver vs. Usermode
If you got clapped using a colorbot with a mapped driver, it's likely not the color sensing itself but how you communicated with the driver. Blizzard scans for leaked drivers and known manual map patterns. Also, if you’re using standard IOCTLs, they can be easily trapped.
Overlay Performance & Hijacking
The reason your overlay is slow as hell is likely because you're creating a top-most window with GDI or a basic DX11 hook that isn't synced with the game's refresh rate. Creating your own transparent window over a high-refresh-rate game like OW2 often leads to massive stuttering and frame drops.
If you're looking at Rigel's source as a reference, keep in mind it's ancient in dev terms. You'll spend more time fixing the offsets and the outdated hooking methods than actually building your features.
Blizzard hasn't been as aggressive as Vanguard yet, but they are definitely stepping up their check on driver communication stacks lately.
Driver vs. Usermode
If you got clapped using a colorbot with a mapped driver, it's likely not the color sensing itself but how you communicated with the driver. Blizzard scans for leaked drivers and known manual map patterns. Also, if you’re using standard IOCTLs, they can be easily trapped.
- Usermode RPM/WPM: It's surprisingly viable for public releases if you handle your handles correctly, but once the AC starts stripping access, you're done.
- KDMapper: It's a classic, but unless you're hijacking a legitimate driver's communication or using a custom communication method (like shared memory), you're vulnerable to IOCTL dispatch hooking/scanning.
- Mouse Input: Interception is bottom-tier. It's been flagged in multiple games. If you want a serious build, go for a proper kernel driver for mouse movement or use a hardware-based solution like an Arduino/KMBox.
Overlay Performance & Hijacking
The reason your overlay is slow as hell is likely because you're creating a top-most window with GDI or a basic DX11 hook that isn't synced with the game's refresh rate. Creating your own transparent window over a high-refresh-rate game like OW2 often leads to massive stuttering and frame drops.
Hijacking an existing overlay (like Steam, Discord, or Nvidia) isn't just about speed; it's about blending in. When you hijack their swapchain, you're utilizing a legitimate process that the AC already trusts to draw frames. If you stick with your own overlay, at least ensure you're using a proper bypass for BitBlt or moving to a layered window setup that doesn't tank the FPS.
If you're looking at Rigel's source as a reference, keep in mind it's ancient in dev terms. You'll spend more time fixing the offsets and the outdated hooking methods than actually building your features.
Blizzard hasn't been as aggressive as Vanguard yet, but they are definitely stepping up their check on driver communication stacks lately.
