[Sierra]

The time between the first and second (reported) detection was 6 minutes and the next detection was just 3 minutes after that. I just found it odd that the internal counter had not been set back for 6 minutes but was set back somehow after 3. But maybe that's completely normal behaviour, I don't know how this whole thing really works ^^

I think the detection # is the type of detection, not the counted number of times he was detected as a cheater

As far as I know the no. behind detection really is the amount of times SMAC caught someone, at least in this module. The report of the auto-trigger module works the way you described it, TnTSCS.

[TheAvengers2]

The # decreases by 1 every 10 minutes regardless of whether or not it incremented during that time.

[GoD-Tony]

Originally Posted by TheAvengers2 The # decreases by 1 every 10 minutes regardless of whether or not it incremented during that time.

This is correct, and the timer begins on detection #1, which isn't logged or sent to admins.

[Sierra]

Thanks for clearing that up, both of you!

[TFC]

L 01/21/2012 - 03:21:00: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #2) (Deviation: 46°)
L 01/21/2012 - 03:23:11: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #3) (Deviation: 46°)
L 01/21/2012 - 18:03:24: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #2) (Deviation: 45°)
L 01/21/2012 - 18:04:44: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #3) (Deviation: 64°)
L 01/21/2012 - 19:17:19: [smac_aimbot.smx] Old Man Sutters (ID: STEAM_0:1:46142014 | IP: 174.98.91.3) is suspected of using an aimbot. (Detection #2) (Deviation: 46°)

if i want auto-permaban for aimbot, must have smac_aimbot_ban "4" right?

why did he not get banned?

there is smac.cfg

// This file was auto-generated by SourceMod (v1.4.2-dev)
// ConVars for plugin "smac.smx"


// [smac_aimbot.smx] Number of aimbot detections before a player is banned. Minimum allowed is 4. (0 = Never ban)
// -
// Default: "0"
// Minimum: "0.000000"
smac_aimbot_ban "4"

// The duration in minutes used for automatic bans. (0 = Permanent)
// -
// Default: "0"
// Minimum: "0.000000"
smac_ban_duration "0"

// Include extra information about a client being logged.
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
smac_log_verbose "0"

// Display a message saying that your server is protected.
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
smac_welcomemsg "1"

[Sidder]

L 01/22/2012 - 15:31:56: Info (map "c8m5_rooftop") (file "errors_20120122.log") L 01/22/2012 - 15:31:56: [SM] Native "GetClientWeapon" reported: Client 4 is not in game L 01/22/2012 - 15:31:56: [SM] Displaying call stack trace for plugin "smac_aimbot.smx":

Ive been getting this in my error log, not sure exactly what it is for =)


edit:nm

[Sierra]

why did he not get banned?

Because there never was a 4th detection (in a row) ^^ He triggered the aimbot module 3 times in the morning and then another 3 times in the evening.

[GoD-Tony]

Originally Posted by Sidder L 01/22/2012 - 15:31:56: Info (map "c8m5_rooftop") (file "errors_20120122.log") L 01/22/2012 - 15:31:56: [SM] Native "GetClientWeapon" reported: Client 4 is not in game L 01/22/2012 - 15:31:56: [SM] Displaying call stack trace for plugin "smac_aimbot.smx": Ive been getting this in my error log, not sure exactly what it is for =)

Seems rare, but fixed in r408.

[TFC]

Originally Posted by Sierra Because there never was a 4th detection (in a row) ^^ He triggered the aimbot module 3 times in the morning and then another 3 times in the evening.

ty. understand....
and this?

L 01/23/2012 - 20:10:57: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #2) (Deviation: 91°)
L 01/23/2012 - 20:11:34: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #3) (Deviation: 51°)
L 01/23/2012 - 20:24:05: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #2) (Deviation: 72°)
L 01/23/2012 - 20:24:10: [smac_aimbot.smx] Hคηdsomε (ID: STEAM_0:0:47137016 | IP: 108.29.117.41) is suspected of using an aimbot. (Detection #3) (Deviation: 50°)

[Sierra]

and this?

looks like the same question I had a few posts above.
And this is the answer that was given to me:

The # decreases by 1 every 10 minutes regardless of whether or not it incremented during that time.

So basically he got caught, which made it go to detection #3.
Then he didn't trigger anything for a certain amount of time (10 minutes) which made it go back down to detection #1 (or even #0, I don't know).
After that this lucky shot triggered it again...

But seeing that he already has been banned on some TF2 community site (Reason SMAC: Aimbot Detected) and him being caught on 2 differnent days on your server I think you can safely just ban the guy ^^ (except if there are any problems with false detections in TF2)

Hope that helped!