[Jonzky]

I am just wondering what sort of confidence (in the detections) is in the auto-trigger module? I have had two detections through it (with two detection on the same player).

L 11/01/2011 - 18:17:39: [smac_autotrigger.smx] cpt... {IUA} (ID: STEAM_0:1:****) is suspected of using auto-trigger cheat: auto-fire (1)
L 11/01/2011 - 18:35:39: [smac_autotrigger.smx] KING.... (ID: STEAM_0:0:****) is suspected of using auto-trigger cheat: auto-fire (1)
L 11/01/2011 - 18:36:10: [smac_autotrigger.smx] KING.... (ID: STEAM_0:0:****) is suspected of using auto-trigger cheat: auto-fire (1)

[Drixevel]

Kind of the same as the aimbot module when it comes to detections, it's only likely if you get a ton of detections instead of 1-2.

[TnTSCS]

Exactly - it is "possible" to jump on the exact frame the game allows you to jump, but not jump after jump after jump...

I guess it would be possible (although I would think not) to fire on the exact frame the game allows another fire, but not shot after shot after shot.

[GoD-Tony]

I know this isn't documented yet, but the number at the end of the log messages means the method used for detection, not the amount like the aimbot module.

Originally Posted by Jonzky I am just wondering what sort of confidence (in the detections) is in the auto-trigger module? I have had two detections through it (with two detection on the same player).

That's a bit suspicious, but what type of weapons are being using on your server? This is gmod right? Is it just standard hl2 weapons?

Originally Posted by r3dw3r3w0lf Kind of the same as the aimbot module when it comes to detections, it's only likely if you get a ton of detections instead of 1-2.

It's different on this module. For one detection to show up, you have to be detected 10 times internally before any signal is given. Each internal detection expires after 5 seconds, which means they have to happen very close together as well.

Originally Posted by TnTSCS Exactly - it is "possible" to jump on the exact frame the game allows you to jump, but not jump after jump after jump...

Again not only are we talking about using the exact frame, but also doing it 10 times relatively close to each other.

Originally Posted by TnTSCS I guess it would be possible (although I would think not) to fire on the exact frame the game allows another fire, but not shot after shot after shot.

Can you elaborate on what you mean by this?

[Jonzky]

Originally Posted by GoD-Tony That's a bit suspicious, but what type of weapons are being using on your server? This is gmod right? Is it just standard hl2 weapons?

The server the detections were on was running a custom weapon pack. Until (possibly) a known, respected player (someone who i can trust) is detected I'll treat the as highly suspicious. Just to point out that the (3) detections did not coincide with a kill.

We do have two other (popular) servers that run a game-mode that uses (possibly modified) CS:S weapons. We do have an anti-cheat tailored to the two other servers (which bans them a minute after detection), Ill raise the time to 10 minutes so that I can test SMAC against a known 'detector' - We would normally get 1/2 hackers banned through it a day.

I'd assume this module is good against triggerbots - If not then whats its main role?

/* Triggerbot */
function SH.Triggerbot( uc )
        if( !SH.vars.aim ) then return end
        if( SH.funcs.GetCVNum("sh_triggerbot") != 1 ) then return end
        if( !me:Alive() ) then return end
       
        if( SH.vars.tlock && !SH.vars.firing && me:Alive() ) then
                oRCC("+attack")
                SH:SetVar("firing",true)
                oT.Simple( me:GetActiveWeapon().Primary and me:GetActiveWeapon().Primary.Delay or 0.05, function()
                        oRCC("-attack")
                        SH:SetVar("firing",false)
                end )
        end
end
    
end

Thats an example of such a thing in GMod.


Edit:

Would you consider an anti-nospread module in SMAC - Assuming its possible to detect.

[GoD-Tony]

Originally Posted by Jonzky The server the detections were on was running a custom weapon pack. Until (possibly) a known, respected player (someone who i can trust) is detected I'll treat the as highly suspicious.

I'm also very suspicious, especially with the player that had two detections so close together. This module was designed not to give any false positives to begin with.

Originally Posted by Jonzky Just to point out that the (3) detections did not coincide with a kill.

This is to be expected since many players hold down their auto-trigger buttons while in a safe spot.

Originally Posted by Jonzky I'd assume this module is good against triggerbots - If not then whats its main role?

Yes, that's an example of what it should be catching.

Originally Posted by Jonzky Would you consider an anti-nospread module in SMAC - Assuming its possible to detect.

I'll be looking into upgrading the Eye Test module with new detection methods when I have time for it.

[TnTSCS]

Originally Posted by GoD-Tony Can you elaborate on what you mean by this?

Ha, maybe it's not possible... I was talking out of the side of my neck with that comment.

sorry about that.

And I overlooked this as well #define TRIGGER_DETECTIONS 10 // Amount of detections needed to perform action

So ya, if we are notified of a violation, I would say it's a confident detection

[Lucky_luck]

I have this Error.log ^^

[SM] Unable to load plugin "smac_autotrigger.smx": Native "SMAC_LogAction" was not found

[GoD-Tony]

Originally Posted by Lucky_luck I have this Error.log ^^

You need to upgrade to the latest SMAC core.

[TnTSCS]

Originally Posted by GoD-Tony Can you elaborate on what you mean by this?

I just thought of something... would using the mouse scroll wheel possibly cause a detection for the auto-fire trigger to false detect a player?

Maybe not my wheel mouse because I have the notch-ball still on my wheel, but I've seen tutorials that tell people to remove that notch thing so they can just free spin their mouse (tuts for how to bhop)... but I could see people doing this for their weapon fire...

I'll write a quick script tonight to type something on every frame and then type something when I fire my weapon using my mwheeldown and see how many times I can get my fire action to trigger frame after frame...

might be impossible, but I'll try it out.

Then I'll change that script to have the OnGameFrame force my player to fire every frame to see what that does.

Even if for nothing other than my own gratification, this will be a good code exercise for me