[GoD-Tony]

Originally Posted by CenT I speak of the module aimbot if you have not situated the module which I spoke ^^

What did you mean by "not responsive enough"? Also, it's best to post about it in the Aimbot module thread to keep things on topic.

[psychonic]

Originally Posted by GoD-Tony I'm a bit confused. The default is off

I didn't realize that. Not sure what all the fuss is about then.

[thetwistedpanda]

GoD-Tony, just a fyi there are many CS:S minigame maps that will could produce false positives as I've seen it happen numerous times. Maps that allow a player to take control of another entity, such as a boat or a chopper, have repeatedly punished players under KAC, so it's likely this one will do the same.

[klausenbusk]

Originally Posted by thetwistedpanda GoD-Tony, just a fyi there are many CS:S minigame maps that will could produce false positives as I've seen it happen numerous times. Maps that allow a player to take control of another entity, such as a boat or a chopper, have repeatedly punished players under KAC, so it's likely this one will do the same.

#define FL_ATCONTROLS			(1 << 6)	// Player can't move, but keeps key inputs for controlling another entity

PHP Code:

if(!(GetEntityFlags(client) & FL_ATCONTROLS))
{
// he are not controlling another entity :)
} 


?

[GoD-Tony]

Originally Posted by psychonic I didn't realize that. Not sure what all the fuss is about then.

I believe CenT was simply asking how to interpret his logs because he had set it to log only.

Originally Posted by thetwistedpanda GoD-Tony, just a fyi there are many CS:S minigame maps that will could produce false positives as I've seen it happen numerous times. Maps that allow a player to take control of another entity, such as a boat or a chopper, have repeatedly punished players under KAC, so it's likely this one will do the same.

I added a "buffer zone" to avoid detection in these types of scenarios, but with klausenbusk's snippet it can now be completely avoided.

Originally Posted by klausenbusk ?

I am impressed with this simple solution. This should also take care of potential issues on other mods such as DoD:S/INS and their stationary weapons. Thanks!

[GoD-Tony]

A little update on this: From the feedback I've received (as well as my own servers), this module has had a 100% detection rate for CS:S, and you should be able to safety enable automatic banning for this mod.

It's also quite aggressive at catching cheaters, as almost all aim related cheats seem to violate the eye angle boundaries that this module checks.

I haven't heard anything back about other mods, so it's still considered experimental outside of CS:S.

[Xp3r7]

Originally Posted by GoD-Tony A little update on this: From the feedback I've received (as well as my own servers), this module has had a 100% detection rate for CS:S, and you should be able to safety enable automatic banning for this mod. It's also quite aggressive at catching cheaters, as almost all aim related cheats seem to violate the eye angle boundaries that this module checks. I haven't heard anything back about other mods, so it's still considered experimental outside of CS:S.

Will it lag a 32 slot server like the wall hack module does?

[GoD-Tony]

Originally Posted by Xp3r7 Will it lag a 32 slot server like the wall hack module does?

No, it should not.

[Jonzky]

How does the detection work? Assuming that a cheat would set the angles above the limit would it mean that there would be a continuous flood of logs for a client who might be cheating or would the 'cheater' only have these angles in specific circumstances?

[GoD-Tony]

Originally Posted by Jonzky How does the detection work?

It checks a player's angles on every tick to make sure they aren't too far outside the normal range. Typically a cheater will join the server, shoot once, and be detected right away.

Originally Posted by Jonzky Assuming that a cheat would set the angles above the limit would it mean that there would be a continuous flood of logs for a client who might be cheating

Yes, normally this would cause a huge amount of flooding. I added code to only allow one detection per player connection. Otherwise a cheater would be detected and logged during every tick of the server (66 times per second).

For servers that have this module set to log/warn only, it might be a good idea to allow a detection to happen once per minute if the player is still in the server. I'll think about adding this in.