"Corrupted client" needs to be explained
 

Hello, hl2dm servers use smac-cvars on competive servers to limit some cvars and some people have mistakes in their cfg, so they get kicked with message "corrupted client". But players can't understand what is the problem, SMAC does not say which CVAR returns weird value.
I will give you example:
As you can see this players had troubles with quotes in cfg and has a long strin in his "rate" convar. Smac gets the reply from client and can't compare it to allowed bounds and kick client saying "Cleint corrupted". People start to reinstall steam and the game, they do not understand what is wrong.
I suggest to SMAC developrs to improve the message player gets explaining which cvar has trouble.
Now only admins in logs can see what is wrong ;(

Re: "Corrupted client" needs to be explained
 

i can read rate was 100000 instead of 80000

Re: "Corrupted client" needs to be explained
 

...remove check of these client convars:
rate
cl_updaterate
cl_cmdrate

and use server convars to limit players rates:
sv_minrate 80000
sv_maxrate 80000
sv_minupdaterate 66
sv_maxupdaterate 66
sv_mincmdrate 66
sv_maxcmdrate 66

And why not check client rate convars ?
Because server cvars can restrict player rates, players can't set lower (or higher) rates what server have set up.
You need follow net_graph current update/cmd rates to see it.
And typing client convar in your own game console without value you see decription of restriction.
https://forums.alliedmods.net/attach...1&d=1395656368

And player client side rate convars (cl_*) can have any value what they like, server plugins can read those however but there is no use of them.
Players can check server current rate restriction by they self, typing in they console

https://forums.alliedmods.net/attach...1&d=1395656396

Re: "Corrupted client" needs to be explained
 

haha thats how it used to be but for SOME reason SOMEONE decided to force em in this idiotic way :P

Re: "Corrupted client" needs to be explained
 

Ade, rate was set to this whole string (look closely):
Some players have a mess with quotes in their cfg. Maybe i gave not the best example, but here is another one: Shogo had cl_cmdrate "66"", for example and could not understand what is wrong (hope you see double quote after 66).

Bacardi you are right in theory, but ability to set cl_updaterate to 9000 value is good example showing sv_maxupdaterate does not work. You may say the game can not send 9000 packets anyway which is true, but in hl2dm world it makes your shotgun stronger for some reason and your interp approaches to zero even though sv_client_min_interp_ratio is set to 1.
If you are interested, here is more detailed explanation.

Rates is not subject of this topic. I wanted to suggest good improvement, but you say nothing about suggestion :(

Re: "Corrupted client" needs to be explained
 

it doesnt reach 0, that's fake lerp as 0.1 but the server sees its true value, 15.1, so I really don't see where the problem lies if you use sv_maxupdaterate; even if you check your update rate in console it will say: it's x but server has temporarily restricted it to y

and i cba to read 6 pages, and i dont think im the only 1
and LOL at stronger shotgun, i doubt this makes my shotgun any stronger than it has been, now, before these rates, before even ob update...

Re: "Corrupted client" needs to be explained
 

Oh God, wrong forum (or at least thread), Ade, to discuss "rates".

Once again, the main idea is: "Corrupted client"-message should be explained to players so they knew what is wrong with their cfg.

Re: "Corrupted client" needs to be explained
 

Oh God, I feel Bacardi and I read ur main post as a variation of the XY problem and replied accordingly

and i can read both ur examples just fine: name of the rate command, followed by the value of it, regardless of the number of quotes... gl finding a solution to any or both of your problems