Esp And Aimbot Script

[Brian Bezdicek]

Alright, in response to some of the aimbot posts made in support, etc.. I decided to take some time and write a pixelsearching proof of concept Aimbot. I figure now when people ask for help about writing aimbots we can refer them to this thread .

I was actually surprised by the speed of PixelSearch. I was expecting it to be significantly slower than it was over such a large area. I did a few timed tests before I went forth and wrote this and the results warrented spending a little time on it. (40-60 miliseconds for a 1024x768 area!!)

However, you can tell that when the object is moving at a decent rate, pixel searching the entire screen would not be possible. In the Camper Strike example, when you have the setting "On + Autoshoot" you can see how it sometimes trails behind the faster moving targets. However, if you set it to "Snap-To Autoshoot" because it has a small search area... the targets are easily brought down.

-Snap-to (Scans an area 50sq pixels surrounding your mouse and if you get near a target it will snap to the target. It will then only scan an area of 10sq pixels while locked onto the target. Much faster)

I think the best aimbot for a FPS written in autoit (at least.. the best/easiest) would be a pixelsearch of a box around your mouse position and force you to "snap" to the heads of enemies. With the speed of pixelsearch in this proof of concept, I think it would be deadly.

Yes.. well, Lets say I was writing an aimbot for a FPS. Pixelsearching the entire screen might be a little too slow, but if I pixelsearched a reasonable square area around your mouse you would simply have to move the mouse "somewhat" close to your enemy, then it would snap to their head.

It has nothing to do with what process your AutoIt script "looks like". They progmatically block you from using commands like Send(), MouseClick(), etc, etc. Which is why the fake device driver gets around it. It emulates an actual mouse so the program can not tell the difference.

Probably a controversial script, but that's irrelevant. I've only mapped the pixelsearch algorithm for the basic two outfits in source (CT and T) so if you use this with regular counterstrike it won't work on the other models.

Basic concept is that it scans a single pixel and compares it using an algorithm to what a typical pixel color of an enemy uniform looks like. If it gets a match, it will fire 3 shots. Because this script needs a fast response time, it can only scan a single pixel, and that pixel happens to be dead center in the crosshairs. How well does it work? Pretty darn well. It does mess up though in the tunnel areas because they are so dark, like the enemy outfits; and for this reason I have implimented a hot-key to pause/unpause it. When you select your hotkey at the start of the program, map that key to the middle mouse button using the intellimouse 4.0 keymapper. I find this works best because you'll want to pause/unpause at split second notice. Feedback (not flames) appreciated.

I am a member of www.japsclan.com it is not a virus website... It is actually, one of the only safe bot sites for counterstrike... I have no idea why the hell you would accuse me of that... But it must not be good. BTW: Don't bag on me, when it comes to hacks, I know what I'm talking about.

One more thing. Since you obviously feel that I am trying to infect your computer with something. I might as well say this: Your script isn't an aimbot... It is just an autoshooter. You can actually what you are saying through the actualy Counter-Script... If you know couner strike scripting, like me, it isn't very hard. Check out www.counter-script.com if you need anymore original ideas.

/\/,Oct 27 2004, 03:25 PM]One more thing. Since you obviously feel that I am trying to infect your computer with something. I might as well say this: Your script isn't an aimbot... It is just an autoshooter. You can actually what you are saying through the actualy Counter-Script... If you know couner strike scripting, like me, it isn't very hard. Check out www.counter-script.com if you need anymore original ideas.

4. Console scripting is limited to what is available in the program. What I have done cannot be done via console. There was an old auto-aimbot for CS writtin via the console, but that was patched; this cannot be patched and it is the only aimbot for Counterstrike Source.So, creating something external like this has several benefits: (i) valve can't patch it; (ii) valve can't detect it.

Basically I just screencapped like 20 shots from various distances and angles of the counterterrorists and terrorists. I then tried to find a general range for colors, and then just wrote constraints - and those constraints took the form of that equation you see. And to increase the speed, I added "If $r

1. When you posted your message your website was down. So I searched google for cache containing the term japsclan.com and found various threads saying that it was one of those sites claiming "CS cheats" but in reality installed a few nasty viruses onto your PC. Couple this with the fact that you did not post anything else with your link. Why just post a link? Maybe you are pissed off at people writing stuff like this for CS? Makes sense. Also, www.JapsClan.org is an official site, and not your site. So there were MANY very shady things behind your original post, so don't get pissy if I incorrectly assumed that your non-existant site was a virus.

one more thing, japs clan is all about cheats, or at leats thats what ive heard, so i stay away from them, one of them came into our server a while ago, booted him out right away, thats why i hate cheating in counter-strike its gay

Here is Version2 of my script. The two main hotkeys now are F1 and F2 and then you still have your pause button. F2 is the same old function in my original script. So just press F2 to enable that, and pause/unpause to turn it on/off.

F1 though is really designed for long range stuff. If you are sniping or just aiming at something far away, the formula in the original program doesn't work too well. So this is where the F1 function comes into play. It samples a single pixel, then freezes all input on the keyboard and mouse, and then continues to check that same pixel for a change for the next 5 seconds. If a change is detected, it will fire three rounds and then unlock the kb+mouse.

BlockInput() is required for this simply because one slight movement of the mouse will register a pixel-change and it's very hard to keep your hand still... so BlockInput() is the only way to go. The downside is obviously the 5s freeze - so if someone comes from behind you or towards you outside of the crosshair, you will likely die. Thus only use F1 for long range attacks; but it works incredible!

Future changes? Two things I want to do when I get a few minutes. First, when switching between F1 and F2, the "first" time you hit pause, you must hit it twice to pause. But after that, pause must only be hit one time. Confusing to explain, but once you try it you'll see what I mean. I want to fix that later and just have one pause needed. And second, sometimes there is dust in the air on the gamescreen and it will register a pixel change if it floats past you. So I want to build some tolerances for the F1 function. Other than that, this program pushes the limits of what can be done with an aimbot and CS. Enjoy!

* Lua scripts require a Lua executor

* These scripts have only been verified to work on the WeAreDevs API exploits such as JJSploit

* If a script has broken features, they may have been patched

* If you found a broken script, please let us know in the forum so it can be taken down

* You can submit your own script on the forum. Be detailed and make it clear that its a submission

3a8082e126