so why not share the code so more people can start working on the aim bot and get it working ?
Work in progress : Undetectable PS2 Aimbot.
id rather see 4 threads with the same mod then no mods .
When is the hack finnished u think?
did you get the hack to work

If you want the source code of a working pixel aimbot for PS2, google "if( NumberOfObjects > 0 && AIM && AimKey)".
Replace model rec with if(m_Stride == 20 && NumVertices > 600).
Use bat file to run game in 32 bit mode.
Use low sensitivity.
Replace model rec with if(m_Stride == 20 && NumVertices > 600).
Use bat file to run game in 32 bit mode.
Use low sensitivity.
Okay I got the code.... but I don't know what you mean by "Replace model rec with if(m_Stride == 20 && NumVertices > 600).
Use bat file to run game in 32 bit mode."
Use bat file to run game in 32 bit mode."
Dead? No, this is definitely not dead.
However, I have right now more important matters to attend to.
I'll start working on this bot around December again. Would be a nice Christmas gift, right?
I did notice what's wrong with my bot though, so if I can somehow find a work-around, the bot'll indeed be released around christmas.
As for the problem I'm having : The bot looks for #ff0011 at x + y on a 1080 x 1080 area, and moves your mouse to that area that works as a OVERLAY.
The problem lies in the fact it's a 1st person shooter and your mouse is basically clipped in the center, which means if you move your pointer it'll turn the screen (thus moving the pixel) and start re-scanning.
The main problem I have is not effectively finding the pixel, but tracking it after it has been found and is moving again....
So yeah, I found the issue, now just to find the way to fix it, and I might have a general idea of how to do that.
So yeah, progress!
For now I'm going to attend to more important matters.
However, I have right now more important matters to attend to.
I'll start working on this bot around December again. Would be a nice Christmas gift, right?
I did notice what's wrong with my bot though, so if I can somehow find a work-around, the bot'll indeed be released around christmas.
As for the problem I'm having : The bot looks for #ff0011 at x + y on a 1080 x 1080 area, and moves your mouse to that area that works as a OVERLAY.
The problem lies in the fact it's a 1st person shooter and your mouse is basically clipped in the center, which means if you move your pointer it'll turn the screen (thus moving the pixel) and start re-scanning.
The main problem I have is not effectively finding the pixel, but tracking it after it has been found and is moving again....
So yeah, I found the issue, now just to find the way to fix it, and I might have a general idea of how to do that.
So yeah, progress!
For now I'm going to attend to more important matters.
Work in progress... where is it? please i need it 

bumping the thread so it never dies
This thread is closed for replies.
Similar Threads
Art & Graphic Designa work in progress 9 Art & Graphic DesignWrestling Ring [Work in Progress] 13 Combat Arms Hacks & Cheats[Working Bypass][New Undetected Injector] 147 CounterStrike (CS) 1.6 Hacks / Counter Strike: Source (CSS) HacksOMFG WORKING HACKS AMAZING!!!!![UNDETECTED]
23 Battlefield 2 Hacks & Cheatsi am looking for a detected or undetected bf2 aimbot
5



Why would the OS and frame rate count..