Installing metamod:source

From AlliedModders Wiki
Jump to: navigation, search

This article will guide you through a Metamod:Source installation.

Normal Installation

Not applicable for Source 2. See GameInfo section below

Valve sometimes makes changes in their games that break Metamod:Source between releases. When this happens, you may need to install a snapshot versions of Metamod:Source. You can see if this is required on the Required Versions page.

  1. Download Metamod:Source.
  2. Extract the package to your game folder. For example, for Counter-Strike:Source, you would have cstrike/addons/metamod after extracting. If you are uploading to FTP, extract the files locally before transferring to your server's game folder.
  3. Restart your server.
  4. Type "meta version" in your server console (or RCon). You should see a line like: "Loaded As: Valve Server Plugin." If the command is not recognized, see the sections below.

When using a Linux server, you may see the following messages:

  • An error indicating that it could not be loaded due to "wrong ELF class: ELFCLASS64". If you are using a 32-bit dedicated server installation, this is normal behavior; as long as meta version is recognized, Metamod:Source is installed.
  • An error indicating that it could not be loaded because "/path/to/server_install/bin/ version `GCC_7.0.0` not found (required by /some_system_path_to/". This is because Valve ships their own copies of those libraries. As modern systems will have newer versions, you can safely delete the listed file from the server install. Do not delete the file in the system path (usually lib or lib32).
  • If you are running a 64-bit operating system yourself, you may need to install the system's 32-bit libraries.
    • On Debian / Ubuntu, you can do this with apt install gcc-multilib.
  • You may find more information about any load failures under a metamod-fatal.log in metamod's bin folder.

Custom VDF File

Note: This is normally not needed - Metamod:Source 1.10.0 and later include a metamod.vdf file for easier installation on most games.

If you have trouble getting it to load, go here to generate a VDF file specific to your game. This file should be placed into your server's addons directory.

Known setups that require this step:

  1. Left 4 Dead 1
  2. 3rd party mods using the Source SDK Base.
  3. Listen servers (created with the in-game "Create Server" option) for non-english game clients.


Note: On Source 1, this is normally not needed - if you do not understand what this is, do NOT do this unless instructed to. The above instructions are sufficient to install Metamod:Source for 99% of servers. For Source 2, this is, however, the only supported loading method.

Metamod:Source 1.4.2 and lower used an older method for loading itself. The advantage of this method was that Metamod:Source could be loaded before the actual game mod, which gave it a small amount of extra functionality. This functionality was never used by plugin developers, and Steam updates kept overwriting gameinfo files, so we switched to a different loading mechanism.

However this loading mechanism may still be desirable if you run into backwards compatibility issues, or you have a plugin which takes advantage of the early-loading mechanism. If this is your case, here are the gameinfo directions below:

  • Open the file in the mod folder called "gameinfo.txt" (Source 1) or "" (Source 2). You will see a few lines at the bottom like this:
    	Game				|gameinfo_path|. 
    	Game				cstrike
    	Game				hl2
  • Add a line after the "{" sign but before all of the "Game" entries that looks like this:
    GameBin				|gameinfo_path|addons/metamod/bin
  • If you're using Windows, you may need to use a backwards slash (\) instead.
  • You're done! To test whether it worked, restart your game server and type "meta version" in the server console. You should see a line that says "Loaded as: GameDLL (gameinfo.txt)." If it doesn't recognize the command, the installation probably failed. If the "Loaded as:" line says something else, gameinfo was probably not modified correctly.
  • For more information or documentation, see Category:Metamod:Source Documentation