Click Here to Learn How to Install the ModManager Scripts

Take the following steps to test your admin script installation:

1. Make sure that your BF2 server is running and is fully loaded and intialized.

2. Start a command prompt by clicking START --> RUN

3. Type "cmd" (no quotes) and hit Return or Click OK. A black command window will open.

4. Type "telnet <IP> <RconPort>" where you replace the <IP> and <RconPort> with the IP and Rcon port (specified in your ModManager.con file in your BF2 Server\admin\ folder. For example, if you are on the same machine running the BF2 dedicated server and you want to test the rcon to make sure it is alive and running you would type "telnet 127.0.0.1 6711"

5. If the Rcon is running, you should see an authentication request.
   ### Battlefield 2 version 3.6 s default RCON/admin ready.
   ### Digest seed: prIzoGBWsyjuSiRr
   

6. Notice the Script revision "3.6". This tells you which revision scripts you are running. If you don't see a script revision then you are NOT running the BF2CC admin scripts.

R-Con Only vs. Daemon Mode Explanation:

The Admin scripts ARE the Rcon connection between the BF2CC Software and the BF2 dedicated server. The admin scripts only need to be installed on the BF2 Server.

In the case of R-Con Only mode, ALL BF2CC clients which connect have their own Rcon connection to the BF2 Server.

In the case of Daemon mode, ONLY the BF2CC daemon talks to the BF2 dedicated server through the Rcon connection on the local machine. In daemon mode all of the BF2CC clients connect to the daemon and the daemon is the gateway between all user commands to the BF2 dedicated server. Since the daemon is the only program talking to the BF2 server, it's easy to see how you can have the added features of user accounts, logging etc in daemon mode. It is NOT necessary to expose your Rcon port to the internet when running Daemon mode, but you will need to expose the Daemon port to the internet (default = 6712) so that the BF2CC clients can connect to the daemon.