Closed ghost closed 11 years ago
Are you sure that's not a plugin with the server you're playing on?
BTW @alfred-valve it might be a good idea to remove cl_cmdbackup like on Source engine, so players don't mess with it.
@AnAkIn1 I'm sure. For tests I use a clean (no plugins, no metamod, no nothing) server downloaded via SteamCMD.
] version
Protocol version 48
Exe version 1.1.2.7/Stdio (cstrike)
Exe build: 16:01:13 Feb 28 2013 (5971)
Server needs to be updated again, been seeing this on a server I play regularly on.
Tried my local linux steamcmd hlds and saw it also, went away after I updated (app_update 90 validate) my local hlds though.
Server version should also be version 5971. (not sure if server 5971 is a beta though, I probably opted in to the beta on my local hlds)
edit: yeah, server 5971 is a beta opt in, maybe they'll push all the beta changes to release today.
It happens on all servers.
I increased the max pending move commands you could send with the last beta updates, servers will also need to update to allow the same number (that beta update will be out today). Running on a listen server should work so I will work out what is going wrong with that.
@alfred-valve : Is there any point to change cl_cmdbackup value?
@alfred-valve Everything is fine on listenserver. Is it possible to write some back-compatibility code? I don't think that server admins will know about SteamCMD and update their servers in a short period of time. I get kick on all servers when a map is changing, old ones, new ones, it doesn't matter. Or force everyone to update their servers: https://github.com/ValveSoftware/halflife/issues/665#issuecomment-14297981
I start a local HLDS, join on it, then I restart the server with
restart
command, and client gets kicked off withCMD_MAXBACKUP hit
message server console:client output:
Everything was working yeasterday
Also, the problem appears on
changelevel