Team Fortress 2 is a Source engine server, so its settings are console variables written into a config file the server executes at startup.
Where the files live
In the panel open Files and go to:
tf/cfg/
server.cfg, executed on every map change. This is where your settings go.mapcycle.txt, the list of maps played in order.motd.txtandmotd_text.txt, the message shown to joining players.
server.cfg
hostname "My PlayNHost TF2 Server"
sv_contact "[email protected]"
rcon_password "a-long-password-here"
sv_password ""
sv_lan 0
sv_region 3
mp_timelimit 30
mp_winlimit 5
mp_maxrounds 5
sv_alltalk 0
sv_pure 1
sv_allow_votes 1
mp_autoteambalance 1
mp_teams_unbalance_limit 1
sv_setsteamaccount "YOUR_GSLT_TOKEN"
hostnameis the name in the browser.sv_passwordempty is an open server. Setting it makes the server private.rcon_passwordgives full remote control. Make it long and never share it.mp_timelimitis in minutes, and is what decides how long a map lasts.sv_pure 1stops clients using custom content that changes gameplay visuals.sv_setsteamaccountis your Steam game server login token, which the server needs to be listed publicly. See the troubleshooting guide for how to create one.
The map cycle
Edit tf/cfg/mapcycle.txt, one map name per line, no file extension:
ctf_2fort
cp_dustbowl
pl_upward
koth_viaduct
pl_badwater
The server plays them in order and loops. To start on a specific map, set it on your server's Startup Settings page, reachable from the server overview, or change it live from the panel console:
changelevel pl_upward
Slots
Your plan's slot count is applied through the MAX_PLAYERS variable on your server's Startup Settings page. Note that TF2 counts spectator and bot slots against the same total. Upgrade the plan in the billing area to run more players.
Apply the changes
Save the file and either restart the server or, from the panel console, run:
exec server.cfg
Some variables only take effect on a map change, so a changelevel is the safest way to confirm a setting has applied.





