Team Fortress 2 Server Settings Explained

A TF2 server is configured in two places: the launch line, read once at start, and server.cfg, run at every map load. Here is what goes where.

The launch line

The server name, the passwords, the player limit, the Steam token and the starting map are launch-line settings. On Flux they are fields in Deployment Settings, and the Server Settings tab keeps them out of server.cfg, where they would otherwise override the form.

server.cfg

SettingDefaultWhat it does
mp_timelimit0 (30 on Flux)Minutes per map before the next one in the cycle
mp_maxrounds / mp_winlimit0Rounds or wins per map; 0 for no limit
tf_weapon_criticals1Random critical hits; competitive servers turn them off
tf_damage_disablespread1Fixed damage instead of a random ±10%
tf_use_fixed_weaponspreads0Same shotgun pattern every time
mp_disable_respawn_times0Instant respawn
mp_autoteambalance1Evens out the teams
tf_bot_quota0Bots filling the server
sv_alltalk0Everyone hears everyone on voice
sv_pure0Whether players may use custom models and sounds
sv_downloadurl(empty)A FastDL web server for custom maps
Tip:On Flux, server.cfg lives in custom/flux/cfg on your server's own storage: TF2 reads every folder in tf/custom as part of the game. The Server Settings tab is that file as a form, and saving runs it at once.

Frequently asked questions

How do I turn off random crits?

Set tf_weapon_criticals 0 in server.cfg; on Flux it is Random Crits in the Server Settings tab.

Where is server.cfg?

In tf/cfg on a plain install. On Flux it is custom/flux/cfg/server.cfg, which the game reads the same way, edited from the Server Settings tab.

Related Team Fortress 2 guides