SRCDS Steam group

Checkin rate usage?
I read on a diff post soemone was able to chk how many rates were being used per client. how am i able to do this?
[Image: 461031727.png]

Zb_block feature: zb_netinfo
When you've got mani installed: ma_rates
Set sv_minrate, sv_mincmdrate, sv_minupdaterate to whatever you want and that's it. It doesn't matter if players have corresponding cl_* settings set to anything lower. They will be forced by the server to the server settings.

However, this is only half the truth. I've written about this many times before. Player's maximum rate is his maximum FPS. Thus, a player who doesn't get solid 100+ FPS will never reach 100 rate.

Similar case:
The solution:

The solution works only for Linux, though Toungue ... but really, use server's server.cfg to force the rates you want. Then kick&ban players who you know are using rate hacks.
well... ive got my rates setup up. but then i see players with cmdrate and updaterate at 20's-30's
and i have to be asking ppl to change thier rates. the forcing of rates doenst seemt o be workin
and regardin ma_rates. where is says IN section is that the rates used per player or. for the entire group?
which section tells u how many rates EACH players is usgin. and not the cmdrate or updaterates just rates. like
rate 30000
[Image: 461031727.png]

just write ma_rates in console
Server forces the sv_cmdrate regardless what players have. Player can have cl_cmdrate 20, but the server can still force player's cmdrate to 60. The value in ma_rates won't change, but the player is forced to cmdrate 60 anyway.
but then why lets say for xample. a player has cl_cmdrate 1 and my server files is "forcing" cl_cmdrate 60
i dont see a change in ma_rates. but their ping is at 5 and are teleporting accross the map. when i ask them to change the rates. thier ping moves up to 80 and they stop skipping about.
[Image: 461031727.png]

Are you sure you have configured it properly?

Here is some history for all of you.

November 29, 2006, 4:15 pm - Jason Ruymen - Product Update

Added cvars to let the server prevent clients setting unreasonable network settings: sv_mincmdrate, sv_maxcmdrate, sv_client_predict, sv_client_interpolate, sv_client_interp, and sv_client_cmdrate_difference

June 12, 2007, 1:45 pm - Jason Ruymen - Product Update

Fixed a bug with sv_minrate and sv_maxrate not applying properly on the client

Forum Jump:

Users browsing this thread: 1 Guest(s)