Difference between revisions of "Installing Metamod:Source"
(→Normal Installation: more setps) |
(Change tt to code and rlaborate where metamod-fatal.log can be found) |
||
| Line 7: | Line 7: | ||
<ol> | <ol> | ||
<li>[http://www.metamodsource.net/ Download] Metamod:Source.</li> | <li>[http://www.metamodsource.net/ Download] Metamod:Source.</li> | ||
| − | <li>Extract the package to your game folder. For example, for Counter-Strike:Source, you would have < | + | <li>Extract the package to your game folder. For example, for Counter-Strike:Source, you would have <code>cstrike/addons/metamod</code> after extracting. If you are uploading to FTP, extract the files locally before transferring to your server's game folder.</li> |
<li>Restart your server.</li> | <li>Restart your server.</li> | ||
<li>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.</li> | <li>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.</li> | ||
| Line 14: | Line 14: | ||
When using a Linux server, you may see the following messages: | 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 < | + | * 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 <code>meta version</code> is recognized, Metamod:Source is installed. |
| − | * An error indicating that it could not be loaded because "/path/to/server_install/bin/libgcc_s.so.1: version `GCC_7.0.0` not found (required by /some_system_path_to/libstdc++.so.6". 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 < | + | * An error indicating that it could not be loaded because "/path/to/server_install/bin/libgcc_s.so.1: version `GCC_7.0.0` not found (required by /some_system_path_to/libstdc++.so.6". 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 <code>lib</code> or <code>lib32</code>). |
* If you are running a 64-bit operating system yourself, you may need to install the system's 32-bit libraries. | * 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 < | + | ** On Debian / Ubuntu, you can do this with <code>apt install gcc-multilib</code>. |
| − | * You may find more information about any load failures under a < | + | * You may find more information about any load failures under a <code>metamod-fatal.log</code> in metamod's <code>bin</code> folder. |
==Custom VDF File== | ==Custom VDF File== | ||
| − | '''Note: This is normally not needed - Metamod:Source 1.10.0 and later include a < | + | '''Note: This is normally not needed - Metamod:Source 1.10.0 and later include a <code>metamod.vdf</code> file for easier installation on most games.''' |
| − | If you have trouble getting it to load, [http://www.metamodsource.net/?go=vdf go here] to generate a VDF file specific to your game. This file should be placed into your server's < | + | If you have trouble getting it to load, [http://www.metamodsource.net/?go=vdf go here] to generate a VDF file specific to your game. This file should be placed into your server's <code>addons</code> directory. |
Known setups that require this step: | Known setups that require this step: | ||
| Line 35: | Line 35: | ||
'''Note: 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.''' | '''Note: 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.''' | ||
| − | 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 < | + | 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 <code>gameinfo.txt</code> 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 < | + | 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 <code>gameinfo.txt</code> directions below: |
<ul> | <ul> | ||
| Line 53: | Line 53: | ||
</li> | </li> | ||
<li>If you're using Windows, you may need to use a backwards slash (\) instead. | <li>If you're using Windows, you may need to use a backwards slash (\) instead. | ||
| − | <li>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, < | + | <li>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, <code>gameinfo.txt</code> was probably not modified correctly.</li> |
<li>For more information or documentation, see [[:Category:Metamod:Source Documentation]]</li> | <li>For more information or documentation, see [[:Category:Metamod:Source Documentation]]</li> | ||
</ul> | </ul> | ||
| − | The < | + | The <code>gameinfo.txt</code> loading method is supported as a legacy feature only. The patcher tool is no longer provided. You can mark <code>gameinfo.txt</code> if you absolutely want to protect it from being overwritten. |
We will continue to make sure Metamod:Source can load via this method for as long as the Source Engine allows it. However, we will concentrate more on supporting the new loading mechanism for general use. | We will continue to make sure Metamod:Source can load via this method for as long as the Source Engine allows it. However, we will concentrate more on supporting the new loading mechanism for general use. | ||
[[Category:Metamod:Source Documentation]] | [[Category:Metamod:Source Documentation]] | ||
Revision as of 01:59, 14 January 2023
This article will guide you through a Metamod:Source installation.
Normal Installation
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.
- Download Metamod:Source.
- Extract the package to your game folder. For example, for Counter-Strike:Source, you would have
cstrike/addons/metamodafter extracting. If you are uploading to FTP, extract the files locally before transferring to your server's game folder. - Restart your server.
- 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 versionis recognized, Metamod:Source is installed. - An error indicating that it could not be loaded because "/path/to/server_install/bin/libgcc_s.so.1: version `GCC_7.0.0` not found (required by /some_system_path_to/libstdc++.so.6". 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
liborlib32). - 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.
- On Debian / Ubuntu, you can do this with
- You may find more information about any load failures under a
metamod-fatal.login metamod'sbinfolder.
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:
- Left 4 Dead 1
- 3rd party mods using the Source SDK Base.
- Listen servers (created with the in-game "Create Server" option) for non-english game clients.
GameInfo
Note: 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.
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.txt 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.txt directions below:
- Open the file in the mod folder called "gameinfo.txt". You will see a few lines at the bottom like this:
SearchPaths { 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.txtwas probably not modified correctly. - For more information or documentation, see Category:Metamod:Source Documentation
The gameinfo.txt loading method is supported as a legacy feature only. The patcher tool is no longer provided. You can mark gameinfo.txt if you absolutely want to protect it from being overwritten.
We will continue to make sure Metamod:Source can load via this method for as long as the Source Engine allows it. However, we will concentrate more on supporting the new loading mechanism for general use.
