Aimbot FOV Source code

obviously, he did read it you dick. Quit being an asshole if you have nothing important to say.

noobs and hacks good combo omg! if u are noob better dont hack sure u use like a stupid rat

hahahahah. wtf

how to use this? kappa

ah and you guys were born knowing what to do i guess..

If someone doesn't know how to use something, then try to help them out. You guys didn't know how to use this at one point, so stop acting like dicks if someone doesn't know something.

Thanks! And for anyone wondering what this is, it's just a code snippet to interpret another players distance and calculate the aimbot's FOV. Typically used with an aim smoothing method. I'm not a big fan of math so this definitely helps.

Thanks just tested it and it works fine. My Aimbot is less obvious now.
(I was too lazy to do the maths myself :P)

How about pointing ppl in the right direction, or links to find out for themselves some sort of path instead of calling ppl noobs etc.

please anyone help me im new to this

What the hell is this crap? I joined to check out some pubg cheat code, and this is the sort of stuff posted? It looks like it was written by a beginner and offers nothing to anybody that could already code. So, since nobody else has called this out, i see
1) You doing some basic trig to get distance from xhair to player using the player's bone coord, but you don't say how your transforming 2d xhair position and 3d bone position to the same coordinate system, so, this part only benefits people who didnt pass grade 9 math and don't know Pythagoras theorem.

2) You've correlated a set of distances with a set of FOVs, but given no context to why (eg, you don't say what local.Distance(pos) is). Based on the fact you're using 15x, 8x, etc, i assume youre using it to detect current scope, which makes sense as you want the FOV. This code is stupid on many levels. On a basic technical level, try writing proper IF statements, eg, you have superfluous else clause, and then a totally separate IF rather than all one single, sensible conditional. On a DEEPER technical level, this entire thing should be an enum or associate array (eg std::map, whatever) if you're doing a lookup to hardcoded values. On a deeper conceptual level, this is super naive, surely there is a way to calculate FOV more accurately, eg, taking into account a) user FOV settings, b) different scopes not accounted for here, such as 1.5x zoom from red dot sights.

So basically, i just don't understand why this was even posted, it offers nothing to someone that can code, and it offers nothing to someone like me that CAN code, but hasn't previously hacked the game.

PS if there is honestly something useful here i've missed, my apologies, and please point it out.