You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know, on GoldSrc status command prints detailed info about clients if this command was invoked from HLDS command line. But when clients uses status command on server, limited information being sent to the clients, for example clients IPs not presented in there for obvious reason. I think this command should work like it works in GoldSrc, but also I have some ideas:
XashID shouldn't be exposed in command output in case when some client invoked this command. We could print some salted value, and salt should be randomly generated once on dedicated server process startup.
We also could present additional non-vulnerable clients info, like their platform name or type of used input interface (keyboard, mouse, gamepad, touch, etc.)
Hashed XashID is already available for other clients through svc_updateuserinfo message. I decided not to put any XashID value in proposed status command yet.
Nor did I include complete useragent, as this might be somewhat sensitive information, considering how unique build number + os + arch combination might be. Maybe we can just send os-arch string, it should be less harmful.
However I added sending input devices. I think other clients deserve to know what input devices the player claims to have enabled.
While we're here, I tried to improve the original status command output, making it easier to read in my taste.
When joining server and typing
status
command, it isn't being sent to the server, instead just printsno server running.
The text was updated successfully, but these errors were encountered: