[ZASTRELIS]

Originally Posted by xeropw Found an extension that claims to block the invalid angles, albeit no bin, which means you must compile it yourself. https://forums.alliedmods.net/showpo...7&postcount=24

And how? You test it? No updates last mounth.

[ZASTRELIS]

I can see how cheater when killed another player shutdown my server. It's happened when he hasn't a large spray.

[xeropw]

Originally Posted by shavit untested plugin that *should* work #include <sourcemod> #include <sdktools> // #define STOP // remove comment to block the usercmd instead of 'fixing' it public Plugin myinfo = { name = "fuck server crashers", author = "shavit", description = "should prevent viewangles crashes", version = "1.0", url = "http://github.com/shavitush" } public Action OnPlayerRunCmd(int client, int &buttons, int &impulse, float vel[3], float angles[3]) { if(IsBadAngle(angles[0]) || IsBadAngle(angles[1]) || IsBadAngle(angles[2])) { #if defined STOP return Plugin_Stop; #else angles[0] = NormalizeAngle(angles[0]); angles[1] = NormalizeAngle(angles[1]); angles[2] = NormalizeAngle(angles[2]); return Plugin_Changed; #endif } return Plugin_Continue; } public bool IsBadAngle(float angle) { return angle > 180.0 || angle < -180.0; } public float NormalizeAngle(float angle) { float temp = angle; while(temp <= -180.0) { temp += 360.0; } while(temp > 180.0) { temp -= 360.0; } return temp; }

So you're just clamping/normalizing angles then? Now since I am slightly unfamiliar with metamod and sourcemod
"inner workings", will a plugin block the server from broadcasting the change in said angles or is it better to do it
on the extension level?

Edit: I can write a small anti-exploit plugin if sourcemod does functionally block these changes.

[ZASTRELIS]

pls do something)

[shavit]

Originally Posted by xeropw So you're just clamping/normalizing angles then? Now since I am slightly unfamiliar with metamod and sourcemod "inner workings", will a plugin block the server from broadcasting the change in said angles or is it better to do it on the extension level? Edit: I can write a small anti-exploit plugin if sourcemod does functionally block these changes.

when i used to develop cheats, around 3 years ago i used a similar sourcemod plugin that blocks anti-aim by normalizing angles and it worked

[xeropw]

Originally Posted by ZASTRELIS pls do something)

Try his angle normalization method.

Here's what you can put in your own custom extension:

PHP Code:

//Extension version
void NormalizeAngles(QAngle &angle)
{
    for(int axis = 0; axis < 3; ++axis)
    {
        while(angle[axis] > 180.f)
        {
            angle[axis] -= 360.f;
        }
 
        while(angle[axis] < -180.f)
        {
            angle[axis] += 360.f;
        }
    }
} 


[root88]

Originally Posted by shavit untested plugin that *should* work #include <sourcemod> #include <sdktools> // #define STOP // remove comment to block the usercmd instead of 'fixing' it public Plugin myinfo = { name = "fuck server crashers", author = "shavit", description = "should prevent viewangles crashes", version = "1.0", url = "http://github.com/shavitush" } public Action OnPlayerRunCmd(int client, int &buttons, int &impulse, float vel[3], float angles[3]) { if(IsBadAngle(angles[0]) || IsBadAngle(angles[1]) || IsBadAngle(angles[2])) { #if defined STOP return Plugin_Stop; #else angles[0] = NormalizeAngle(angles[0]); angles[1] = NormalizeAngle(angles[1]); angles[2] = NormalizeAngle(angles[2]); return Plugin_Changed; #endif } return Plugin_Continue; } public bool IsBadAngle(float angle) { return angle > 180.0 || angle < -180.0; } public float NormalizeAngle(float angle) { float temp = angle; while(temp <= -180.0) { temp += 360.0; } while(temp > 180.0) { temp -= 360.0; } return temp; }

Plugin won't fix this exploit.

[xeropw]

Got some more information. Apparently it is enough to send IN_ATTACK whilst setting the viewangles to crash the server. The server receives the IN_ATTACK request and the incredibly large viewangles and before any response can be done - patching the angles, skipping the cmd, or anything, the server is already crashed.

[ZASTRELIS]

Originally Posted by root88; //Extension version void NormalizeAngles(QAngle &angle) { for(int axis = 0; axis < 3; ++axis) { while(angle[axis] > 180.f) { angle[axis] -= 360.f; } while(angle[axis] < -180.f) { angle[axis] += 360.f; } } }

and what i must do with it?) Where NormalizeAngles func must be used?

public Action OnPlayerRunCmd(int client, int &buttons, int &impulse, float vel[3], float angles[3])
{
    if(IsBadAngle(angles[0]) || IsBadAngle(angles[1]) || IsBadAngle(angles[2]))
    {
        #if defined STOP
        return Plugin_Stop;
        #else
        //angles[0] = NormalizeAngle(angles[0]);
        angles[0] = NormalizeAngles(angles[0]);
        
        //angles[1] = NormalizeAngle(angles[1]);
        angles[1] = NormalizeAngles(angles[1]);
        
        //angles[2] = NormalizeAngle(angles[2]);
        angles[2] = NormalizeAngles(angles[2]);

        return Plugin_Changed;
        #endif
    }

    return Plugin_Continue;
}

public bool IsBadAngle(float angle)
{
    return angle > 180.0 || angle < -180.0;
}

void NormalizeAngles(QAngle &angle)
{
    for(int axis = 0; axis < 3; ++axis)
    {
        while(angle[axis] > 180.f)
        {
            angle[axis] -= 360.f;
        }
 
        while(angle[axis] < -180.f)
        {
            angle[axis] += 360.f;
        }
    }
}

???

[Neuro Toxin]

Originally Posted by root88 Plugin won't fix this exploit.

OnPlayerRunCmd is a prehook and should override / fix the exploit.

Edit: Sounds like removing IN_ATTACK on invalid angles will fix the exploit.

Edit2:

An angle of -10058801942080820000000000000000000
Adding 360 will still leave an invalid angle