So, correct me if I’m wrong, but there’s a relatively simple formula to convert the GUID (which in fact is the Steam CommunityID (aka SteamID64)) to SteamID.
Also, correct me if I’m wrong again, but DrFunkenstein found that one could use guidstates.dat from QW as a template for setting up auto-login usergroups based on GUID (SteamID). This effectively circumvents having to set and use a universal password among admins. (right?)
Furthermore, it looks like we’ve got some decent independently-made RCON tools that will work with multiple servers.
So, these are the only outstanding issues I see remaining:
-
It seems to me that the first and foremost pressing issue that remains is that you can’t RCON the current playerlist of a server which means you have to manually look it up via other means if you want to use an RCON tool to kick/ban someone.
-
Unless I missed something, it seems we have no first-person spectating. This makes spotting hackers extremely difficult. Furthermore, we have no demo recording, which would also aid in this matter immensely.
-
We have no way to set up reserved slots based on GUID in the same fashion as mentioned with the guidstates.dat. Currently, I believe you have to use a universal password from a console command to have the server kick someone and connect you in their place. This sort of functionality is paramount to communities that pay to host servers for any game and a universal password is simply unmanageable.
Am I missing anything here? That’s all I could come up with as being absolutely necessary. I can think of other things, of course, but nothing as important as these.
What say you, Splash Damage?
