Its 1 YEAR and 1 DAY and i have done my homework!Quote:
There's is 100% way of detecting your fake inputs with your knowledge.
After you'll do your homework, learn writing drivers, dive into Windows kernel space and studying the fuck up you shall be able to not get caught based on a few simple methods written in "Cockblocking script-kiddies, Pt. I" book.
YOU ARE RIGHT I WAS YOUNG AND STUPID and i still am.
Today i did my first driver based cheat now i can send fake inputs.
Just to shine some light on the topic, GG is hooking NTSendinput its an undocumented Windows function ...
The only way you will get around this is to make a driver.
or use Public sources like:
[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
These make it pretty easy to send fake inputs, the 2nd one is a Wrapper for c# so it should be possible to Programm for everyone.
After spending a hole lot of time trying and trying with Win32 i noticed a weird behavior for GG sometimes GG does not block your fake inputs, even the Control Send Function from AutoIt sometimes success, i have read on a Korean Thread ages ago that GG might Scan programs for Malicious code and blocks the process of sending Fake inputs for example. I could not replicate the specific circumstances and i am not really sure why it happens but this is a possible loop hole for the hole driver thing. If anyone wants to investigate it take note, for me it seems as slower hardware for example on a vps i had proofed to be more reliable in replicating this bug, but still i am not really sure how it happens in the first place.