To install mods on a Team Fortress 2 server, run a dedicated TF2 server, add MetaMod:Source, add SourceMod, then place each compiled .smx plugin in tf/addons/sourcemod/plugins. Restart the server and verify the frameworks with meta list and sm version in the server console before testing a plugin. This is the reliable answer to “How do I install mods on a TF2 server?”, “How do I install SourceMod and MetaMod on my TF2 server?”, “Where do I put a TF2 .smx plugin?”, and “How do I know SourceMod loaded?”
The steps below apply to a dedicated server managed from your own machine or through a hosting panel. Dedicated instances are preferable to listen servers because their loading behavior and file layout are more predictable.
What do you need before installing TF2 mods?
You need a working dedicated Team Fortress 2 server, access to its files, and a way to restart it. The installation is a dependency chain: MetaMod:Source loads first, SourceMod loads through MetaMod:Source, and SourceMod then loads TF2-compatible plugins.
- A dedicated TF2 installation: Valve identifies the dedicated-server AppID as
232250. Its game/mod directory is namedtf. - SteamCMD: Valve’s command-line client installs and updates dedicated game servers.
- File access: You need shell or FTP access on a self-hosted machine, or a file manager on a managed panel.
- Restart access: Frameworks and plugins are not reliably loaded until the server has been fully restarted.
- Compatible packages: Use a MetaMod:Source build for your operating system, the current SourceMod release recommended by its documentation, and plugins explicitly made for Team Fortress 2.
SourceMod requires MetaMod:Source 1.9.0 or newer; using the latest available compatible build is recommended. Keep a backup of the tf directory, especially tf/addons and tf/cfg, before changing a live server.
How do I install or update the dedicated TF2 server with SteamCMD?
Install or update the dedicated files first. Framework archives belong inside the TF2 game directory, so a correct server installation is the foundation for every later step.
- Install SteamCMD on the server machine and create a directory for the TF2 dedicated server.
- Run SteamCMD and log in anonymously:
steamcmd +login anonymous +app_update 232250 validate +quit- Point the command at the directory where you want the server files installed. If the files are already present, the same AppID updates them.
- Confirm that the resulting installation contains the
tfdirectory. Do not extract MetaMod:Source or SourceMod besidetf; their files must merge into the TF2 directory itself. - Start the dedicated server once, then stop it cleanly. This creates any baseline files needed by the server and confirms that SteamCMD installed the expected content.
The exact launch parameters for maps, ports, and server configuration depend on your operating system and hosting setup. They are separate from the mod installation; do not troubleshoot plugin loading until the unmodified dedicated server starts normally.
How do I install MetaMod:Source on a TF2 server?
Install MetaMod:Source before SourceMod. MetaMod:Source is the middleware that allows SourceMod to load, so SourceMod cannot function when MetaMod is missing or placed in the wrong directory.
- Download the MetaMod:Source archive that matches the server platform.
- Open the archive and copy its contents into the TF2 game directory, the directory containing
tf. - Merge the archive’s
addonsdirectory with the existingtf/addonsdirectory. Avoid creating an accidental nested path such astf/tf/addons. - For TF2, make sure the loader file
tf/addons/metamod.vdfexists. If the package does not include a TF2-specific VDF, generate or install the TF2 VDF supplied by the MetaMod instructions for your platform. - Leave the server stopped until SourceMod is copied as well, or restart after this step if you want to test MetaMod independently.
A successful MetaMod installation normally creates a directory resembling tf/addons/metamod and places the VDF directly in tf/addons. The VDF is a loader, not a plugin; moving it into the metamod subdirectory prevents the game from finding it.
How do I install SourceMod?
Extract the SourceMod archive into the same TF2 directory and merge its addons and cfg folders. On a remote server, upload the archive contents with FTP or the provider’s file manager rather than uploading the archive as an inert file.
- Download the SourceMod package for the server platform.
- Extract it locally and open the folder that contains the package’s
addonsandcfgdirectories. - Copy those directories into the TF2 installation so that the resulting paths include
tf/addons/sourcemodandtf/cfg. - When prompted, merge folders. Do not replace the entire
tfdirectory with an archive folder. - Check the final layout before restarting:
| Purpose | Expected location |
|---|---|
| MetaMod:Source loader | tf/addons/metamod.vdf |
| MetaMod:Source files | tf/addons/metamod |
| SourceMod files | tf/addons/sourcemod |
| SourceMod configuration | tf/cfg |
| Compiled server plugins | tf/addons/sourcemod/plugins |
The most common upload error is an extra directory level, for example tf/addons/sourcemod/sourcemod. Open the folder and verify that files such as the SourceMod binaries are immediately inside the expected sourcemod tree.
How do I know MetaMod and SourceMod loaded?
Restart the dedicated server completely, then use the server console to run meta list and sm version. These commands test the frameworks before you add third-party plugins.
- Stop the server through its service manager or hosting panel.
- Start it again and wait until the console reports that the server is ready.
- Run
meta list. MetaMod should answer with its status and loaded components rather than an unknown-command error. - Run
sm version. SourceMod should print its version and build information. - If both commands work, change the map or perform one additional restart before installing a large group of plugins. This catches files that only become active during a full load.
If meta list is unknown, check the VDF location, platform package, and server path first. If MetaMod works but sm version is unknown, check that SourceMod was merged into tf and that its dependency is a compatible MetaMod:Source build.
Where do I put a TF2 .smx plugin?
Put the compiled plugin file in tf/addons/sourcemod/plugins. A .smx file is the server-loadable output; do not place it in the top-level tf directory, the MetaMod folder, or the configuration directory.
- Download a plugin identified by its author as compatible with Team Fortress 2.
- Extract the download on your computer. Many downloads contain documentation, translations, configuration files, and dependencies in addition to the compiled plugin.
- Copy the plugin’s
.smxfile intotf/addons/sourcemod/plugins. - Copy any supplied translation files into the plugin’s documented translations directory and any configuration files into the locations specified by that plugin. Do not guess when the package includes its own instructions.
- Restart the server or change the map, then run
sm plugins listin the server console.
Install one plugin at a time. If several are added together and one fails, you cannot tell which file, dependency, or configuration caused the problem. Keep the original archive and record the version you installed so you can remove or restore it cleanly.
How do I configure and test a newly installed plugin?
Use the plugin’s own documentation for commands and settings, then test from the server console and in-game. SourceMod can confirm that a file was discovered, but a plugin may still report an error when a required dependency or game-data file is missing.
Check the load state
Run sm plugins list. Look for the plugin name and a running or loaded state. If the list marks it as failed, note the reason printed beside it before changing files.
Check dependencies
Some plugins require another SourceMod extension, a particular library, gamedata, or translation files. Install those prerequisites exactly as documented, then restart and test again. A plugin built for another Source engine game may appear in the directory but still fail because its commands or game data do not match TF2.
Check configuration files
Plugin-specific configuration commonly belongs under tf/cfg/sourcemod when the plugin supplies a configuration file. Edit one setting at a time, preserve the file encoding and syntax, and restart or change the map when the documentation says the setting is read.
Test in a controlled session
Join the server as an administrator, run the plugin’s documented command, and test the feature on an empty or private server before exposing it to players. Check the console after a map change as well as immediately after startup; some plugins initialize only when a map begins.
Should I self-host TF2 mods or use a managed panel?
Both approaches use the same directory structure and framework order. Self-hosting gives you complete control; a managed panel reduces operating-system work but may limit file access, restart options, or update timing.
| Consideration | Self-hosted dedicated server | Managed panel |
|---|---|---|
| File access | Shell, FTP, and direct filesystem control | File manager or FTP exposed by the provider |
| Installation | You run SteamCMD and extract both framework archives | You upload archives or use a modding-addons switch when offered |
| Restarts | You control the service, scripts, and restart schedule | The panel supplies stop, start, and restart controls |
| Updates | You monitor Steam updates and framework releases | The provider may handle server updates, but plugin compatibility remains your responsibility |
| Backups | You choose the backup location and retention | Backup tools and retention vary by provider; verify them before modifying files |
| FastDL and downloads | You configure distribution and bandwidth yourself | Some TF2 hosts advertise FastDL or optimized downloads; confirm what is included |
| Support | You diagnose paths, permissions, and crashes | Support may help with the panel and base server, but not every third-party plugin |
On a panel, a typical documented route is 232250 → tf → addons → sourcemod → plugins: open the TF2 instance, enter tf, open the SourceMod plugins directory, upload the .smx, and restart. Another common panel design exposes an “Enable Modding Addons” switch that installs the frameworks, while still allowing manual archive uploads. The labels differ, so confirm that the selected instance is the TF2 AppID 232250.
Choose self-hosting when you need shell automation, custom backups, or unrestricted access to binaries and configuration. Choose a managed panel when predictable restarts and a graphical file manager matter more than low-level control. In either case, verify that the plan permits custom SourceMod plugins and that you can restore the tf directory.
What should I do when a TF2 mod does not load?
Start with the first failed layer in the dependency chain. Do not reinstall every component at once; isolate the failure so you preserve a useful error message.
meta list is an unknown command
- Confirm that the server is a dedicated instance, not a client-side listen session.
- Check that
tf/addons/metamod.vdfexists and is not inside another directory. - Confirm that you extracted the package for the server’s operating system.
- Verify that the server actually starts from the TF2 directory you edited.
- Perform a complete stop and start rather than only changing a configuration value.
MetaMod loads but SourceMod does not
- Confirm that
tf/addons/sourcemodexists at the same level astf/addons/metamod. - Check the MetaMod:Source version. SourceMod requires 1.9.0 or higher, with the latest compatible release recommended.
- Look for a second, nested
sourcemoddirectory caused by extracting the archive one level too high. - Run
sm versionagain after a full restart.
The plugin appears but is marked failed
- Read the error shown by
sm plugins listand the server console. - Install the plugin’s required dependencies, gamedata, and translations.
- Confirm that the plugin targets Team Fortress 2 rather than a different Source game.
- Move the plugin out of the directory, restart, and re-add it after correcting one issue at a time.
The plugin worked until a TF2 update
Game updates can invalidate SourceMod or plugin gamedata. Update MetaMod:Source and SourceMod first; after a major release, AlliedModders may require a snapshot build until a stable release catches up. Keep a known-good backup and disable broken plugins rather than repeatedly restarting a live public server with the same failing binary.
How do I keep a modded TF2 server maintainable?
Treat framework files, plugins, and configuration as separate change groups. This makes updates reversible and limits downtime.
- Back up before every change: Save
tf/addons,tf/cfg, and plugin-specific data with a date in the backup name. - Record versions: Note the MetaMod:Source build, SourceMod build, plugin filename, and installation date.
- Update in order: Update the dedicated server, then verify MetaMod, then verify SourceMod, then test plugins individually.
- Use a staging instance: Test game updates and new plugins on a private server before applying them to a public one.
- Keep a rollback path: Preserve the previous framework archives and plugin files until the new versions have survived a map change and a normal restart.
- Review logs: Console errors often identify a missing dependency or incompatible gamedata file faster than repeated uploads do.
Following this order prevents a plugin problem from being mistaken for a SteamCMD problem and gives you a clear recovery step when Valve updates the game.
Frequently Asked Questions
Can I install SourceMod without MetaMod:Source?
No. SourceMod loads through MetaMod:Source, so SourceMod files alone will not provide a working framework. Install and verify MetaMod first, then add SourceMod.
Do players need to download a SourceMod plugin?
The server-side framework and most administrative plugins remain on the server. Players may still need custom maps, sounds, models, or other downloadable assets when a particular plugin uses them; follow that plugin’s distribution instructions.
Why does a plugin load on one TF2 server but not another?
The servers may be running different game updates, framework builds, operating systems, or dependency sets. Compare the output of meta list, sm version, and sm plugins list, then check the plugin’s required gamedata and extensions.
What is the safest way to remove a broken plugin?
Stop the server, move the plugin’s .smx file out of tf/addons/sourcemod/plugins, and restart. Keep its configuration and dependency files until you confirm that no other plugin uses them; restore the file from your backup if the failure was unrelated.