Date: 06 8, 2001 3:37:23 PM

# Manual Installation - Walk-Through

Note:This portion of the guide discusses a manual installation of Admin Mod, and is not recommended for people who do not have a clear understanding of directory structures, file editing, etc. – For a script-based, more automated installation, please read the Running the Windows Installation Script section. However, no matter what type of installation you are undertaking, there is a lot of good information to learn from here, so be sure to read it at some point in time, even if you do script-based installation.

Note:For Linux users, the installation process is identical to the one described below, except for the .dll files. When reading, mentally replace '.dll' with '_i386.so'. This means that 'metamod.dll' corresponds to 'metamod_i386.so'. Furthermore, slashes must be inverted when discussing file paths.

This walkthrough will leave you with a fully functional default installation of Admin Mod. It does not cover adding users or plugins to your server.

1. Stop What you are doing

   If your server is running stop it. Atempting to install Admin Mod with the server running is a bad idea.

2. Unpack/unzip the file you downloaded.

   Make sure to allow the directory structure in the ZIP file to be recreated when the files are unzipped. If you are using WinZip, you should make sure the box labeled "Use folder names" is checked before you extract the files from the zip archive. There should also be a way to specify this in any other archive program you may use.

   We will refer to the location where you have unpacked/unzipped Admin Mod as the "Admin Mod Directory" (`<AM>`)

3. Find your Half-Life Installation.

   Where do you want to install Admin Mod to? First find the folder where you installed Half-Life or Counter-Strike. In this folder there should be one or more executable files with the Half-life or Counter-Strike icon, as well as the files hl.exe hlds.exe OR cstrike.exe if you have the Counter-Strike Retail version of Half-Life. This folder will be refered to as the Half-Life folder (`<HL>`).

4. Find your Mod Directory.

   In the Half-Life folder there are a set of folders, such as tfc, dmc and Ricochet and you may have others. Many of these folders will have a game modification in them. For example cstrike is the Counter-Strike mod folder and dod is the Day Of Defeat Mod folder.

   You need to find the folder of the mod for which you want to install Admin Mod. If I wanted to install Admin Mod for Counter-Strike, my mod folder would be cstrike, if i wanted to install for Science and Industry Mod, the mod folder would be si. This is refered to as the "Mod Directory" (`<MOD>`). Normally it is trivially simple to work out what mods are in which folders but if you can't work it out try looking at the names of the maps in the `<MOD>\maps\` directory.

5. Install Metamod

   - In the `<MOD>` directory create a new folder. Name it `addons`

   - In the `<MOD>\addons\` folder create a new folder. Name it `metamod`

   - In the `<MOD>\addons\metamod\` folder create a new folder. Name it `dlls`

   - Copy the file metamod.dll from `<AM>\dlls\metamod.dll` to `<MOD>\addons\metamod\dlls\metamod.dll`

   - Copy the file metamod.ini from `<AM>\config\metamod.ini` to `<MOD>\addons\metamod\plugins.ini`

   All the metamod files are now installed. To activate it when the server starts, the liblist.gam file needs to be modified. This is best left until last.

6. Install Admin Mod

   - In the `<MOD>\addons\` directory create a new folder. Name it `adminmod`

   - In the `<MOD>\addons\adminmod\` directory create three new folders. Name them `dlls`, `config` and `scripts`

   - Copy all files with a .amx extension from `<AM>\scripting\binaries\` to `<MOD>\addons\adminmod\scripts\`

     If there are no .amx files in the `<AM>\scripting\binaries\` folder then you will need to create them. To do this run the compile_all.bat batch file on windows or the compile_all shell script on linux. This is in `<AM>\scripting\examples\` folder. Once it has finished you should copy the newly created .amx files across as described above.

   - Copy the files `admin_MM.dll` and `amx_admin.dll` from `<AM>\dlls\` to `<MOD>\addons\adminmod\dlls\`

   - Copy the files `plugin.ini` and `adminmod.cfg` from `<AM>\config\` to `<MOD>\addons\adminmod\config\`

   - Edit your current config file(s)

     If you are running a listenserver (you launch a server with the 'Create Game' button and do not tick the 'Dedicated Server' box) then you need to edit the listenserver.cfg file.

     If you are running a dedicated server you need to edit your server.cfg file

     If you use both server types edit both files

     Open the .cfg file in a plain text editor (notepad, vim or something similar that will save as plain text) and go to the bottom of the file. Add the lines:
     `// execute the adminmod config file
     exec addons/adminmod/config/adminmod.cfg`
     Save the file. Close the file.

7. Add Admin Mod to the Metamod plugins.ini

   Open the file `<MOD>\addons\metamod\plugins.ini` in a plain text editor

   - Windows users

     add the line
     `win32 addons/adminmod/dlls/admin_MM.dll`

   - *nix users

     add the line
     `linux addons/adminmod/dlls/admin_MM_i386.so`

   Save the file. close the file

8. Edit your Admin Mod config file

   See: Setting up your Admin Mod config file

9. Edit your users.ini file

   See: Setting up your users.ini file

10. Edit your plugin.ini file

    See: Setting up your plugin.ini file

11. Set up any other files you may need

    if you know that you need one or more of these files then you should read the relevant sections linked to below. If you don't know what these files are for then you probably don't need them yet so you should move on to the next step.

    - maps.ini: Setting up your maps.ini file

    - models.ini: Setting up your models.ini file

    - ips.ini: Setting up your ips.ini file

12. Backup your liblist.gam file

    It is always a good idea to have a backup of the liblist.gam file in case things go badly and you need to revert to a normal server without MetaMod enabled.

    Copy the file `<MOD>\liblist.gam` to `<MOD>\AdminMod_backup_of_liblist.gam`

13. Edit your liblist.gam

    If you did not stop your server at the begining of this guide then do so now.

    - Windows users

      Open the `<MOD>\liblist.gam` file in a plain text editor (notepad, etc). Find the line which begins with the word `gamedll`. For Science and Industry mod, this line reads:
      `gamedll "dlls\si.dll"`
      Change the path inside the double quotes so that it points to the metamod.dll file:
      `gamedll "addons\metamod\dlls\metamod.dll"`

    - *nix users

      Open the `<MOD>\liblist.gam` file in a plain text editor (vim, etc). Find the line which begins with the word `gamedll_linux`. For Science and Industry mod, this line reads:
      `gamedll_linux "dlls/si_i386.so"`
      change the path inside the double quotes so that it points to the metamod.dll file:
      `gamedll_linux "addons/metamod/dlls/metamod_i386.so"`

    Save the file and exit the editor.

14. Restart the server

    Admin Mod and MetaMod are now installed and enabled. When you start the server it will load MetaMod, MetaMod will load Admin Mod and the server will then continue as normal.

Configuration of access levels, users accounts, name reservations and other features are explained elsewhere in this documentation. This guide leaves you only with Admin Mod installed and working, the rest is up to you. We strongly reccomend that you read the rest of this manual thoroughly before you proceed to try and use Admin Mod.