# The Admin Mod Configuration Files

If you have run a Half-Life dedicated server for more than a minute or two already, then you know that the server uses configuration files (usually with a file extension of .cfg) to set many optional configuration variables that the server reads when it is started. Admin Mod has a similar set of files, which determine how the Admin Mod is configured and behaves. Most of Admin Mod's configuration files have an extension of ".ini" - although some of Admin Mod's configuration options are set in the Half-Life server config files.

See also: Setting up server.cfg and the *.ini files

Here’s a quick description of what each of the specific Admin Mod .ini files are used for:

users.ini
The users.ini file is used to specify who will have special rights on your server (by name or WON ID) and what commands they have permissions to execute. See: Setting up your users.ini file

ips.ini
The ips.ini file is used for slot reservation on your server based on IP address. All you have to do is specify the IP addresses of the computers that can use one of your reserved slots. See: Setting up your ips.ini file

models.ini
The models.ini file is used for model reservation. It prevents players from using the specified models unless they set the correct password. It lets you protect any given model from use by unauthorized players. See: Setting up your models.ini file

maps.ini
The maps.ini file is used to control which maps users can vote for. It has the same format at the mapcycle.txt file. Note that it does not replace the mapcycle.txt file (which controls the maps that run on your server and the order they are played in). Instead, it is just a list of maps available to be started via an Admin Mod vote. See: Setting up your maps.ini file

plugin .ini
New to version 2.50, this file is used to denote the compiled script files that are to be used on your server. The scripts that come with Admin Mod 2.50 are organized and split into chunks by functionality and by game type. So, to add a custom script or disable certain parts of the functionality, one has the option with this file to do so without having to recompile every piece of functionality, every time you make a change. Want to test a new script? Just compile it, dump it into the mod's dlls directory, add the script name to the plugin.ini file and reload – presto, you can test away, and you didn’t have to modify (and possibly break) your already existing scripts. See: Setting up your plugin.ini file

metamod .ini
This is a simple file that specifies the DLL (dynamic link library) file to run when using meta mod in conjunction with Admin Mod. Starting with Admin Mod version 2.50, here is what happens:- HLDS executes metamod.dll - Metamod in turn executes admin_mm.dll. If that’s confusing to you or makes absolutely no send, don’t worry – it’s more useful for people upgrading from an older version of Admin Mod, and hopefully they will know what we mean. If they don’t, they should read the fast-track/manual upgrade documentation. The metamod.ini file comes pre-configured and is very simple. You should not need to change it, but if you do, we will assume you know how it works and what you are doing to an extent where you will not need such an explanation. Note that Meta Mod is frequently updated. Be sure you are always running the latest version by checking regularly at http://www.metamod.org for updates. See: How to Use Bots with MetaMod (AM 2.50)

There is also a “metagame.ini” file that can be used, but it is usually not needed. It would be used, for instance, to start another mod program which otherwise would have been loaded in the liblist.gam file if Admin Mod was not installed on the computer (Bots are a good example of this). If you are using a non-supported mod or auto detection of your game mod fails, feel free to go to the Admin Mod Forums and ask for help.

Another file, named “liblist.gam,” is a plain text file on your server that the dedicated server program reads when started to determine what it should do and some of the files it should load and run. This file is not unique to Admin Mod -- all servers utilize this file to specify what base runtime options and resources the server should use. Admin Mod requires that this file be changed in order to allow the server to start Admin Mod when the server itself is fired up. The specifics of this file and it's setup for Admin Mod are discussed later in a section covering manual installation. If you are doing the standard, automated installation, this file is configured for you.