============================ BF2CC Client INSTALLATION: ============================ 1. Extract ALL files into their own Folder. You must run the BF2CC.exe file from a folder with ALL included files. You can NOT run BF2CC.exe from Winzip, Winrar, or any other shell/zip style program. 2. You MUST have the .NET Framwork 1.1 installed to run BF2CC.exe. If you get an error while trying to load the program, then you don't have the .NET Framework 1.1 installed. Please go to www.WindowsUpdate.com to get ALL Windows Updates, .NET Framework 1.1, .NET Framework Service Packs etc. BF2CC will NOT work with the .NET Framework Beta 2.0 or 1.0. 3. You can connect the BF2CC client directly to the BF2 Dedicated server (via the ModManager Scripts) or you can connect the BF2CC Client to the BF2CC Daemon. In either case, you will need to have the ModManager Scripts installed on your Battlefield 2 Server. In the Login Screen, make sure you specify which type of connection you wish to make. The choices are BF2CCDaemon or R-Con Only. ===================== R-Con vs. Daemon ===================== Running the BF2CC Daemon is the preferred to an R-Con only connection. Using the BF2CC Daemon provides additional functionality such as: ** BF2 Server Process Management (Ability to start/stop the Server remotely) ** Multiple User Accounts with Role Based Security Permissions (Access to certain features can be restricted) ** Logging of all Admin Actions ** Store and Apply settings using a convenient Profile based system ** Future Improvements such as the ability to store Extra Ban List information and retrieve PB Screenshots If you have complete remote access to your server, you will want to install the BF2CC Daemon alongside your BF2 server. In either case, you will need to install the ModManager Scripts onto the computer running your BF2 server. See ModManager Install section below. You can download the MM scripts from http://www.BF2CC.com. They also come included in the latest Daemon release. ===================== Trouble Shooting ===================== ** BF2CC Client Won't Load You MUST have the .NET Framwork 1.1 installed to run BF2CC.exe. If you get an error while trying to load the program, then you don't have the .NET Framework 1.1 installed. Please go to www.WindowsUpdate.com to get ALL Windows Updates, .NET Framework 1.1, .NET Framework Service Packs etc. BF2CC will NOT work with the .NET Framework Beta 2.0 or 1.0. ** Connection Problems: 1. Make sure you have the ModManager Scripts Installed on your BF2 server and that your Server is using ModManager. See ModManager Section Below. 2. You can test your R-Con functionality. Instructions at http://www.bf2cc.com/help_test_admin_scripts.htm 3. Make sure if you have the correct Connection Setting selected on the Login Screen. "BF2CCDaemon" vs "R-Con Only" 4. If making an R-Con Only Connection then you need to have your R-Con Port (as specified in the ModManager.con file) open for TCP traffic through your server's firewall. (Default R-Con Port = 6711) 5. If making a BF2CCDaemon connection, make sure you have a BF2CCD running on your server and that the Daemon port (Default 6712) is open for TCP Traffic through your server's firewall. ** Client won't Start Refreshing After Launching/starting the BF2 server (Daemon Mode Only) This is a known issue that can occur randomly or always on certain systems. The only workaround currently is to re-login. Just click the Disconnect Button, and then the Login Button. ===================== ModManager Install: ===================== !!!!!! MODMANAGER SCRIPTS ONLY NEED TO BE INSTALLED SERVER SIDE !!!!! !!!!!! R-Con Only Mode must have ServerSettings.con file with --> sv.adminscript "modmanager" <-- setting. !!!!!! MODMANAGER SCRIPTS ARE NOT NECESSARY TO RUN THE BF2CC CLIENT !!!!! For More Info on ModManager Please visit http://forums.multiplay.co.uk/forumdisplay.php?s=&forumid=195 1. Just extract the ModManager script files directly into your C:\Program Files\EA Games\Battlefield 2 Server\ folder. NOTE: Your folder might be different, so extract these files into the root folder of your BF2 server. 2. Overwrite any files if prompted to do so. You can download the latest MM scripts at http://www.BF2CC.com 3. If you will be making an R-Con Only connection, you must edit your ModManager.con file to reflect the R-Con settings you wish to use. This file is located in your C:\Program Files\EA Games\Battlefield 2 Server\Mods\BF2\Settings\ folder. You can specify the values for the following Settings: mm_rcon.rconIp "0.0.0.0" mm_rcon.rconPassword "testpw" mm_rcon.rconPort 6711 ** Setting the R-Con to an IP of 0.0.0.0 will bind to ALL IP's on that machine. If you are running more then 1 BF2 server, you will need to specify the individual IP's for each server. ** Make sure that your R-Con port is open for TCP traffic through your firewall. ** Reboot Your BF2 server after you install the MM Scripts. 4. If you will be using the Daemon on your server there is no need to touch any ModManager files. The Daemon will automatically edit the ModManager.con file 5. If using R-Con Only mode, you must edit your ServerSettings.con file to use: sv.adminscript "modmanager" You can specify this setting using the EA server launcher as well. ====================== 2048 Change Log ====================== The Daemon supports the Following Auto-Admin Features * Smart Team Balance (Priority Based) * Idle Player Detection with Auto-Kick * High Ping Kick * Auto- Warn/Kick/Ban on Banned Words * Switch Teams at End of Round * Auto-Messages ** CHANGED (Admin Scripts) BF2CC now relies ModManager Scripts with the BF2CC module. MM scripts can provide R-Con only servers with Auto-Admin features! ** FIXED (Client Bug) Profiles weren't saving if the Map List form wasn't loaded, due to a failed Map Count Check ** FIXED (Client Bug) After losing a connection to the Daemon or Rcon, sometimes a Re-login caused a crash ** FIXED (Client Bug) New Reasons weren't being saved in the W/K/B Options Menu ** FIXED (Client Bug) Exiting the program using File --> Exit wasn't saving the form layout. ** FIXED (Client Bug) Removed a Debug Messagebox saying "Close Up" in the User Section ** FIXED (Client Bug) Prompt Before Stop/Restart label was cutoff in general options menu ** FIXED (Client Bug) Changing the value for Community Logo URL wasn't enabling the save/cancel buttons ** FIXED (Client Bug) Elapsed Time now stops counting when you are disonnected or when the server is not running ** FIXED (Client Bug) Fixed Infragistics Component crashes. No more big red X's on player's grid or log grid. (hopefully) ** FIXED (Client Bug) Profiles weren't updating when connecting betweeen 2 different Daemons. ** CHANGED (Client) Changed some code to prevent more than 1 login form from being created and possibly prevent strange behavior when logging in and out multiple times ** CHANGED (Client) "Outlook" Group By Row removed to save space. Users can use Row Filter to sort by User ** CHANGED (Client) Removed Map Check. It is now on the Daemon side. ** ADDED (Client) Player's Grid now shows Rank Icons, Total Time for Each Player on the Server, and Idle time for Each Player ** ADDED (Client) R-Con IP Setting to the Dashboard Control, so that Rcon IP can be changed remotely (as opposed to only in the configuration of the daemon) ** ADDED (Client) Join Button to join the BF2 server you are connected to. ** ADDED (Client) Client can import .con files (Settings or Maps) into the GUI. ** ADDED (Client) Ability to enter a custom message (on the fly) underneath the warns/kick/bans right click menu ** ADDED (Client) Ability to Right Click on a Player Name in the Chat Log and Warn/Kick/Ban for Language Violation ** ADDED (Client) Added "Copy" Right Click Menu to In Game Chat & Log Controls. ** ADDED (Client) Option to Kick Using PunkBuster kicks (displays kick reason to player after disconnect) ** ADDED (Client) "[Ranked]" Indicator in Server Status for ranked servers ** ADDED (Client) Added More Error dialog boxes to show an unsuccessful Start BF2 Server request (Daemon Mode) ** ADDED (Client) Players on Each Team Next to Tickets ** FIXED (Deamon Bug) Windows Daemon Crash when starting up and trying to create default.profile. Crash was caused by maplist.con files with an extra space at the end of the last line. ** FIXED (Daemon Bug) Memory Leak Bug in the ReadBlock and ReadLine functions for RCON communications would cause huge memory leaks on Linux servers ** FIXED (Daemon Bug) Bug in the automessage function would not display the 5minute BF2CC message ** FIXED (Daemon Bug) Enhanced the server shutdown to use quit before trying to kill the process (Linux) ** FIXED (Daemon Bug) Profiles with no maps will load the first map in the folder to prevent a crash ** ADDED Additional Error handling to startup and profile creation code ** ADDED (Daemon) Added the Following Command Line Parameters -daemonconfig Goes through the reconfiguration section. The daemon will also launch the config screen if the file config.xml is missing. -ranked Runs the server in ranked mode. Required in order to be able to launch a ranked server. -showlog Shows log to screen -noquitprompts Disables the GUI Prompts when quitting the daemon. -autostart "profile name" Automatically launches the BF2 server with the last/default profile when the Daemon is started. "profile name" is an optional parameter and should represent a profile name. -lockdemorec Disables Demo Recording. Nobody can Change. This is a provider request since it's eats CPU -locknetsettings Locks the BF2 network settings controls on the Client. This is a provider request so that users can't screw up their BF2 network settings. -playerlimit Nobody can exceed maximum player limit. -skipportchecks Skips open port checking for RCON and Daemon.