Just to clarify, is it higher than it was before the unintended changes? Or is it back to "normal"?
It can go higher than before if you are running at very high framerates.
And just to clear up some confusing wording in these posts: We have always sampled user input once every client frame. We have always sent them to the server in batches. The rate of the client sending those batches was accidentally lowered from 60hz to 20hz, and now it's 60hz or even slightly more now. We aren't sending more usercmds than we used to, but we will send each one multiple times now, which will help users with upstream packet loss. Since we're sending them more often, it means the server will get more of them before each cutoff to run the frame, so it should have a modest reduction in latency.
Read more