![]() Added a new system for coaching players.Use the ConCommand "cl_gameserver_list" in the Team Fortress 2 client console to list all of the game server accounts owned by the currently logged in Steam account.Put the values for "tf_server_identity_account_id" and "tf_server_identity_token" into your server.cfg.This will generate values for "tf_server_identity_account_id" and "tf_server_identity_token" Use the ConCommand "cl_gameserver_create_identity" in the Team Fortress 2 client console to create a server account using the currently logged in Steam account.Added a new system to associate dedicated servers with Steam accounts.Added the Ready for Duty achievement for completing all of the training courses.Added 3 new training courses for the Demoman, Engineer, and Spy.Spawn room by second cap for each time is now a one-way door.Added a new server convar "sv_logsecret" which emits a new S2A_LOGSTRING2 UDP packet to any UDP log targets with the secret value pre-pended.Fixed a packet injection exploit in the client/server streams.Source Engine Changes (CS:S, DoD:S, TF2, HL2:DM) The updates will be applied automatically when your Steam client is restarted. (High ping usually does very little to registry and all that crap that people complain about.) We can discuss the idea of banning high ping later, but for now it's only an inconvenience.Updates to Team Fortress 2, Counter-Strike: Source, Day of Defeat: Source and Half-Life 2: Deathmatch have been released. If it is really having an effect on gameplay, a kick should suffice. Aside from hacking our server cfg file, you can't get around these settings.Īs for high ping, I am not going to be authorizing a ban, that just seems a step too far. The server forces anyone above or below those rates to the max/min possible. Sv_mincmdrate "33" // Minimum updates per second that the server will allow. Sv_maxcmdrate "67" // Maximum updates per second that the server will allow. Sv_minupdaterate "33" // Minimum updates per second that the server will allow. Sv_maxupdaterate "67" // Maximum updates per second that the server will allow. Sv_minrate "13000" // Min bandwidth rate allowed on server Sv_maxrate "25000" // Max bandwidth rate allowed on server The server has had these settings since about when we moved servers: (copy/pasted right from our cfg file) ![]() You're treading on some old ground Magoo. If someone comes into the server with a 600 ping can I ban them? Admins could act as manual ping checkers while we are on the server. I have seen people in the server with 1-5 ping because they are ping masking by altering these values and I have also heard the Captain yell at people that we do not allow people to ping mask in our servers. The server caps would override any auto cfg settings that you might have. The way the server is configured we should all be using 67 for those two later values and if you have garbage internet you should still be able to use rate 25000. The change would be on the minimum rate cap, cmdrate value, and updaterate value. So even if your auto cfg file tells the server to use 60000 for you because you have super fast internet it will cap you at 30000. There is a maximum set because of server bandwidth limitations. It was causing the server to crash.Įveryone is already subject to a rate cap that is somewhere around 30000. The ping checker was removed from the server last I heard.
0 Comments
Leave a Reply. |