Note: In these installation instructions, we refer to the root of your game directory structure as <mod_dir>. For example, if you have a Windows dedicated server with a default installation and you are using Counter-Strike, then <mod_dir> would be C:\HLServer\cstrike\. If you are using Linux and TFC, then <mod_dir> would be /home/hlds_l/tfc. Please verify the location of your Half-Life server before beginning this installation process. Old users note: Metamod and clanmod have changed directory, all files have been moved due to the new addon folder structure, please make note of this and read all paths carefully.
If you already have Metamod installed on your server then you can skip this step and move on to step two. Since Metamod is also required for AdminMod, HLGuard, StatsMe, Cheating-Death and many other Half-Life mods, many servers already have it installed.
If you need to download Metamod you can get it at one of the following:
You do not need the complete package. All you need is metamod.dll for Windows servers or metamod_i386.so for Linux servers. Download this file and save it in the <mod_dir>/addons/metamod/dlls/ directory.
Next, you need to update your liblist.gam file so that metamod is loaded. liblist.gam exists in <mod_dir>. Follow these instructions depending on whether you are running a Windows or Linux server.
For Windows servers:
- open liblist.gam with a plain text editor such as Notepad. Avoid the use of rich text editors such as Wordpad and MS-Word.
- find the line that specifies your game dll. It looks something like this:
gamedll "dlls\<yourgame>.dll"- change this line to this:
gamedll "addons/metamod/dlls/metamod.dll"- save and close the file
For Linux servers:
- open liblist.gam with a such as vim, or pico.
- find the line that specifies your Linux game dll. It looks something like this:
gamedll_linux "dlls/<yourgame>.so"- change this line to this:
gamedll_linux "addons/metamod/dlls/metamod_i386.so"- save and close the file
For Windows servers:
- extract clanmod_mm.dll into the <mod_dir>/addons/clanmod/dlls/ folder.
- extract the ClanMod config files and directories into the <mod_dir>/addons/clanmod/ folder. This folder may need to be created if you don't have a previous version of ClanMod installed.
- open the file <mod_dir>/addons/metamod/plugins.ini in a plain text editor such as Notepad. Avoid the use of rich text editors such as Wordpad and MS-Word. This file may need to be created if it doesn't already exist.
- Add the following line to plugins.ini: win32 addons/clanmod/dlls/clanmod_mm.dll
- save the file and exit the text editor
For Linux Servers:
- extract clanmod_mm_i586.so into the <mod_dir>addons/metamod/dlls/ directory.
- extract the ClanMod config files and other directories into the <mod_dir>/addons/clanmod/ directory. This directory many need to be created if you don't have a previous version of ClanMod installed.
- open the file <mod_dir>/addons/metamod/plugins.ini in a plain text editor such as vim, or pico. This file may need to be created if it doesn't already exist.
- Add the following line to plugins.ini:
linux addons/clanmod/dlls/clanmod_mm_i586.so- save the file and exit the text editor
ClanMod is now installed and ready to run. To start ClanMod, stop and restart your hlds server. The ClanMod plugin should automatically load. You can also load and unload the plugin on every map change using the appropriate Metamod commands. (Type "meta help" in server console for more help) To ensure that the plugin is running, type "clanmod_version" in your hlds console.
To configure and customize ClanMod, edit the various configuration files found in <mod_dir>/addons/clanmod. The first thing you need to do is define your admins. To do this, edit the file <mod_dir>/addons/clanmod/cm_admins.cfg. There are many examples of how to do this included in the file. For complete details on how to define admins, see the ClanMod Manual section titled "Creating Admins". Once you have defined your admins, you will want to make use of ClanMod when you are in-game. For instructions on how to do this, see the sections "Logging In" and "On-Screen Menus" in both the ClanMod Manual and the ClanMod Adminstrator's Guide.
For your reference, the various files and directories in <mod_dir>/addons/clanmod/ are described below:
Main configuration files found in <mod_dir>/addons/clanmod/:
- clanmod.cfg: the root config file which sets up the basic ClanMod features and execs the other config files. Note: this file is automatically exec'd by ClanMod. It must always reside in <mod_dir>/addons/clanmod/ and must not be renamed.
- titles.cfg: all of the text messages that ClanMod displays are defined here using cm_string commands.
- cm_admins.cfg: the server admins and their access flags are defined here using cm_admin commands.
- cm_menus.cfg: the menu commands are defined here using cm_cmd commands.
- cm_maps.cfg: the maps available for changelevel and voting are listed here using cm_map commands.
- cm_badwords.cfg: words not permitted to be said on the server are listed here using cm_word commands. Also, if word replacement is enabled, replacement phrases are defined here using cm_whine commands.
- cm_aliases.cfg: command aliases are defined here using cm_alias commands.
- cm_cvars.cfg: cvars are defined here using cm_cvar commands.
Other files and directories found in <mod_dir>/addons/clanmod/:
- addons/: ClanMod addon scripts
- clans/: server config files for clans
- leagues/: server config files for leagues
- matches/: server config files for matches
- conmotd.txt: Displayed in the console when players connect.
- rules.txt: Displayed when "Show rules" menu item is selected.
- adminhelp.txt: Displayed when "Show help" menu item is selected by admins.
- playerhelp.txt: Displayed when "Show help" menu item is selected by non-admins.
- banlist.txt: contains a log of all bans that admins have made using ClanMod.
- snaplist.txt: contains a log of all snapshots taken using ClanMod.
NOTE: If you get the error message "Z_Malloc: failed on allocation of xxxx bytes" when loading a new map, you will have to either make smaller configs (remove comments - lines with "//" at the beginning) or run the server with the command line parameter -zone 4096.