[Greyscale]

Is it possible to remove the cheat flag on client convars?

cl_forwardspeed is the only thing limiting run-speed in CS:S after changing m_flMaxspeed. It's a client-side cheat cvar that won't allow their speed to exceed that number and I want to go above it.


Any way to do this?

[Sammy-ROCK!]

have you checked sv_maxspeed?

[Greyscale]

sv_maxspeed defaults to 320, if you increase that to say 1000, cl_forwardspeed still caps it at 400.

It's like 2 layers of clamping.

[blodia]

the clients speed is limited by sv_maxspeed and the cl_ cvars, whichever is lowest.

i have a method that works for a script i'm working on, first set sv_maxspeed to your maximum speed, lets say 1000, then in OnPlayerRunCmd check vel[0] and vel[1] to see if they're 400/-400 then change them to your max speed 1000/-1000. the client always sends the max speed limited by the cl_ cvars.

[Greyscale]

So changing the 'vel' vector in OnPlayerRunCmd to the sv_maxspeed will fix it?

[blodia]

only the 1st 2 elements of the array, and you have to check if its positive or negative, oh yeah you also have to multiply it by 1.1363636 so if its -400 then -(sv_maxspeed)*1.1363636 and for 400 its sv_maxspeed*1.1363636.

[Greyscale]

I'm confused.

Where does 1.1363636 come from? And wouldn't the magnitude of the first 2 elements be what I need to pay attention to?

Can I just do vel[0] = 1000.0; vel[1] = 1000.0 ?

Maybe a snippet of your code would explain better.

[rhelgeby]

Almost. The vel array is a vector (as I you already knew I think), so the length of the vector is the speed. You need to calculate the first two elements based on the speed you want, or all elements if you want vertical speed too.

[blodia]

i haven't cleaned up the code as i was testing it to see if it worked as i hoped.

PHP Code:

public Action:OnPlayerRunCmd(client, &buttons, &impulse, Float:vel[3], Float:angles[3], &weapon)
{
    if (vel[0] != 0.0)
    {
        if (vel[0] < 0.0) vel[0] = -600 * 1.1363636;
        if (vel[0] > 0.0) vel[0] = 600 * 1.1363636;
    }
    if (vel[1] != 0.0)
    {
        if (vel[1] < 0.0) vel[1] = -600 * 1.1363636;
        if (vel[1] > 0.0) vel[1] = 600 * 1.1363636;
    }
    return Plugin_Continue;
} 


the 3rd element is always 0 from what i saw. the 1st 2 are either -400, 0 or 400 so you don't need to find the length of the vector as it is either 0 or 400, acceleration is processed sometime after this info is passed to the server. its negative and positive to relate to which direction the client is moving e.g back or forward. when i changed the values and tested them i saw the actual maxspeed was less than the value i was testing (600 in the snippet), after trying a few values i found i had to multiply the value i wanted by 1.1363636.

[blodia]

i don't know if you have got it working how you want Greyscale but i've been doing more tests and it seems as though you don't have to multiply by 1.1363636, i was using cl_showpos to check my speed and since its capped clientside to 400 and i was changing on the server side the display wasn't correct. so this should work fine

PHP Code:

public Action:OnPlayerRunCmd(client, &buttons, &impulse, Float:vel[3], Float:angles[3], &weapon)
{

    if (vel[0] < 0.0) vel[0] = -1.0 * <variable containing sv_maxspeed>;
    if (vel[0] > 0.0) vel[0] = <variable containing sv_maxspeed>;
    if (vel[1] < 0.0) vel[1] = -1.0 * <variable containing sv_maxspeed>;
    if (vel[1] > 0.0) vel[1] = <variable containing sv_maxspeed>;

    return Plugin_Continue;
}