search

Jire / Overwatcheat

Free, open-source undetected color cheat!
GNU Affero General Public License v3.0
320 stars 92 forks source link

What to change in source code to make it work again? #45

Open safadao123 opened 6 years ago

safadao123 commented 6 years ago

Hey can you tell me what to change on the source so that it works again? I`ve read some people changed a couple of lines and it was working again, so i wonder if you or anyone could tell me. Ty.

v-b7 commented 6 years ago

@safadao123 Even if you would make it work you will be banned/screen-locked. Injected mouse events sent by this aimbot can be detected by blizzard's anti-cheat

Jire commented 6 years ago

@v-b7 mouse_event() directly sends input into the mouse stream. You would have to hook NtUserSendInput() on kernel mode to determine if it was physically or virtually sent, and Blizzard does not.

My guess how they can detect some cheats is: A gaming mouse sends 1000 inputs per second normally. If they would count the events per second when you DON't shoot and compare them with the amount of inputs per second WHILE you shoot and there is a "huge" consistent difference.

Why Overwatcheat will last for years, or even forever: You still retain full control of the mouse when the aimbot is active, and the aimbot mouse events are sent at a rate far less than your gaming mouse.

And just to clarify: People have been using a fixed version of this cheat for years without any bans.

safadao123 commented 6 years ago

@Jire What did you change to make it work ? Do you know of any bypass to screenlock working atm? I tried obs but it didnt work and people are saying it was patched

v-b7 commented 6 years ago

@Jire Some say that they can detect injected mouse events. One way is by installing a hook that monitors low-level mouse input events. A sample here. They pushed an update that got several banned or screen-blocked a couple of months ago, however, if you say that your method still works then those blizzard employees aren't that smart after all :smile: