There are literally hundreds of possible variables in srcds, many of which have no effect on a TF2 server.To simplify this guide I’ll provide you with a very simple sample server config file and talk about some of the more important variables. // General server settings hostname "Payload/Control-Point Rotation [Fremont, CA]" rcon_password "myunguessablepassword" sv_password "" sv_lan 0 sv_region 1 // game settings mp_timelimit 30 mp_maxrounds 4 mp_winlimit 0 // voice settings sv_voiceenable 1 sv_alltalk 0 // bandwidth rates/settings sv_allowupload 1 sv_allowdownload 1 sv_minrate 10000 sv_maxrate 0 sv_maxupdaterate 100 sv_minupdaterate 66 sv_mincmdrate 66 sv_maxcmdrate 100 // run in pure mode sv_pure 1 sv_pure_kick_clients 1 My server config is significantly more complicated than that, but trying to mention every possible variable that you can tinker with would be a huge article unto itself!Generally, players use voice chat for tactical information, so set this to 0 unless you have a good reason.
The big one is the file located in the orangebox/tf/cfg folder.
This file is where you set all of the server variables that control how your server runs.
This doesn’t count in the tie-breaker or sudden death round (which defaults to 2 minutes long).
The maximum number of that one team can win before the server changes maps.
Most of these variables are pretty self-explanatory. These are easily confused and mean different things in different types of maps.
They are also the ones that new admins are most likely to screw up.
This simple little tool will handle the download and installation of your base Source Dedicated Server.
The first step in this process is to get the hldsupdatetool. It will present you with a license agreement, type “yes” and hit enter to proceed. Now we have to run the steam client, which will check to see if it is currently up to date and download a whole bunch of updates. The dot after the -dir flag tells it to install the game server based in the current directory.
This isn’t at all required, but it is good practice.
The standard practice seems to be creating and account called “hlds” and using that account to run the process.
They build a version for Windows, Linux and Mac so you can run it on whatever system you happen to have available.