Dead Radio Stream Rap Indie Hip Hop Music

Posts: 1305 · Posted: Sun May 20, 2007 15:46

Ok - it seems that some people are still pointing their fingers are the rates problem from time to time, whether it be ingame whilst playing or talking about it here on the forums, but they also don't seem to realise how annoying/frustrating it is to keep going on about it. So let it be known:

THEY ARE ENFORCED BY THE SERVER

Regime has stated this fact multiple times (and displayed the config settings too - see end of post) and even if players are somehow bypassing these settings then it's down to Valve to get sorted out - Regime can't control this. The setting has been made to ensure a level playing field for all who join - even if you do think something is "screwy" with an opponent, just do one thing before you talk or report it: do you really want to cause the admin another headache?

Now, I'm off to get some WE LOVE REGIME! t-shirts printed... Wink

server config
---------------
rate 20000-30000
cl_updaterate 66-67
cl_cmdrate 66-67
cl_interp_* is also forced (forgot to what value)

Posts: 3635 · Posted: Sun May 20, 2007 17:59

Heh thanks Jay.. I gotta admit it is getting rather annoying to constantly have to repeat it. I'm starting to sound like a broken record. Smile

Now what you posted are the values the rates are enforced to. It might actually be quite a good idea to post a bit of the config file of the server though; If anyone wants to critisize them, they can provide me with sources that prove me wrong. The config settings are below.

Code:

// Minimum bandwith rate. Forces players 'rate' setting to be this value as minimum. (value between 0-30000)
sv_minrate "25000"

// Maximum bandwith rate. Forces players 'rate' setting to be this value as maximum. (value between 0-30000. 0=unlimited)
sv_maxrate "25000"

// Minimum interp ratio. Forces players 'cl_interp_ratio' setting to be this value as a minimum. (Default=1)
// sv_min_cl_interp_ratio divided by sv_min_updaterate is the minimum interp clients would be able to use.
sv_min_cl_interp_ratio "1"

// Maximum interp ratio. Forces players 'cl_interp_ratio' setting to be this value as a maximum. (Default=2)
// sv_max_cl_interp_ratio divided by sv_max_updaterate is the maximum interp clients would be able to use.
sv_max_cl_interp_ratio "1"

// Minimum update rate. Forces players 'cl_updaterate' setting to be this value as minimum. (value between 0-100)
sv_minupdaterate "66"

// Maximum update rate. Forces players 'cl_updaterate' setting to be this value as maximum. (value between 0-100)
sv_maxupdaterate "67"

// Minimum cmd rate. Forces players 'cl_cmdrate' setting to be this value as minimum. (value between 0-100)
sv_mincmdrate "66"

// Maximum cmd rate. Forces players 'cl_cmdrate' setting to be this value as maximum. (value between 0-100)
sv_maxcmdrate "67"

// cl_cmdrate is moved to within sv_client_cmdrate_difference units of cl_updaterate before it is clamped between sv_mincmdrate and sv_maxcmdrate.(Default=20)
sv_client_cmdrate_difference "1"

// This can be used to force the value of cl_interpolate for connected clients (only while they are connected)
// -1 = let clients set cl_interpolate to anything (Default)
// 0 = force cl_interpolate to 0
// 1 = force cl_interpolate to 1
sv_client_interpolate "1"

// Enable or disable Valve's lag compensation
sv_unlag "1"

// Time in seconds Valve's lag compensator will compensate for (Default 0.5 -> 500ms)
sv_maxunlag "0.5"

// Ping samples to use for deciding how much lag to compensate (Default 1)
sv_unlagsamples "1"

// Enable or disable push lag compensation
sv_unlagpush "0"

Some very unfriendly (and now banned) person, pointed out on the server yesterday that rate enforcement does 'not work' because of the cl_restrict_server_commands thing being set to 1 for some players. Just so you know this is absolute rubbish, as the only thing that cvar does, is control whether a server admin can execute commands on a client. If we were using a 3rd party rate enforcement tool then this would be true, cause they physically change the values on the client by using client exec commands. The method we use does not change any values on the client however, nor does it run client exec commands. It just ignores the values the client wants to use and forces the client to use the values the server sees fit. These config settings that make the server do that (above) are part of the source engine and are not affected by cl_restrict_server_commands.

In case you are wondering why we havent got a plugin on the server that sets the cl_restrict_server_commands thing to 0 for everyone; The whole cvar cl_restrict_server_commands will be removed in the next Valve update. Instead, there will be a small number of client exec commands that will be allowed by default (whitelisted by Valve) and no option of turning off the blocking for the rest of the commands. So basically; Soon cl_restrict_server_commands "1" will be the only option anyone has.

Jay I hope you dont mind but I have changed the title of the topic, so people will know where to look for it better..

Posts: 1305 · Posted: Sun May 20, 2007 20:57

Nope - not got ANY problem with that - I'm just glad you found the post ok - let's hope this slows down if not stops the queries about it.

Posts: 3635 · Posted: Sat Mar 29, 2008 12:28

Lately there have been people complaining to eachother about rates again. I'd like to point out the above as a reminder and add one thing to it...

If you do not believe that client rate restrictions are working, go in game, open up the console and type in:

Code:

rate

Code:

cl_updaterate

Code:

cl_cmdrate

Yes - The same as you would use to set your client rates, but without a number behind them. The current setting will then be displayed in console and you will see a message telling you that the value is enforced by the server to a value as shown in the above post.

Posts: 1531 · Posted: Sun Mar 30, 2008 1:08

omg, rates?