Installing SourceMod Plugins on a CS:GO Server

If vanilla Counter-Strike: Global Offensive starts feeling a bit flat, plugins are the usual cure. With SourceMod and MetaMod loaded on the server, you can adjust everything from join sounds to full gameplay overhauls. The install process trips up players more often than it should, so this walkthrough sticks to the steps that actually matter.

Finding the Plugin You Want

SourceMod hosts a public directory of community plugins, and most of what you need will live there.

1. Open the SourceMod plugins listing.
2. Use the search bar near the top to narrow results by name or feature.
3. Click any result to open its detail page.
4. Look for the Get Plugin button or a direct download link near the bottom.
5. Save the `.smx` file somewhere you will not forget about five minutes later.

If a plugin ships with extra config files or gamedata, grab those too. They usually live in the same archive.

Uploading and Activating the Plugin

Before you upload anything, confirm that both SourceMod and MetaMod are already installed on the server. Plugins will not load without them, no matter how cleanly you drop the files in.

1. Open your HolyHosting control panel and stop the server.
2. Connect through the FTP file manager.
3. Browse to `csgo/addons/sourcemod/`.
4. Open the `plugins` folder, or create it if it is missing.
5. Click Upload and drop your `.smx` files inside.
6. Wait until each file reaches 100%, then start the server back up.

When the server boots, the plugin should load automatically alongside SourceMod.

Troubleshooting

Plugin is not showing up in-game. The most common cause is the file landing in the wrong directory. The `.smx` itself must sit directly inside `csgo/addons/sourcemod/plugins`. Subfolders and other paths are ignored by the loader.

The expected folder is not in the FTP. That structure only appears after SourceMod and MetaMod have been correctly installed. If `csgo/addons/sourcemod` is missing entirely, revisit the SourceMod and MetaMod setup guide first, then come back to this one.

Once the file is in the right place, the rest is on the plugin itself to behave.