[Owyn]

i get an error too so i can't play it either, person who got banned sent me it, just look at first screen, i descripted you a situation from what he says and from what we see on screens

[Bugsy]

Originally Posted by Pamaliska use play, not viewdemo

Tried play, playdemo, viewdemo

@owyn

It's hard to tell what actually happened with just looking at a screenshot. For all I know he was legitimately detected and then ran over to where the bot was and took a SS.

[Owyn]

SS is taken automaticly right after ban, and ban is automaticly right after detection without any delays
he's a fair player and been checked before

he killed an enemy (via HS) that was at right down the staird near passage from enemy territory and an enemy under him was shooting his teammate near him, then killed the guy under him (not via hs)

[Bugsy]

Originally Posted by .Owyn. SS is taken automaticly right after ban, and ban is automaticly right after detection without any delays he's a fair player and been checked before he killed an enemy (via HS) that was at right down the staird near passage from enemy territory and an enemy under him was shooting his teammate near him, then killed the guy under him (not via hs)

Very strange. The angles are now checked before the bot is spawned. Once the watched player gets a kill, an imaginary line is drawn from the watched player to where the bot will be spawned. If this angle is outside of spec, no bot will be spawned. If the player aims in a downward direction at all it should have been blocked since atleast a 5 degree upward aiming angle is required (looking straight ahead is a 0 degree angle). Thanks for the report

Ill do some more experimenting and hopefully get it to occur.

[xOR]

L 03/15/2009 - 18:24:14: [AMXX] Displaying debug trace (plugin "aimbotdetect.amxx")
L 03/15/2009 - 18:24:14: [AMXX] Run time error 4: index out of bounds 
L 03/15/2009 - 18:24:14: [AMXX]    [0] aimbotdetect.sma::ShootsBlanks (line 1644)
L 03/15/2009 - 18:24:14: [AMXX]    [1] aimbotdetect.sma::client_authorized (line 476)

this is the error with debug mode.

[Bugsy]

Thanks, I found the problem and fixed it.

[Bugsy]

While fixing the above bug I also found a bug in the auto-watch ratio checking that resulted in an auto-watch being applied much more frequently than it was supposed to. I accidentally had get_pcvar_float instead of get_pcvar_num on the point incrementer var; the number being returned by get_pcvar_float was something crazy like 3242342 when it should have been 1. This was resulting in an auto-watch point being added any time that single ratio check was met.

[xOR]

great. are you planning to release the changed version soon? and if not, could you PM or mail the small update to me? see, my servers are currently at risk of getting broken again at any time, it just doesn't make so much sense to play there when no bullets hit
although people can still kill with HE and knife.

[Bugsy]

Here is the temporary fix for people that need it now. I did not have time to test but it should work. Please report back if you still get the bug.

[xOR]

seems to work fine so far, the error messages immediately stopped with the new version.