Yeah it was detected i think, i got hit at least in the same day the others did.
Yeah it was detected i think, i got hit at least in the same day the others did.
I haven't got hit and still using it. I wonder if the people that did get hit renamed the executable file? Its pretty basic but you never know...
Outdated shiet
Last edited by n0b0d0y; 06-14-2016 at 08:38 PM.
I never even compiled the exe file, did rename the au3 files tho and got banned two weeks ago or whenever it was.
Last edited by ziggar; 06-14-2016 at 08:08 PM.
Did anyone figure out settings to make this worth using? Just spazzed around like crazy no matter I did to it, and using a sniper with it was worthless. Wondering if it's just that limited or if I used it wrong?
Last edited by aldenceise; 06-15-2016 at 04:41 AM.
I got it wokring fine, I turn the estting down to 10 for smoother aimbot, but slower.. doesn't jerk around alot.. but I think I'm using a diff version than op.
There seems to be a lot of conflicting info here. Was the latest GUI version the one that was detected? I've used it quite a bit and have had no issues whatsoever. Was it the non-GUI version then?
I reckon they were looking for it for a short amount of time only. After all once it has gotten people banned there is no need to invest resources to catch a fraction of what they already did.
Iirc, there was some unnecessary injections going on as well and using fastfind.dll which was a completely pointless telltale sign of sinister activities (since fastfind.dll from the looks of it was just a wrapper for couple gdi+ functions).
Guess with the mouse emulation block it doesn't even work anymore.
autoit is basically the easiest to detect. ever.
the reason why autoit is so popular, is that you can write bots pretty fast and easily simply with pixelrecognation. thats why there is an autoit bot for overwatch, because its easy to write, you simply need the get the unique pixels of every skin and point your mouse.
thats why the first bot for d3 was written in autoit too. it was called "script", tho. still a bot.
hearthstone had pixelbots too.
i don't know why ppl still go for this shit. basically every new game, there will be some kind of autoit bots at the start and everybody still asks if this is undetected. you act like 13 year old morons without a clue how this works. you're posting here, that you are not banned, keep using it and you will be banned. stop making theorys if you dont have a clue or just assume something.
even in a game, were a perma bann means, your done with this game, i dont think its worth it to bot. get your shits straigth.
So Auto-it is easy to detect because it is easy to code in? I could write a library that does everything people use auto-it for in an hour or two... but it wouldn't really make any difference. You are bashing pixel bots, not Auto-It. The reason why people are staying at the pixel level is due to the protection Blizzard has put into the game. Last I read, the game crashes on any ReadProcessMemory calls without doing something special beforehand. Injecting any DLLs into the game that isn't whitelisted also leads to a ban. Blizzard has done REALLY well with protecting the game so far. Don't bash people's attempts at staying out of process.
Yeah it was great for what it was and the time it came out, still have a pixel bot that works fine but now using another one that is memory based, the pixel bot sure helped until i found an external hack tho.
And i know chancity put a lot of work into it so don't think it's fair for you to come here talking shit.
I mean you can make autoit work well if you read memory too, who was it that had a known cheat in autoit at some point? Oh yeah supex0.
Can someone send me the script please? I couldn't find it anywhere! Thanks
I, too, please send the code, I'll see what I can do.