HelpNeed ideas for new features + aimlock questions

Posts 111 of 11 · Page 1 of 1
Need ideas for new features + aimlock questions
Working on a private external hack, here are my features:
Bunnyhop
Triggerbot
NoFlash
Aimlock
GlowESP
SkinChanger

Also working on a radarhack right now. Should be easy to add.

Does anyone have any ideas for new features I could add?

Also, I'm having some problems with my aimlock. It works just fine I guess, but sometimes with certain weapons it's just garbage. It'll take about 4 or 5 shots to get a kill. In addition, when there are no enemies to lock onto, it'll lock onto a random spot on the map. I've just been kind of dealing with it but it's getting old. I tried adding a dormant check so if there are no enemies to lock onto it just won't write angles. This kind of worked but was too buggy so I removed it.
What could I do to fix these issues?

Thanks for the help.
Quote Originally Posted by tweedash View Post
Working on a private external hack, here are my features:
Bunnyhop
Triggerbot
NoFlash
Aimlock
GlowESP
SkinChanger

Also working on a radarhack right now. Should be easy to add.

Does anyone have any ideas for new features I could add?

Also, I'm having some problems with my aimlock. It works just fine I guess, but sometimes with certain weapons it's just garbage. It'll take about 4 or 5 shots to get a kill. In addition, when there are no enemies to lock onto, it'll lock onto a random spot on the map. I've just been kind of dealing with it but it's getting old. I tried adding a dormant check so if there are no enemies to lock onto it just won't write angles. This kind of worked but was too buggy so I removed it.
What could I do to fix these issues?

Thanks for the help.
To fix the aim lock problem we would need to see your code. Without seeing it I would suggest making it only on while holding a certain key, this way you know when enemy's are able to be locked on to. Also you could add RCS, slowaim, recoil crosshair (assuming it's an external overlay), auto defuse, auto strafe. Auto pistol.
Quote Originally Posted by ImWhacky View Post
To fix the aim lock problem we would need to see your code. Without seeing it I would suggest making it only on while holding a certain key, this way you know when enemy's are able to be locked on to. Also you could add RCS, slowaim, recoil crosshair (assuming it's an external overlay), auto defuse, auto strafe. Auto pistol.
http://pastebin.com/eP5hb8eB
This is my aimlock code.

didn't know auto defuse or auto strafe were possible via external.
Quote Originally Posted by tweedash View Post
http://pastebin.com/eP5hb8eB
This is my aimlock code.

didn't know auto defuse or auto strafe were possible via external.
I'll look at this when I get home, auto defuse is possible, there is a source somewhere on this site
Quote Originally Posted by ImStyL View Post
Here's some things that might help out your aimlock issue,
- Lower down the smoothness(cause i can't think of any other thing that might be causing this)
- Try checking if the target is a player and alive before aiming.

FOV changer with no hands is pretty fun sometimes, so there's a feature for you to think about.

Added you on Skype

Quote Originally Posted by ImWhacky View Post
I'll look at this when I get home, auto defuse is possible, there is a source somewhere on this site
Thanks. I'll look around.
Quote Originally Posted by tweedash View Post
Added you on Skype



Thanks. I'll look around.
i tried the code and it straight up didn't work, all my offsets are up to date and its just not working so at least you got farther than i did lol. and by the way, you dont need so many sleep functions.
Here's some things that might help out your aimlock issue,
- Lower down the smoothness(cause i can't think of any other thing that might be causing this)
- Try checking if the target is a player and alive before aiming.

FOV changer with no hands is pretty fun sometimes, so there's a feature for you to think about.


Just offtopic a bit.
Dafuq .-.

Why dont you "if (!FindCs)" and then log error message, you just cout 2 times in any case, even if FindCs returns false it will say that the thread is running .-. and there is nothing also blocking the thread from been run
Quote Originally Posted by PhY'z View Post


Just offtopic a bit.
Dafuq .-.

Why dont you "if (!FindCs)" and then log error message, you just cout 2 times in any case, even if FindCs returns false it will say that the thread is running .-. and there is nothing also blocking the thread from been run
yeah i completely missed that double cout, fixed
Believe this has been solved.

/Closed.
Posts 111 of 11 · Page 1 of 1
This thread is closed for replies.

Similar Threads

Tags for this Thread

None

Need help?