[CowGod]

Originally Posted by Drumanid Maybe it's worth doing an anti flood of 'bans'? Example: PHP Code: g_iTime[MAXPLAYERS + 1]; // Global public void CheckSidemoveCount(int client) {     if(g_iPerfSidemove[client] >= g_ConVar_SilentStrafeBanThreshold.IntValue)     {         int iTime = GetTime();         if(g_iTime[client] > iTime) return;         g_iTime[client] = iTime + 5;         PrintToChatAll(" \x0B[\x02AC\x0B] \x0E%N \x01- найден Silent-Strafe!", client);         ServerCommand("sm_ban \"%N\" \"%i\" \"[AntiCheat] Silent-Strafe\"", client, g_ConVar_SilentStrafeBanTime.IntValue);                  g_iPerfSidemove[client] = 0;     } }

It's very rare that that detection will flood bans, but it does happen from time to time so I will just add something when I wake up in a little bit thanks for the input.

[Lubricant Jam]

Cow never seems to disappoint, good release my dude.

[CowGod]

Originally Posted by Lubricant Jam Cow never seems to disappoint, good release my dude.

Thanks for the support man, if you have any suggestions or questions just let me know. Now I actually need to go to sleep LOL because I have been up way too long. Tomorrow I will finish working on the wallhack blocking

[Panimal]

Great work! i dont use SB, so now i can use it on my servers. thanks

[Razvann.]

// CowAntiCheat.sp(365) : error 017: undefined symbol "SourceBans_BanPlayer"
// CowAntiCheat.sp(486) : error 017: undefined symbol "SourceBans_BanPlayer"
// CowAntiCheat.sp(533) : error 017: undefined symbol "SourceBans_BanPlayer"
// CowAntiCheat.sp(572) : error 017: undefined symbol "SourceBans_BanPlayer"
// CowAntiCheat.sp(655) : error 017: undefined symbol "SourceBans_BanPlayer"
// CowAntiCheat.sp(829) : error 017: undefined symbol "SourceBans_BanPlayer"

Why? (trying to compile)

Solved: upgrading files of SBans to the newest.

[ASKER_CZ]

Isnt it easier to trigger sm_ban playername ?.. do it like this please

[r3v]

Hey, CowGod! I uploaded your AntiCheat in my CS:S server. One player got a ban with this reason:

PHP Code:

[CowAC] TriggerBot / Smooth Aimbot Detected. 


I have SMAC with Anti Aimbot module, but no logs about aimboting. I watched demo, but nothing suspicious. He was banned, then he gets killed... Is this recommended for CS:S? Is there big difference between these two games, especially aimbot? First time I installed this AntiCheat 1.06 version a few days ago then you release it, now updated to 1.08 and this is first ban with your anticheat today. Here's the cfg:

PHP Code:

// This file was auto-generated by SourceMod (v1.8.0.6040)
// ConVars for plugin "CowAntiCheat.smx"


// Enable aimbot detection (bans) (1 = Yes, 0 = No)
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_aimbot "1"

// Threshold for aimbot ban detection (Default: 5)
// -
// Default: "5"
ac_aimbot_ban_threshold "3"

// Ban time for aimbot detection (Default: 0)
// -
// Default: "0"
ac_aimbot_bantime "0"

// Enable auto-shoot detection (logs to admins) (1 = Yes, 0 = No)
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_autoshoot "1"

// Threshold for auto-shoot log detection (Default: 20)
// -
// Default: "20"
ac_autoshoot_log_threshold "20"

// Enable backtrack elimination (1 = Yes, 0 = No)
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_backtrack "1"

// Enable bhop detection (bans) (1 = Yes, 0 = No)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_bhop "0"

// Threshold for bhop ban detection (Default: 10)
// -
// Default: "10"
ac_bhop_ban_threshold "10"

// Ban time for bhop detection (Default: 10080)
// -
// Default: "10080"
ac_bhop_bantime "10080"

// Enable instant defuse detection (logs to admins) (1 = Yes, 0 = No)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_instantdefuse "0"

// Ban time for instant defuse detection (Default: 0)
// -
// Default: "0"
ac_instantdefuse_bantime "0"

// Enable macro detection (logs to admins) (1 = Yes, 0 = No)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_macro "0"

// Threshold for macro log detection (Default: 20)
// -
// Default: "20"
ac_macro_log_threshold "20"

// Enable perfect strafe detection (bans/logs) (1 = Yes, 0 = No)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_perfectstrafe "0"

// Threshold for perfect strafe ban detection (Default: 15)
// -
// Default: "15"
ac_perfectstrafe_ban_threshold "15"

// Ban time for perfect strafe detection (Default: 0)
// -
// Default: "0"
ac_perfectstrafe_bantime "0"

// Threshold for perfect strafe log detection (Default: 10)
// -
// Default: "10"
ac_perfectstrafe_log_threshold "10"

// Enable silent-strafe detection (bans) (1 = Yes, 0 = No)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_silentstrafe "0"

// Threshold for silent-strafe ban detection (Default: 10)
// -
// Default: "10"
ac_silentstrafe_ban_threshold "10"

// Ban time for silent-strafe detection (Default: 0)
// -
// Default: "0"
ac_silentstrafe_bantime "0"

// Enable triggerbot detection (bans/logs) (1 = Yes, 0 = No)
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
ac_triggerbot "1"

// Threshold for triggerbot ban detection (Default: 5)
// -
// Default: "5"
ac_triggerbot_ban_threshold "3"

// Ban time for triggerbot detection (Default: 0)
// -
// Default: "0"
ac_triggerbot_bantime "0"

// Threshold for triggerbot log detection (Default: 3)
// -
// Default: "3"
ac_triggerbot_log_threshold "3" 


[weeeishy]

@r3v, regardless if it works for css or not. Reset your threshold to the default values. Read this from the first post..
"I highly recommend leaving ban/log thresholds at their current values to further avoid false positives."

[Czar_]

Originally Posted by ASKER_CZ Isnt it easier to trigger sm_ban playername ?.. do it like this please

Would probably be best to just add a sort of sourcebans detection and ban based on that. I use BoomPanel so I just removed everything that requires sourceban.

[r3v]

Originally Posted by weeeishy @r3v, regardless if it works for css or not. Reset your threshold to the default values. Read this from the first post.. "I highly recommend leaving ban/log thresholds at their current values to further avoid false positives."

My fault. Thank You.