BF2CC - ModManager Python Script Installation Procedure:

MODMANAGER SCRIPTS ONLY NEED TO BE INSTALLED SERVER SIDE

R-Con Only Users:

1. Download and Extract the ModManager.zip Scripts into the root path of your BF2 dedicated server install. This is C:\Program Files\EA Games\Battlefield 2 Server\ by default. Your path may be different.
2. Open up the \Battlefield 2 Server\Mods\BF2\Settings\ModManager.con file using Wordpad or Notepad.
3. Find and edit the following R-Con settings:

   mm_rcon.rconIp "0.0.0.0"
   mm_rcon.rconPassword "password"
   mm_rcon.rconPort 6711

   Specify your IP, Password and Port. This Rcon port must be open for TCP traffic through your firewall. Specifying an IP of 0.0.0.0 will bind to ALL IP's on that computer. You can't use 0.0.0.0 if you are running multiple BF2 servers on that computer.

4. Make sure that you are telling your BF2 server to use the ModManager scripts instead of the default admin scripts. If you are using the EA Server Launcher you can set the AdminScript setting to ModManager. If you are launching the server manually (or other method), you will need to make sure your ServerSettings.con file has the following setting:

   sv.adminScript "modmanager"

5. Launch your BF2 server OR Reset the Server if it was already running.
6. You should be able to connect to the R-con now using the BF2CC client. If you are having connection issues you can test your Rcon by following these instructions.

   R-Con Only users can use ModManager to perform auto-administration tasks on their server. Please read the ModManager.txt file inside the ModManager.zip file for more info.

Daemon Users:

1. Extract the ModManager.zip Scripts into the root path of your BF2 dedicated server install. This is C:\Program Files\EA Games\Battlefield 2 Server\ by default. Your path may be different.
2. Daemon Users do NOT need to modify any files. The Daemon will automatically edit the ModManager.con files with the appropriate R-Con settings when the Daemon launches your BF2 server.
3. The ModManager.con file that are included with the ModManager scripts (which ship inside of the Daemon files) are automatically setup to DISABLE the auto-admin features of ModManager. This is because it is easier to use the Auto-Admin features built into the Daemon and controlled through the client GUI. If you want to ensure that your ModManager.con file has MM Auto-Admin features disabled, you should edit the following settings inside your ModManger.con file.

   mm_kicker.idleLimit 0
   mm_kicker.maxPing 0
   mm_kicker.enableChatChecks 0