Antiaim detector fix #220
Antiaim detector fix #220
Conversation
|
Feel free to test it for yourself and tell me if you encounter more false positives (; |
|
If you really wanna be sure that there are no false positives you can increase the treshold in the config to >= 2, but this will limit the legit AA detection a little bit, but it seems like this can fix all false positives, as all of the possible ones had 1 infraction and only 3 out of over 50 cheaters wont get caught. |
|
As of now I eliminated every false positive and got all but 1 false negative. |
|
Are you sure what angles can be >180? 👀 |
|
I have no idea why but if found out, that sometimes the angle can get higher, especially on legit players, which causes false positives. For example 1 player got 5 false positives and i checked the LBYdelta value and it was >230 (;. So I did tests with about 40 demos now and I was able to resolve all false positives and of every player in these demos only 2 spinbots werent detected, which causes me to doubt that they had an AA in the first place and not just pitch down. |
|
Also the values of the cheaters were always between these 2 values. |
|
I don't sure, but normalized angles can't be > 180. But, if that work, then fine 👀 |
Well this shouldn't give you false positives in 99% of the cases. The only real false positive from 150 suspects was a suspect who was doing +left in console, which broke the animation one time. Also I got 2 possible false positives, but these suspects were raging and I could not see any legit AA, but I think there was one. There were also 6 possible false negatives, which were spinbots, but they could have disabled desync and since I don't check for pitch down, those were not detected.
From 150 cases 141 where correct. But keep in mind that the threshold has to be >= 1. Also this CAN detect legit AA.
Maybe the possible false negatives can be detected, if we change the lby_delta treshold, but this is trial and error.