Idea: detection for camping and aimbots.
For aimbots this might maybe help: http://aimbots.net/tutorials/18257-lean-3-sigma-howto-detect-fellow-cheaters.html I don't understand it fully, but maybe you can use some code or something.
Things you might look at (not sure if the topic i linked to looks at any of this):
-accuracy differences between instant and non-instant hit weapons not normal (gotta test enough owners and newbers with accuracy stats of all weapons to get this right though)
-accuracy of instant hit weapons ~55-65% (just tested the lastest version of KingOrgy's clienthook for 085, got 2x 60% and 1x62%)
-use of instant hit weapons versus non-instant hit weapons
-speed almost never gets over g_speed+15% (dont think you can get more than that without strafe jumping, the 320ups speed limit is often exeeded on turning or something but never gets over like 10%)
-direction player is looking in changes a lot when it does (you could make something like this: 0-fovdegrees:x times; fov-fov+45:x times; fov+45-fov+90:x times. And count every frame how much it differs - it will almost never change over fov+45 degrees in One frame but it does when aimbotting)
Btw only suspect if kills>200 on ctf, or combine kills of a couple of maps in dm. Else stats aren't accurate enough I think.
They should also get autoreported on some site when the detection system detected a high chance on it for the third time in a day or something (counting once per map), especially if they got kicked out (then the first cheat detection should be a report too). Not autobanned, just autoreported (and if possible autodemo'd&uploaded).
For campers, count the kills while staying in the same radius (say 400 units) for 10 seconds? (so save the location of the last 10 kills or something and compare when the player kills another).
^those are just ideas, i am not really asking for anything but it'd be cool to keep oau clean of all shit. I think some of the aimbot checks wouldn't be too hard, so we could release it in beta if some are implimented. The camper check should (doing it this way) just be an array of killplaces and a few if-tests on them on the event of a kill (which is already "detected" of course), so also doable.
For aimbots this might maybe help: http://aimbots.net/tutorials/18257-lean-3-sigma-howto-detect-fellow-cheaters.html I don't understand it fully, but maybe you can use some code or something.
Things you might look at (not sure if the topic i linked to looks at any of this):
-accuracy differences between instant and non-instant hit weapons not normal (gotta test enough owners and newbers with accuracy stats of all weapons to get this right though)
-accuracy of instant hit weapons ~55-65% (just tested the lastest version of KingOrgy's clienthook for 085, got 2x 60% and 1x62%)
-use of instant hit weapons versus non-instant hit weapons
-speed almost never gets over g_speed+15% (dont think you can get more than that without strafe jumping, the 320ups speed limit is often exeeded on turning or something but never gets over like 10%)
-direction player is looking in changes a lot when it does (you could make something like this: 0-fovdegrees:x times; fov-fov+45:x times; fov+45-fov+90:x times. And count every frame how much it differs - it will almost never change over fov+45 degrees in One frame but it does when aimbotting)
Btw only suspect if kills>200 on ctf, or combine kills of a couple of maps in dm. Else stats aren't accurate enough I think.
They should also get autoreported on some site when the detection system detected a high chance on it for the third time in a day or something (counting once per map), especially if they got kicked out (then the first cheat detection should be a report too). Not autobanned, just autoreported (and if possible autodemo'd&uploaded).
For campers, count the kills while staying in the same radius (say 400 units) for 10 seconds? (so save the location of the last 10 kills or something and compare when the player kills another).
^those are just ideas, i am not really asking for anything but it'd be cool to keep oau clean of all shit. I think some of the aimbot checks wouldn't be too hard, so we could release it in beta if some are implimented. The camper check should (doing it this way) just be an array of killplaces and a few if-tests on them on the event of a kill (which is already "detected" of course), so also doable.
+1!
If i good remember i had already 64% as stat on a server and i'm not da master ^^ Look in QL the best one have 69% average for 108 games 
lol
)
