[TwOzCaR]

Originally Posted by SaintK Will the changes discussed here be applied in the official builds?

only if the authors want too, so we can't say for sure. but some tweaking is necessary for some modules (wh/aimbot) for the official builds after my opinion.

[GoD-Tony]

Originally Posted by SaintK Will the changes discussed here be applied in the official builds?

I would prefer getting SMAC released in the official thread first, and then we can begin testing a revised Aimbot module over here in the dev builds.

[Mike_BoG]

Whoa. SMAC has banned over 10 players the last 24 hours for aimbotting, even players who i didn't see had an aimbot. After looking trough the logs and the STV recordings they snapped and got banned. Yeeey

[SaintK]

edit - nm

[TwOzCaR]

Originally Posted by Mike_BoG Whoa. SMAC has banned over 10 players the last 24 hours for aimbotting, even players who i didn't see had an aimbot. After looking trough the logs and the STV recordings they snapped and got banned. Yeeey

nice =) it did the trick then, they were all confirmed cheaters via demo ?

[SaintK]

Originally Posted by TwOzCaR you need to edit the aimbot.sp file and recompile the sourcemod plugin. it is sat to 45o which is way to underpowered, maybe a 25 angle would be better find in -> sourcemod/scripting/smac/aimbot.sp

This is confirmed too low. It triggered multiple detects on a client playing heavy having no aimbot.

L 08/11/2011 - 21:183: [SpA]Gibboss28 (ID: STEAM_0:1:13 | IP: 82.18.) is suspected of using an aimbot. (Detection #2) (Deviation: 31°)

[TwOzCaR]

Originally Posted by SaintK This is confirmed too low. It triggered multiple detects on a client playing heavy having no aimbot.

there are 2 lines of interest which is good tampering with

line 26: #define AIM_ANGLE_CHANGE 15.0 // Max angle change that a player should snap

line 251: if (fAngleDiff > 45)
fAngleDiff = (fAngleDiff - 90) * -1;

my settings at the moment ^ but u say 25 is too low set? is that confirmed or just a thought?

[SaintK]

Originally Posted by TwOzCaR there are 2 lines of interest which is good tampering with line 26: #define AIM_ANGLE_CHANGE 15.0 // Max angle change that a player should snap line 251: if (fAngleDiff > 45) fAngleDiff = (fAngleDiff - 90) * -1; my settings at the moment ^ but u say 25 is too low set? is that confirmed or just a thought?

I only changed the 45.0 value to 25.0 - and that is definitely, confirmed to low. It had "Deviation: 31°" where that client is 100% clean.

[GoD-Tony]

Originally Posted by TwOzCaR line 251: if (fAngleDiff > 45) fAngleDiff = (fAngleDiff - 90) * -1;

Whoa, this part shouldn't be changed at all. It's there because of the way that the angles need to be calculated.

/*
    Using these values as an example:
    vLastAngles = -179
    vAngles = 170
*/

/*
    GetVectorDistance() will return 349 in this case,
    but the player didn't do such a large spin.
*/
fAngleDiff = GetVectorDistance(vLastAngles, vAngles);

// The max a player could snap is 180, and the above case is accounted for here.
if (fAngleDiff > 180)
    fAngleDiff = (fAngleDiff - 360) * -1;
    
// Player snapped 11 degrees. 

I probably should have commented the code as I went along, but this went from a small test case to SMAC pretty quickly.

[Mike_BoG]

Just got my first false-positive.. I guess i should set it up to 30 or higher?