Team Fortress 2 settings, map changes and troubleshooting

Team Fortress 2 settings are split between Startup and files such as tf/cfg/server.cfg. Our startup script writes the server name, join password and RCON password from the panel, so edit those three values in Startup.

Make a controlled change

1. Open your service in the Game Server Control Panel. Tell players about the interruption, stop the server cleanly, and create a backup.
2. Use Startup → Default Map for the map loaded at startup. An installed standard map such as ctf_2fort is a sensible baseline when testing a problem.
3. For other gameplay settings, use Files → tf → cfg → server.cfg. Keep the previous file and change one setting at a time. Avoid duplicate commands that fight with the panel-managed values.
4. Save, start, and join. After a later map change, verify that the setting still behaves as intended.

Passwords and administration

The Server Password controls player access. The Admin (RCON) Password permits remote administration and must not be shared with ordinary players. Leave RCON disabled unless you need it; if enabled, use a private, unique password. A Steam game-server login token is another private credential, not a player password.

Common checks

• The name or password changes back: save it in Startup instead of editing the generated line in server.cfg.
• A custom map will not load: return to the previous installed map and check the filename and required files.
• Client/server version mismatch: let Steam finish updating the client, then ask support to check the server version.
• Only public search fails: compare with Favorites or direct connection before changing configuration.

Keep the allocated game, client and SourceTV ports unchanged. For unresolved issues, open a support ticket and choose Game Servers with the map, error and recent changes. Do not reinstall or replace the whole configuration merely to clear an error.

Browse all game-server guides