ConfigManager 1.72

PLEASE READ THE IMPORTANT.TXT FILE!  IT CONTAINS (*SUPRISE*) IMPORTANT INFO!

ConfigManager is a tool designed for dedicated servers. It simplifies administration of 
a server by eliminating the need to modify the server ini file when making changes to
add-ons, such as mods & mutators.  Activating & disactivating an add-on that is compatible
with ConfigManager is a simple as checking one checkbox in webadmin (or issuing one command
from the console).

ConfigManager has two functions:

1. AutoInstallation (includes activation & deactivation)

2. Increased control over the mods configured for your server, by ensuring that EVERY mod on
   your server (including those that are known as ServerActors) to add settings to webadmin/adminmenu.
   
Config Manager does its magic through special "loader" files.  In order for Config Manager to be able
to control a mod/mutator on your server, the mod/mutator must come with a loader file (something like
"ConfigManagerLoader.u").  If your favorite mod doesn't provide a loader, thus cannot be controlled by
Config Manager, contact the mod author to inquire about future compatibility with Config Manager.




================================================================================================================
Installation
================================================================================================================

To install Config Manager, you'll need to replace your current access control with Config Manager's
access control. (If you are upgrading from a previous version of Config Manager, no changes are necessary.  Simply
overwrite the ConfigManager.u and ConfigManager.int files with the versions contained in this .zip file.)


There are two ways to change the access control on your server:

1. You can specify the appropriate access control on the command line (via the ?AccessControl parameter)
   Ex: ucc server CTF-Magma.ut2?Game=xGame.xCTFGame,?AccessControl=ConfigManager.ConfigMasterAccessControlIni
   
2. You can change the value of the 'AccessControlClass' line in the [Engine.GameInfo] section of your server's ini.
   Ex: [Engine.GameInfo]
       AccessControlClass=ConfigManager.ConfigMasterAccessControlIni
              
NOTE: You should only use 1 of the above methods, not BOTH!




As you know, there are two different administration systems in UT2003.  The value you use to enable Config Manager
will depend on which administration system you normally use on your server.

Single Administration System
--------------------------------------------------------------------------

To enable Config Manager from the command line, add this parameter:
?AccessControl=ConfigManager.ConfigMasterAccessControl

OR

To enable Config Manager from the ini file, change this value:
[Engine.GameInfo]
AccessControlClass=ConfigManager.ConfigMasterAccessControl

NOTE: Only use 1 of the above methods, not BOTH!


Advanced Administration System
---------------------------------------------------------------------------

To enable Config Manager from the command line, add this parameter to the command line:
?AccessControl=ConfigManager.ConfigMasterAccessControlIni

OR

To enable Config Manager from the ini file, change this value:
[Engine.GameInfo]
AccessControlClass=ConfigManager.ConfigMasterAccessControlIni

NOTE: Only use 1 of the above methods, not BOTH!


===============================
Detailed Overview of Features:
===============================

AutoInstallation
----------------------------------------------------------------------------------------------

AutoInstallation is the primary (and most exciting) feature of ConfigManager.  It takes all of the
guesswork out of installing and configuring mods & mutators by allowing the mod authors themselves
to do all the work for you!

Mod authors must include a seperate .u file (which will never be more than 5KB or so) in the zip file for any mod
(past or present).  This file contains all of the information that is required for the mod to be completely 
installed properly.  ConfigManager uses these small files to control all of the ini changes.  The way it's 
setup, there is no "package dependency", which means that even if you download and install a mod/mutator 
that is compatible with ConfigManager, and (for some strange reason :P ) you don't have ConfigManger installed 
on your server, it won't cause any errors or crash the server.

Installing a ConfigManager-compatible mod is as simply as 1-2-3:

1. Download the zip file containing the mod.
2. Unzip the contents of the file into your server's UT2003 directory.
3. Restart the server.

Bingo!  The new mod is now ready to be activated.  It varies with each mod, but normally, you can enable a
mod by browsing to the "Server Actors" section of the "Defaults" page in webadmin, which will automatically
appear once you have at least one loader in your system directory.


Extended Control
----------------------------------------------------------------------------------------------

ConfigManager also features extended control over the packages on your server.  By default, UT2003 does not allow
many mods a chance to add stuff to webadmin.  Mods that are installed by adding lines to ServerActors are a 
good example of the type of mod that will usually not have a chance to add stuff to webadmin.

Config Manager extends the power of UT2003's new webadmin system by providing many options for mod authors
to automatically add all their configurable options to webadmin.

ConfigManager is also 100% compatible with Ladder, and through tightly integrating Ladder with ConfigManager, you'll
now be able to add all ConfigManager-compatible mods to your Ladder profiles.
