Battlefield 2™ Dedicated Server Readme v1.0 (new revision)
July 21st 2008
Copyright Electronic Arts
Battlefield 2™ v1.50

=================

Table of Contents

I. Installing the Windows Dedicated Server
II. Configuring and starting the Windows server using the Server Launcher
IIa. Configuring and starting the Windows server using the server executable
III. The Map List
IV. Installing the Linux Dedicated Server
V. Configuring and starting the Linux Dedicated Server
VI. Hosting a Battlefield 2™ Server
VII. Remote Console (rcon) Access
VIII. BattleRecorder
IX. Points to note when using BattleRecorder
X. Remote VOIP Server
XI. Appendix A – Map Names, Sizes & Modes
XII. Appendix B – Useful commands
XIII. Appendix C - Hardware Requirements
XIV. Appendix D - Server settings and their functions
XV. Version notes

==========================================

I. Installing the Windows Dedicated Server

To install the server, double click the “Battlefield 2 Server.exe” file and follow the on screen prompts. It is recommended you install PunkBuster even if you are not running a Ranked server.

Note that if your system clock and date are not set correctly this can lead to issues with stats processing on Ranked servers. Please ensure the time and date are set correctly before starting the game server.

=========================================================================

II. Configuring and starting the Windows server using the Server Launcher

Run the shortcut to start the server – “Start” – “Programs” – “EA Games” – “Battlefield 2 Server” – “Run Dedicated Server” and the Server Launcher window will appear.

Click the “+” at the bottom to create a new profile.

Enter a suitable name (no spaces or special characters allowed) and click “OK”.

Edit the settings in the server GUI as needed. Note that clicking once on an option will display a brief description of what function that command carries out.

See Appendix D for a list of the server commands and their functions.

============================================================================

IIa. Configuring and starting the Windows server using the server executable

It is possible to start the server without using the Server Launcher GUI. This is done by creating a shortcut to the server executable (BF2_w32ded.exe) and applying startup parameters to it. The syntax for the parameters are as follows:

+config
+mapList "

Example:

"C:\Program Files\Electronic Arts\Battlefield 2 Server\BF2_w32ded.exe" +config C:\serversettings.con +mapList C:\maplist.con

This setup is designed primarily for Ranked Server Partners. For individual servers it is more convenient to use the Server Launcher.

=================

III. The Map List

The maplist tab allows you to select the maps and game modes you want to run on the server. By default this will display Conquest maps, but the game mode can be selected by clicking on the right hand dropdown box:

The available game modes are as follows:

Gpm_cq – Conquest
Gpm_coop – Cooperative

Different maplists are available for each game mode. Not all game modes are available on all maps. Note that coop can only be played on maps that are enabled for single player. Also note that Cooperative mode is not supported on Ranked servers. If Cooperative mode is selected on a Ranked server the ranking system will be disabled while the Coop map plays.

See Appendix A for a list of all the map names and their supported modes and sizes.

To add a map to the maplist, simply highlight it in the left hand window and click the right arrow to add it. You may also add maps by double clicking them, or use CTRL + click or SHIFT + click to add multiple maps. Use the up and down arrows to re-order the maps in the right hand window.

Maps may be removed from the maplist in the same fashion.

Once you have configured your settings and added the maps you want, click the “Save” button to save the configuration and then click the “Start” button to start the server. Note that clicking on “Start” again will set the server to auto-restart if it should end unexpectedly.

=========================================

IV. Installing the Linux Dedicated Server

Copy the install archive onto your server PC and double click it to begin the installation.Select “Run in a Terminal” from the resulting pop up.

Note that if you are carrying out a remote installation using SSH or other remote admin tool you may need to use the “chmod” command to allow the correct file access privileges. Please consult your Linux documentation on how to use the “chmod” command.

Once the archive has unpacked, you will be required to read and accept the EULA both for the server and for PunkBuster before installation will continue.

Enter a suitable path to complete the installation, for example /Home//. The server will automatically create a folder called “BF2” in that path and install the server into it.

Note that if your system clock and date are not set correctly this can lead to issues with stats processing on Ranked servers. Please ensure the time and date are set correctly before starting the game server.

======================================================

V. Configuring and starting the Linux Dedicated Server

The command files for the Linux server are stored in the following folder:

Battlefield 2 - /BF2/Mods/BF2/Settings
Special Forces - /BF2/Mods/xpack/Settings

The files are called “serversettings.con” which holds all of the settings for the server, and “maplist.con” which contains all of the settings for which maps to load, what size and in which order to run them. These files may be opened and edited using any text editing program.

See Appendix D for a list of the server commands and their functions.

To add a map to the maplist, you must prefix each entry with the “maplist.append” command. The correct syntax for this command is as follows:

Maplist.append

<br /> <br /> For example, to add the map “Dalian Plant” to the maplist to run in 64 player Conquest mode the command would be as follows:<br /> <br /> Maplist.append dalian_plant gpm_cq 64<br /> <br /> Note that if the map size is not added to the end of the command, the map size will be taken from the “sv.MaxPlayers” value in the “serversettings.con” file. Adding a map size to the map list is useful for running small maps with larger numbers of players, for example running a 32 player map with 64 players. Note that this is not supported for Ranked servers and made lead to your server being removed from the Ranked Server Providers list if you do so.<br /> <br /> Please see Appendix A for a list of all of the map names and the supported sizes and game modes.<br /> <br /> It is recommended that you make a backup copy of your “serversettings.con” and “maplist.con” files in case you need to replace them at any time, or if you wish to quickly switch server configurations.<br /> <br /> To start the server, open the “BF2” folder and run “start.sh”. It is recommended you run the server in a terminal window to enable easier monitoring and control of the server.<br /> <br /> To start a Special Forces server, open the “BF2” folder and run “start.sh /xpack”.<br /> <br /> =====================================<br /> VI. Hosting a Battlefield 2™ Server<br /> =====================================<br /> <br /> In order to host a Battlefield 2™ server, you must have the following ports open in your firewall. <br /> <br /> UDP 27900<br /> UDP/TCP 29900<br /> TCP 80<br /> TCP 4711<br /> UDP 27901<br /> UDP 1500-4999<br /> UDP/TCP 1024-1124<br /> UDP 29900<br /> UDP/TCP 27900<br /> UDP 17567<br /> UDP 55123-55125<br /> UDP/TCP 18000<br /> UDP/TCP 18300<br /> <br /> Please note this is for a single server instance. Should you wish to run multiple instances on one host, all of the instances must run on unique ports.<br /> <br /> =================================<br /> VII. Remote Console (rcon) Access<br /> =================================<br /> <br /> To setup remote console access to the server:<br /> <br /> - On the server create a new plain text document in \admin\ called default.cfg<br /> <br /> - Enter the following text into the new file:<br /> <br /> port=4711<br /> password=YourPassword<br /> <br /> - Save the file, and start the server.<br /> <br /> To use Rcon while on the server, press the "Tilde" (~) key on your keyboard to open the console, and type the commands you wish to run in the following fashion:<br /> <br /> - rcon login <YourPassword><br /> Use this command to login to the server.<br /> <br /> - rcon users<br /> This command lists all the users connected to the server.<br /> Very similar to admin.listPlayers<br /> <br /> - rcon exec <command name><br /> Replace <command name> with a console command you would like to execute on the server.<br /> For example: rcon exec admin.kickPlayer 3<br /> <br /> ====================<br /> VIII. BattleRecorder<br /> ====================<br /> <br /> The Battlefield 2™ Server includes a facility called BattleRecorder. This records all of the gameplay for a particular round and makes it available for players in that round to download and view at a later date. There are two components to BattleRecorder, which are described below.<br /> <br /> To set up BattleRecorder on your server, follow the instructions below:<br /> <br /> The Dedicated Server requires the following information:<br /> <br /> - AutoRecord<br /> Set AutoRecord to on (sv.autorecord 1) to enable the BattleRecorder. Every round played on the server will now be recorded to a file.<br /> <br /> - DemoDownloadURL <http://YourServer.com/YourDirectory/><br /> This is the URL that will be passed to all the connected clients at the end of the round. This is the URL that the Battlefield 2™ front end will try and download the demo file from when the user selects 'download'. The demo file must be in the directory specified in the URL, or the demo download will fail. The URL specified here is case sensitive and must match exactly the URL of your web site.<br /> <br /> - AutoDemoHook <adminutils/demo/Your_Script.exe><br /> The server runs this script at the end of every round where AutoRecord is enabled. In the majority of cases the default script may be used.<br /> <br /> - DemoQuality <value><br /> You can control the quality of the recording made by the BattleRecorder. '1' is the default setting, and we recommend this is used for internet games. '10' is the highest setting, using this will increase the size of the file by around a factor of 8.<br /> Higher settings will also increase the load on the server.<br /> <br /> The second component to BattleRecorder is the script that is run when a round ends. This script can be rewritten or replaced as needed. The Battlefield 2™ server will simply attempt to execute the script specified in AutoDemoHook at the end of each round.<br /> <br /> The default script, called auto_rotate, was written in Python and then built in to an executable.<br /> <br /> The Python script can be found here \adminutils\demo\rotate_demo.py<br /> <br /> The script will move a BattleRecorder file from the server to a new local location, or to an FTP site. You can also specify the number of files to keep archived.<br /> <br /> The script is configured using a configuration file, called 'auto_rotate.cfg', found in the root of the Battlefield 2™ Server installation root directory.<br /> <br /> In this file you can configure:<br /> <br /> - file_limit = <value><br /> Use this value to set the number of BattleRecorder files you would like to keep available. The default is 30. Once the limit is reached, a new file will replace the oldest one.<br /> <br /> - target_root = <local directory path><br /> If you intend to transfer to a local directory, enter the path here.<br /> <br /> - use_ftp = <bool><br /> Set this to 1 if you wish to FTP the DemoRecorder file to a new location.<br /> <br /> - ftp_target_dir = <path to webroot demos><br /> Enter the path on the FTP site where you want the DemoRecording transferred to. Note this path is case sensitive and must match exactly the folder name of your FTP upload site.<br /> <br /> - ftp_server = <server URL or IP><br /> Enter the URL or IP of your FTP server. Again this is case sensitive and must match exactly the full URL of your FTP upload site.<br /> <br /> For example, if the URL of your web site is:<br /> <br /> “www.myftp.com/BF2/Demos”<br /> <br /> Then your “ftp_target_dir” should be “/BF2/Demos/” (without the quotes) and your “ftp_server” should be “ftp.myftp.com” (without the quotes). In the “serversettings.con” file or in the Server Launcher, your “DemoDownloadURL” should be “http://www.myftp.com/BF2/Demos/” (again without the quotes).<br /> <br /> - ftp_user = <FTP login username><br /> Enter your FTP sites login username.<br /> <br /> - ftp_password = <password><br /> Enter the password for your login account.<br /> <br /> ============================================<br /> IX. Points to note when using BattleRecorder<br /> ============================================<br /> <br /> BattleRecorder will significantly increase your server's load; therefore we do not recommend running 64 player games with the BattleRecorder feature enabled.<br /> <br /> BattleRecorder files become larger as you increase the number of players and the ticket allocation. For a round with 64 players with 250 tickets on each side, you should expect a file size of around 10-12 Mb with the DemoQuality set to 1.<br /> <br /> When you download a BattleRecorder file, using the 'Community' function in the Battlefield 2™ front end, it is saved in:<br /> <br /> \My Documents\Battlefield 2\Profiles\Default\Demos\<br /> <br /> Every profile on your computer will save BattleRecorder files to this location.<br /> <br /> It is possible to download BattleRecorder files from a friend or website and copy them into the BattleRecorder directory above. They will then appear on the 'Community' page for you to play.<br /> <br /> =====================<br /> X. Remote VOIP Server<br /> =====================<br /> <br /> Battlefield 2™ Server includes a remote VOIP server. This is included to run as a standalone VOIP server to remove the need for the game server to handle VOIP as well as the game.<br /> <br /> To use the remote VOIP server, install the Battlefield 2™ Dedicated Server onto the PC you wish to use as a remote VOIP server. There are two files to pay attention to:<br /> <br /> BF2VoipServer_w32ded.exe - The server executable.<br /> voip.con - The remote server configuration file.<br /> <br /> To set up the server, open the "voip.con" file and edit the entries to support your game server setup. The syntax is as follows:<br /> <br /> <port> <password> <game server interface IP><br /> <br /> 55125 no_password 123.123.123.123<br /> <br /> Note that it is only necessary to include the game server interface IP if you are connecting multiple game servers to a single remote VOIP server, for example:<br /> <br /> 55125 no_password 123.123.123.123<br /> 55126 no_password 123.123.123.124<br /> 55127 no_password 123.123.123.125<br /> <br /> Also note that all game servers that connect to a remote VOIP server must do so over unique ports.<br /> <br /> ==========================================<br /> XI. Appendix A – Map Names, Sizes & Modes<br /> ==========================================<br /> <br /> - Dalian Plant<br /> Map name – dalian_plant<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Daqing Oilfields<br /> Map name – daqing_oilfields<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Dragon Valley<br /> Map name – dragon_valley<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - FuShe Pass<br /> Map name – fushe_pass<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Gulf of Oman<br /> Map name – gulf_of_oman<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Kubra Dam<br /> Map name – kubra_dam<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Mashtuur City<br /> Map name – mashtuur_city<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Operation Clean Sweep<br /> Map name – operation_clean_sweep<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Sharqi Peninsula<br /> Map name – sharqi_peninsula<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Songhua Stalemate<br /> Map name – songhua_stalemate<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Strike at Kerkand<br /> Map name – strike_at_karkand<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Zatar Wetlands<br /> Map name – zatar_wetlands<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> ===========<br /> Euro Forces<br /> ===========<br /> <br /> - Great Wall<br /> Map name – greatwall<br /> Sizes – 16, 32<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Operation Smoke Screen<br /> Map name – operationsmokescreen<br /> Sizes – 16, 32<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Taraba Quarry<br /> Map name – taraba_quarry<br /> Sizes – 16, 32<br /> Modes – gpm_coop, gpm_cq<br /> <br /> ============<br /> Armored Fury<br /> ============<br /> <br /> - Midnight Sun<br /> Map name – midnight_sun<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Operation Harvest<br /> Map name – operationharvest<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Operation Road Rage<br /> Map name – operationroadrage<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> ===============<br /> Additional Maps<br /> ===============<br /> <br /> - Wake Island 2007<br /> Map name – wake_island_2007<br /> Sizes – 64<br /> Modes – gpm_cq<br /> <br /> - Road to Jalalabad<br /> Map name – road_to_jalalabad<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Highway Tampa<br /> Map name – highway_tampa<br /> Sizes – 16, 32, 64<br /> Modes – gpm_cq<br /> <br /> ==============<br /> Special Forces<br /> ==============<br /> <br /> - Devils Perch<br /> Map name – devils_perch<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Ghost Town<br /> Map name – ghost_town<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Iron Gator<br /> Map name – iron_gator<br /> Sizes – 16, 32, 64<br /> Modes – gpm_cq<br /> <br /> - Leviathan<br /> Map name – leviathan<br /> Sizes – 16, 32, 64<br /> Modes – gpm_cq<br /> <br /> - Mass Destruction<br /> Map name – mass_destruction<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Night Flight<br /> Map name – night_flight<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Surge<br /> Map name – surge<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> - Warlord<br /> Map name – warlord<br /> Sizes – 16, 32, 64<br /> Modes – gpm_coop, gpm_cq<br /> <br /> ==================================<br /> XII. Appendix B – Useful commands<br /> ==================================<br /> <br /> To view all the available server commands, once the server has started, in the console press the “Tab” key twice. This will display all of the server command roots, such as “sv.” and “admin.”. To view each command subset, type a root command followed by pressing the “Tab” key twice, for example type “sv.” then “tab” twice (minus the quotes).<br /> <br /> ================<br /> Maplist Commands<br /> ================<br /> <br /> - mapList.list<br /> Every map on the server has an ID number, which is used for voting to change maps. This command lists those numbers, the map name, game mode and the number of players if specified.<br /> <br /> - mapList.configFile <new location for file><br /> Used to specify the location of the _mapList.con<br /> The default is \My Documents\Battlefield 2\ServerConfigs\<br /> <br /> - mapList.mapCount<br /> Shows the total number of maps in the current map list<br /> <br /> - mapList.currentMap<br /> Shows the map list ID number of the current map being played<br /> <br /> - mapList.clear<br /> Clears the current map list.<br /> Warning: If there are no maps in the map list when the server starts loading a new map, all clients will be left on the loading screen.<br /> <br /> - mapList.remove 

<map ID number>
  <br /> Removes the map you specify from the map list<br /> <br /> - mapList.append 
  
  <map name>
    <game mode> [number of players]<br /> Add a new map to the end of the map list.<br /> You must specify the map name and the game mode. Number of players is optional, if not specified will default to the current server setting.<br /> <br /> - mapList.insert 
    
    <map ID number>
      <map name>
        <game mode> [number of players]<br /> Exactly the same as mapList.append, but with this command you can specify at what map ID number to insert the new map into the list at.<br /> <br /> ==============<br /> Admin Commands<br /> ==============<br /> <br /> - admin.listPlayers<br /> Lists the players connected to the server.<br /> This command lists the players ID number, their player name and if the player is remote it also lists the players IP number.<br /> <br /> - admin.runNextLevel<br /> Forces the server to end the round and start the next map in the map list.<br /> <br /> - admin.currentLevel<br /> Shows the map list ID number for the current map being played.<br /> The same as mapList.currentMap.<br /> <br /> - admin.nextLevel 
        
        <map ID number>
          <br /> This allows you to set which map to run next in the rotation.<br /> <br /> - admin.restartMap<br /> Restarts the current map.<br /> <br /> - admin.banPlayer <player ID number> [timeout]<br /> Enter the player ID number you would like to ban. Bans the player from this server by using their IP address.<br /> Bans can be set on CD key hashes.<br /> Bans are stored as absolute times in banlist.con. Existing bans in banlist.con will be interpreted as permanent bans.<br /> You can choose from a selection of time outs:<br /> Entering 'perm' means that the ban is permanent. This is the default if no time out is entered.<br /> An integral number meaning the number of seconds the ban will be active (i.e. 3600 means one hour).<br /> Entering 'round' means the ban is active until the next map.<br /> A whole number preceded by a colon (i.e. :1234567), meaning the epoch expiration time of the ban (number of seconds since 1 Jan 1970).<br /> <br /> - admin.banPlayerKey <player ID number> [timeout]<br /> Enter the player ID number you would like to ban. Bans the player from this server by using their CD key hash.<br /> You can also specify a time out. See admin.banPlayer for the time out list.<br /> <br /> - admin.addAddressToBanList <IP address> [timeout]<br /> Enter the IP number you would like to ban.<br /> You can also specify a time out. See admin.banPlayer for the time out list.<br /> <br /> - admin.addKeyToBanList <CD key hash> [timeout]<br /> Enter the CD key hash you would like to ban.<br /> You can also specify a time out. See admin.banPlayer for the time out list.<br /> <br /> - admin.removeAddressFromBanList <IP address><br /> Enter the IP address you would like to remove from the ban list.<br /> <br /> - admin.removeKeyFromBanList <CD key hash><br /> Enter the CD key hash you would like to remove from the ban list. <br /> <br /> - admin.clearBanList<br /> Clears all ban lists.<br /> <br /> - admin.listBannedAddresses<br /> Displays a list of the currently banned IP addresses.<br /> <br /> - admin.listBannedKeys<br /> Displays a list of the currently banned CD keys.<br /> <br /> - admin.kickPlayer <player ID number><br /> Enter the ID number of the player you would like to kick.<br /> <br /> =======================================<br /> XIII. Appendix C - Hardware Requirements<br /> =======================================<br /> <br /> We highly recommend Battlefield 2™ servers are run on dedicated server platforms. Currently, the best performance is on a machine with the following specifications:<br /> <br /> =====<br /> LINUX<br /> ===== <br /> <br /> - Minimum Specification, based on playing a 16 player game:<br /> CPU: 1 Ghz<br /> RAM: 256 Mb<br /> <br /> - Recommended Specification, based on playing a 64 player game:<br /> CPU: 3 Ghz. For AMD Athlon 64 CPU: 3500+ (2.2 Ghz)<br /> RAM: 2 Gb<br /> <br /> - Recommended Specification, based on playing a 48 player Titan game:<br /> CPU: 3.6 Ghz. For AMD Athlon 64 CPU: 4800+<br /> RAM: 2 Gb<br /> <br /> - Optimal Specification, based on playing a 64 player Conquest game:<br /> Only run one instance of BF2 per physical CPU with Hyperthreading disabled<br /> CPU: AMD Athlon 64 4800+ or 3.6GHz Xeon.<br /> RAM: 2Gb per physical CPU<br /> <br /> - Optimal Specification, based on playing a 48 player Titan game:<br /> Only run one instance of BF2 per physical CPU with Hyperthreading disabled<br /> CPU: AMD Athlon 64 4800+ or 3.8GHz Xeon.<br /> RAM: 2Gb per physical CPU<br /> <br /> =======<br /> WINDOWS<br /> =======<br /> <br /> - Minimum Specification, based on playing a 16 player game:<br /> CPU: 1 Ghz<br /> RAM: 384 Mb<br /> <br /> - Recommended Specification, based on playing a 64 player game:<br /> CPU: 3 Ghz. For AMD Athlon 64 CPU: 3500+ (2.2 Ghz)<br /> RAM: 2 Gb<br /> <br /> - Optimal Specification based on playing a 64 player Conquest or game:<br /> Only run one instance of BF2 per physical CPU with Hyperthreading disabled<br /> CPU: AMD Athlon 64 4800+ or 3.66GHz Xeon.<br /> RAM: 2Gb per physical CPU<br /> <br /> =========<br /> BANDWIDTH<br /> =========<br /> <br /> - Minimum<br /> 2.5 Mbit<br /> <br /> - Recommended<br /> 5Mbit<br /> <br /> Note that the server requires more upstream bandwidth (server to client) than downstream (client to server). The above bandwidth recommendations are upstream speeds.<br /> <br /> As always if you can increase any of the above hardware you will improve your overall gameplay experience.<br /> <br /> ========<br /> FIREWALL<br /> ========<br /> <br /> The use of a software firewall on the server is not recommended, as it can adversely affect server performance and the overall gameplay experience.<br /> <br /> ====================================================<br /> XIV. Appendix D - Server settings and their functions<br /> ====================================================<br /> <br /> Note that the following commands are prefixed "sv." when use in the serversettings.con file or server console on both Windows and Linux.<br /> <br /> - ServerName – This is the name that the server will display in the server browser.<br /> <br /> - Password – This allows you to set a password for the server. Note that Ranked servers cannot be password protected.<br /> <br /> - Internet – Check this box to have the server display in the “Multiplay” menu in the 2142 client. Ranked servers must have this option checked.<br /> <br /> - Ranked – This sets whether or not the server will use the official Ranking system and send end of round scores to the backend stats system. To run a Ranked server the server IP address must be listed in the Ranked Server Providers list – contact your server provider for this facility.<br /> <br /> - WelcomeMessage – This allows you to enter text that will be displayed on the server info window while the client is loading the map.<br /> <br /> - ServerIP – This sets the IP address that the server will display to the client. This is primarily for servers that have a front-end game IP and a back-end admin IP.<br /> <br /> - ServerPort – This is the port that the clients will use to communicate with the server. Note that if multiple server instances are run on the same host PC, this value must be unique to each instance. Recommended range is from the default 16567 to 16570.<br /> <br /> - AllowFreeCam – This setting allows the player to use the free camera mode while waiting to spawn into the game (press Space on the spawn screen to activate).<br /> <br /> - AllowExternalViews – This allows the players to switch between the normal internal view and the various external views while in vehicles.<br /> <br /> - AllowNoseCam – This allows the player to use the nose camera (eliminating the vehicle model) while in aircraft.<br /> <br /> - HitIndicator – This setting controls whether the hit indicator will be displayed to the clients when shooting enemy targets.<br /> <br /> - MaxPlayers – This sets how many players will be allowed to join the server. It also sets the map size that will be loaded in Conquest mode. Note the maximimum number of players in Titans Mode is 48. In Cooperative mode this value sets the amount of bots to load. As human players join bots will be removed on a one for one basis.<br /> <br /> - NumPlayersNeededToStart – How many players need to be connected to the server before the round starts. This setting has mandatory values for Ranked servers – 6 players for a 16 player server, 6 for 32 player and 8 for 48/64 player.<br /> <br /> - NotEnoughPlayersRestartDelay – This sets how long the round will continue if the number of players falls below the value set above. Once this time has expired the server will end the round.<br /> <br /> - CoopBotRatio - This detemines the percentage of total bots that will be on team 1 which is the MEC and Chinese. This setting does not affect human players.<br /> <br /> - CoopBotCount - This specifies the total number of bots that will spawn in a Coop game. This does not affect the number of human players.<br /> <br /> - CoopBotDifficulty - This determines how tough the bots are in Coop mode with 10 being the easiest, 50 being medium and 100 being the hardest.<br /> <br /> - NoVehicles - This sets the server in "Infantry Only" mode and removes all vehicles except boats. Boats are excluded to allow gameplay on maps like Wake Island.<br /> <br /> - StartDelay – this sets the time period between the required number of players joining the server and the round starting (this will be displayed to the clients as the “Commander Election” period).<br /> <br /> - EndDelay – This sets the time period between the round ending and the server rotating to the next round/map.<br /> <br /> - SpawnTime – How long a player must wait before respawning. The default 15 seconds is mandatory on Ranked servers and cannot be changed.<br /> <br /> - ManDownTime – The time period during which a player may be revived. This value must be lower than the SpawnTime value. Again this is a mandatory 15 seconds on Ranked servers.<br /> <br /> - TicketRatio – How many tickets each team will have. Note this is a percentage figure, not how many actual tickets each team has. The actual number of tickets is set by the map size and the game mode, for example on Conquest: Assault maps where one team has an uncapturable base, that team will start with less tickets than the team with no uncap. The default value of 100 is mandatory on Ranked servers. This value has no bearing on gpm_ti game modes.<br /> <br /> - RoundsPerMap – How many rounds will be played on each map before loading the next map.<br /> <br /> - TimeLimit – This value (in minutes) sets how long the round will last before ending. The round can still be ended normally if one team loses all of its tickets or its Titan is destroyed. Note that time limits may not be used on Ranked servers. Also note that this value is listed in seconds in the "serversettings.con" file on Linux servers. Time limits may not be set on gpm_ti game modes.<br /> <br /> - SoldierFriendlyFire – A percentage value of how much damage will be caused by direct infantry weapon fire to players on the same team.<br /> <br /> - VehicleFriendlyFire - A percentage value of how much damage will be caused by direct vehicle weapon fire to players on the same team.<br /> <br /> - SoldierSplashFriendlyFire - A percentage value of how much damage will be caused by indirect infantry weapon fire to players on the same team.<br /> <br /> - VehicleSplashFriendlyFire - A percentage value of how much damage will be caused by indirect infantry weapon fire to players on the same team.<br /> <br /> - TkPunishEnabled – Controls whether or not the punish system for team killing is on or off.<br /> <br /> - TkNumPunishToKick – The number of times a player may be punished for team kills before being automatically kicked from the server.<br /> <br /> - TkPunishByDefault – This setting will automatically punish players for teamkilling if the victim does not choose to punish or forgive.<br /> <br /> - VotingEnabled – Controls whether or not players may vote for map changes, commander mutiny and player kicks.<br /> <br /> - VoteTime – The time (in seconds) that a vote will last for before the result is applied.<br /> <br /> - MinPlayersForVoting – How many players are required to vote for the vote to be successful.<br /> <br /> - VoipEnabled – Controls whether or not the Voice Over IP system will be used by the clients.<br /> <br /> - VoipServerRemote – Controls whether or not the server will use its own in-built Voip system or the Battlefield Remote VOIP Server.<br /> <br /> - VoipServerRemoteIP – The IP address of the remote VOIP server, if one is to be used.<br /> <br /> - VoipServerPort – The port used by the server to control VOIP<br /> <br /> - VoipBFClientPort – The VOIP port used by the clients to communicate.<br /> <br /> - VoipBFServerPort – The VOIP port the server uses to resend messages on to the clients. <br /> <br /> Note – all the above ports must be unique if more than one instance is hosted on one PC.<br /> <br /> - VoipSharedPassword – The password set on a remote VOIP server. This will be communicated by the server to the clients to enable them to use the remote server.<br /> <br /> - VoipQuality – This sets how much bandwidth will be allocated to ensure good VOIP communication.<br /> <br /> - GameSpyPort – The port over which the server will communicate with the GameSpy back-end system. Again this must be unique for multiple instances on a common host. It is recommended to stay between the default port 29900 and port 29950.<br /> <br /> - AllowNATNegotiation – This determines whether or not clients behind a NAT enabled router or firewall will be able to join the server. In 99% of cases this setting is not needed.<br /> <br /> - InterfaceIP – This is used to communicate with the remote VOIP server. This IP must be set in the "voip.con" file if multiple servers are to use the same remote VOIP server.<br /> <br /> - AutoBalanceTeam – Determines whether or not the server will force the teams to be even.<br /> <br /> - TeamRatioPercent – This is a percentage value of how many players need to be on each team before the server considers the teams even. The default value of 100 will split the players evenly across both teams.<br /> <br /> - AutoRecord – Enables the BattleRecorder feature.<br /> <br /> - DemoDownloadURL – This is the URL for the website where the BattleRecorder demo files will be stored. This is communicated to the clients so they can retrieve the demos.<br /> <br /> - AutoDemoHook – Leave as default unless you are very familiar with the python scripting language.<br /> <br /> - DemoQuality – This sets the quality of the recording.<br /> <br /> - AdminScript – Allows the use of custom python scripts for server administration. Leave as default if you are not familiar with the python scripting language.<br /> <br /> - SponsorLogoURL – The URL of an image that will be displayed in the server info window in the server browser when the server is highlighted.<br /> <br /> - CommunityLogoURL – The URL of an image that will be displayed in the server info window while the client loads the map.<br /> <br /> - PunkBuster – Determines whether or not the PunkBuster anti-cheat system will be used. This is mandatory for Ranked servers. Visit www.evenbalance.com for more info on PunkBuster.<br /> <br /> - UseGlobalRank – Determines whether or not players ranks will be displayed in-game. This setting is always set to on for Ranked servers.<br /> <br /> - UseGlobalUnlocks - Determines whether or not players will be allowed to use items they have unlocked on Ranked servers. This setting is always "on" for Ranked servers and cannot be turned off.<br /> <br /> - NumReservedSlots – Determines the number of reserved player slots on the server. The player nicknames that are allowed to use these reserved slots are listed in the file “reservedslots.con” in the "settings" folder of the server install (this file needs to be created manually). <br /> <br /> - FriendlyFireWithMines - When set to off, this prevents mines and claymores from being detonated by friendly players and vehicles.<br /> <br /> ==================<br /> XV. Version Notes<br /> ==================<br /> <br /> v1.50<br /> <br /> - Various changes made to prevent cheating.<br /> - Added checks to prevent "runway grieving"<br /> - Added Highway Tampa to the default build to make it a compulsory update.<br /> - Added the new map Operation Blue Pearl.<br /> - Special thanks to Blackbird at the TV2 community www.battle.no <br /> <br /> v1.41<br /> <br /> - Fixed an extremely intermittent server crash bug.<br /> <br /> v1.4<br /> <br /> - Added a new map, Road to Jalalabad.<br /> - Fixed the Linux server hangs when trying to load a Special Forces Co-Op map.<br /> - Fixed a crash in Co-op after a player is revived without a kit.<br /> - Fixed a server crash on Linux 32 when trying to rotate maps in Coop Mode.<br /> - Adjusted the minimum number of players to start the round on ranked servers. <br /> The new values for 16, 32 and 64 players are 6, 8 and 8 respectively.<br /> - Re-enabled unlocks on unranked servers.<br /> - Ranked Servers now force unlocks.<br /> - Added support for multiple gamemodes in single maplist for mods.<br /> <br /> v1.3<br /> <br /> - Added support for Armored Fury booster pack<br /> - Co-op: <br /> Co-op Mode allows you to play Single Player levels on the Internet and LAN with both AI controlled bots and human players. Several new options have been created that will allow the server creator to modify how the bots behave in game.<br /> Number of Bots: This setting allows you to determine the total number of bots that will spawn in game.<br /> <br /> Bot Ratio: This setting allows you to determine the percentage of total bots that will spawn for each team. For example, setting this value to 25 means that 25% of the total bots will spawn in Team 1, and 75% in Team 2. Team 1 is always the MEC, Chinese, or their allies, while Team 2 is always the USA, EU, and their allies.<br /> <br /> Bot Difficulty: This setting determines the skill level of the bots. 10 is easiest, 100 is the most difficult.<br /> <br /> - Fixed issues with remote console and linux server<br /> <br /> v1.22<br /> <br /> - Improved Server Stability<br /> - Various client side fixes<br /> <br /> v1.21<br /> <br /> - Fixed the Hmmwv with TOW crash on Battlefield 2: Special Forces maps<br /> - Fixed the Battle Recorder crash<br /> - Fixed the error in Client - Server communication causing sound, animation and other sync issues.<br /> <br /> v1.2<br /> <br /> - Added support for Euro Forces booster pack<br /> <br /> v1.12<br /> <br /> - Improved server stability<br /> - Various client side fixes<br /> <br /> v1.03<br /> <br /> - Added a new map, Wake Island 2007<br /> - Added reserved slot functionality<br /> - Changed automatic TK banning to ban by cd-key instead of IP address<br /> - Fixed a crash in the Ranked Linux server when communication with stats <br /> back-end ceased.<br /> <br /> v1.02<br /> <br /> - Fixed a server memory leak<br /> <br /> v1.01<br /> <br /> - Various client side fixes