Ok thanks for quick answer.
I though if each players sent (packets)cmdrate 100 to server
and server "balance" updaterate 66 each player so everything works that should be.
(Player max. settings cl_updaterate 66 cl_cmdrate 100)
If
-tickrate 66, player can't sent over 66 cmdrate
But this was my notion
anyone free to use
And I test myself again those rates,
I found new-goofy-trick on those server commands.
If you start using
sv_mincmdrate 1 - 100 (0 disable)
You get another command in use
"sv_client_cmdrate_difference" = "20"
replicated
- cl_cmdrate is moved to within sv_client_cmdrate_difference units of cl_updaterate before it is clamped
So here example, server (that we can see results)
-tickrate 100 sv_maxupdaterate 60 sv_minupdaterate 60 sv_maxcmdrate 100 sv_mincmdrate 10
Player can't set
cl_updaterate because it's locked
60
Player can set
cl_cmdrate 10 - 100 but it depends new command
sv_client_cmdrate_difference
- If sv_client_cmdrate_difference 20
- player can set cl_cmdrate between 40 - 80
- If sv_client_cmdrate_difference 1
- player can set cl_cmdrate between 59 - 61
- If sv_client_cmdrate_difference 100
- player can set cl_cmdrate between 10 - 100
This work like tolerance, players
cl_updaterate 50
sv_client_cmdrate_difference 10
Player can set
cl_cmdrate 50 (+- 10)
And it follows updaterate if change
Now player change
cl_updaterate 80
Player
cl_cmdrate 80 (+- 10)