Skip to content

TF2 Mods and SourceMod Plugins: How to Install Them on Your Server

Which TF2 mods run on a server and which stay on your PC: install MetaMod:Source and SourceMod, add plugins and extensions, switch on the bundled map vote, and set sv_pure for client mods.

Updated October 28, 2026
Team Fortress 2

"TF2 mods" means two different things, and only one of them goes on a server. Client mods are custom HUDs, skins, and model or sound replacements, and they live on each player's own PC. Server mods are SourceMod plugins, MetaMod:Source plugins and custom maps, and they run on your server for everyone who joins. This guide covers the server side: installing MetaMod:Source and SourceMod, adding plugins and extensions, switching on the map vote that SourceMod already ships, and the one setting, sv_pure, that decides whether your players' client mods load on your server.

Complete Getting started with your Team Fortress 2 server first.

Client Mods or Server Mods?

Client mods Server mods
Examples Custom HUDs, skins, model and sound replacements SourceMod plugins, Stripper:Source, custom game modes, custom maps
Installed on Each player's own PC Your server, inside tf/
Who sees the effect That player only Everyone on the server
What the server controls Whether they may load, through sv_pure Everything

You cannot push a HUD or a skin onto your players from the server, and a player cannot add a server plugin by dropping it into their own game folder. Custom maps sit in between: they run on the server and download to players when they join, which is covered in Custom Maps and FastDL.

SourceMod and MetaMod:Source

SourceMod is the plugin platform almost every TF2 server mod is written for: admin menus, map votes, custom game modes and thousands of community plugins. It needs MetaMod:Source underneath it. MetaMod hooks into the Source engine, and SourceMod builds the plugin system on top.

Use the 1.12 stable build of both. SourceMod's 1.12 release announcement lists "greatly improved 64-bit support" and says that support "may soon be a requirement for Team Fortress 2 servers". MetaMod:Source declared 1.12 its stable branch in March 2025.

Step 1: Upload MetaMod:Source, then SourceMod

There is no startup variable to set. Both are plain file drops into the game folder, which is tf/ on a managed Team Fortress 2 server, and nothing needs to change on the launch command. Upload with the panel's File Manager, or over SFTP if you are moving a lot of files.

  1. Download the current stable MetaMod:Source build for Linux and extract it locally.
  2. Upload the extracted contents into tf/. You should end up with tf/addons/metamod/ and tf/addons/metamod.vdf.
  3. Download the current stable SourceMod build for Linux, extract it, and upload its contents into tf/ as well. That adds tf/addons/sourcemod/, tf/addons/metamod/sourcemod.vdf and tf/cfg/sourcemod/.
  4. Restart the server.

Extract before you upload

AlliedModders are explicit about this: "If you are uploading to FTP, extract the files locally before transferring to your server's game folder." Uploading the archive itself and trying to unpack it on the server is the usual way this goes wrong.

You do not need to edit gameinfo.txt

MetaMod:Source 1.10.0 and later ship a metamod.vdf that loads it as a Valve Server Plugin automatically. The gameinfo.txt edit some older guides describe is, in AlliedModders' own words, something you "really, really do not need to do".

Step 2: Verify

After boot, run from the console:

meta version
sm version
text

Both should respond with their version strings. meta version should report Loaded As: Valve Server Plugin. If you get Unknown command: sm version, SourceMod did not load. Work through meta list first, as described under Common Issues below.

Step 3: Add Admins

Edit tf/addons/sourcemod/configs/admins_simple.ini and add one line per admin:

"STEAM_0:0:11101" "99:z"
tf/addons/sourcemod/configs/admins_simple.ini

The format is "<SteamID>" "[immunity:]<flags>". 99:z is immunity level 99 with the z flag, which the AlliedModders documentation describes as enabling all flags and ignoring immunity. Then reload the admin list without restarting:

sm_reloadadmins
text

The server answers [SM] Admin cache has been refreshed. Every flag letter, and how to give a moderator kick and ban without root, is in TF2 Server Commands.

Step 4: Use the Admin Commands

Connect in-game and type the commands in chat. ! runs the command and shows the reply to everyone, / runs it silently, and from the console you use the full sm_ name:

!admin                            Open the admin menu
!kick <player> <reason>           Kick
!ban <player> <minutes> <reason>  Ban
!slap <player> <damage>           Slap a player
!slay <player>                    Kill a player
!map <mapname>                    Change map
text

!nominate and !rtv are not on that list because their plugins ship switched off. The next section turns them on.

Turning On the Map Vote That Ships With SourceMod

SourceMod's own build script packages seven of its plugins into addons/sourcemod/plugins/disabled/ rather than plugins/: mapchooser, nominations, rockthevote and randomcycle, plus the three SQL admin plugins. The AlliedModders wiki is plain about that folder: "Plugins in this sub-folder won't be loaded." Those first three are the end-of-map vote, !nominate and !rtv.

To turn them on, move the .smx files up one level and load them:

  1. In the File Manager, move mapchooser.smx, nominations.smx and rockthevote.smx from tf/addons/sourcemod/plugins/disabled/ to tf/addons/sourcemod/plugins/.
  2. Load them from the console, or just change the map:
sm plugins load mapchooser
sm plugins load nominations
sm plugins load rockthevote
sm plugins list
text

sm plugins list should now show all three. Moving a plugin the other way, into disabled/, is how you switch one off, such as funvotes.

Installing Plugins and Extensions

SourceMod loads two kinds of add-on, and they go in different folders.

Plugin Extension
File .smx (compiled), with .sp source .ext.so on a Linux server
Folder tf/addons/sourcemod/plugins/ tf/addons/sourcemod/extensions/
Loads Automatically when SourceMod starts When a plugin requires it, or with an .autoload file
Load by hand sm plugins load <name> sm exts load <name>

For a plugin:

  1. Download the compiled .smx. Most are posted in their thread on the AlliedModders forums (forums.alliedmods.net) or in a GitHub repository.
  2. Upload it to tf/addons/sourcemod/plugins/. If the download is a zip laid out as addons/sourcemod/..., upload the whole tree, because larger plugins also bring translations/ and gamedata/ files that have to land in the matching folders.
  3. Change the map, or run sm plugins refresh. SourceMod also reloads a plugin on map change when its file has changed.
  4. Run sm plugins list and check it is there. A missing plugin almost always means the .smx is not directly in plugins/.

Plugin configs only appear after the first load

Many plugins generate config files in tf/cfg/sourcemod/ on first load. Edit those after the first boot, then reload the plugin.

Some plugins ship only as source (.sp) and must be compiled first, with the web compiler on sourcemod.net or a local spcomp. Most popular plugins offer a precompiled .smx download.

Stop the server before replacing an extension

AlliedModders warn that you cannot update a running extension. Unload it or stop the server first, because on Linux overwriting a loaded extension will most likely crash the server.

Plugins and Extensions Worth Knowing

Name Type What it does
TF2Items Extension "Items with custom attributes": lets plugins hand out modified weapons. Custom loadout and boss modes depend on it
TF2Attributes Plugin, with a gamedata file Adds and changes item attributes. Ships as tf2attributes.smx plus gamedata/tf2.attributes.txt, and is often paired with TF2Items
SteamWorks Extension Exposes Steam functions to plugins. Install it when a plugin lists it as a dependency
Advertisements Plugin Timed server messages (rules, a Discord link, tips) read from addons/sourcemod/configs/advertisements.txt, shown as chat, centre, hint, menu or top messages
Stripper:Source MetaMod:Source plugin Filters and adds map entities before a map loads, without editing the .bsp. Rules go in addons/stripper/global_filters.cfg for every map, or addons/stripper/maps/<map>.cfg for one
MapChooser Extended Plugin set Extended versions of the map vote, nominations and RTV. Its GitHub repository has been archived since 2021, so start with the bundled plugins above and add it only if you need its extra features

Stripper:Source is a MetaMod:Source plugin, not a SourceMod one. It is extracted into tf/ and lives under tf/addons/stripper/, and it does not appear in sm plugins list. Check it with meta list instead.

Leave the extension-heavy plugins out until you need them

Add TF2Items, TF2Attributes and Stripper:Source only if you plan to run custom loadouts or modes. TF2Items and TF2Attributes ship their own gamedata files, and the AlliedModders wiki notes that gamedata can change whenever Valve releases an update. Fewer of them means fewer things to wait on after a patch.

Custom Game Modes

Most custom TF2 modes, such as Versus Saxton Hale, Freak Fortress 2, MGE and DeathRun, are SourceMod plugin packs installed with the steps above, usually on top of TF2Items and TF2Attributes. Each mode, its dependencies and its config files are covered in Team Fortress 2 Gamemodes.

Client Mods and sv_pure

You do not install client mods, but your server decides whether they work on it. That is sv_pure, and it matters for fairness as well as looks: the official TF2 wiki points out that modified client files can do things like brighten enemy skins or make walls see-through, and that "VAC doesn't protect against these kinds of exploits because they don't modify the game process itself."

sv_pure What it does to client mods on your server
-1 No purity or consistency checks at all
0 The default. Only the rules in cfg/pure_server_minimal.txt apply
1 Applies cfg/pure_server_full.txt, then your cfg/pure_server_whitelist.txt
2 Forces Steam content only: no custom skins, models or sprays. HUD layouts, sounds and some visual effects are still allowed

sv_pure 1 with a whitelist is the middle ground. The Valve Developer Community gives Valve's own casual TF2 servers as the example, where "users can use custom view model animations and HUDs, but not models, materials, or sounds." By default a pure server kicks a client whose files break the rules. Set sv_pure_kick_clients 0 to warn instead.

For a casual or community server where players want their custom skins, sv_pure 0 is the usual choice, and Team Fortress 2 Gamemodes uses it for trade servers. For anything competitive, use 1 or 2.

Common Issues

  • Plugins not loading: look at tf/addons/sourcemod/logs/errors_*.log for compile or runtime errors. The log names the plugin and the failure.
  • "sm version" unknown after installing SourceMod: run meta list and read the answer. No reply at all means MetaMod:Source is not installed. Listing 0 plugins means sourcemod.vdf is missing from tf/addons/metamod/. A <NOFILE> or FAILED entry means the files are in the wrong place or could not load. Check they landed under tf/addons/, not the server root.
  • !rtv or !nominate does nothing: those plugins are still in plugins/disabled/. Move them up as described above.
  • Plugin requires an extension that is missing: install the dependency (often SteamWorks or TF2Items) before the plugin that needs it.
  • A mode or loadout plugin broke after a TF2 update: community plugins and their gamedata lag behind game updates. Check the plugin's thread or repository for a new build.
  • Admin commands do nothing: your SteamID in admins_simple.ini is wrong or formatted incorrectly. Check the line against the example above and run sm_reloadadmins.
  • Players' custom skins don't show: sv_pure is 1 or 2. That is the setting working as intended. Lower it only if you are happy with the trade-off above.

FAQ

Can I use TF2 mods on Valve's casual servers?

Only the kinds Valve allows. The Valve Developer Community gives the casual servers' rule as custom HUDs and view model animations allowed, but not models, materials or sounds. On your own server, sv_pure sets that rule.

Do my players need to install anything for server mods?

No. SourceMod plugins run on the server only. Custom maps and their files download to players when they join, and FastDL is how you make that download fast.

What is the difference between SourceMod and MetaMod:Source?

MetaMod:Source is the loader that hooks into the game. SourceMod is a MetaMod plugin that provides the plugin system, admin system and commands. You need both for SourceMod plugins, and MetaMod alone for MetaMod plugins such as Stripper:Source.

Sources


Made with 💜 by GameServerKings

Need a Team Fortress 2 server?

Deploy an instantly-provisioned Team Fortress 2 server on high-clock hardware. DDoS protected, no contracts, cancel anytime.

From $5.40 /month