Battlefield 2142™ Dedicated Server Readme v3.5
11th January 2007
Copyright Electronic Arts
Battlefield 2142™ v1.20

=================
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 2142™ Server
VII.	Remote Console (rcon) Access
VIII.	BattleRecorder
IX.	Points to note when using BattleRecorder
X.	Remote VOIP Server
XI.	Min & Max unlocks commands
XII.	Appendix A – Map Names, Sizes & Modes
XIII.	Appendix B – Useful commands
XIV.	Appendix C - Hardware Requirements
XV.	Appendix D - Server settings and their functions
XVI.	Version notes

==========================================
I. Installing the Windows Dedicated Server
==========================================

To install the server, double click the “Battlefield 2142 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 2142 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 (BF2142_w32ded.exe) and applying startup parameters to it. The syntax for the parameters are as follows:

+config <path to serversettings.con file>
+mapList <path to maplist.con file>"
+Provider "<your provider name>"
+region "<your region>"
+type <0 or 1>

Example:

"C:\Program Files\Electronic Arts\Battlefield 2142 Server\BF2142_w32ded.exe" +config C:\serversettings.con +mapList C:\maplist.con +provider "EA" +region "UK" +type 0

This setup is designed primarily for Ranked Server Partners. For individual servers it is more convenient to use the Server Launcher. Note that the parameters +provider, +region and +type are only required if the server is to run Ranked; they are not necessary for Unranked servers.

=================
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_ti – Titans
Gpm_coop – Cooperative
Gpm_sl - Assault Lines

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.

Note that the maximum supported number of players for Titans mode is 48. While it is possible to include up to 64 players this is not supported and not recommended.

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/<user>/. The server will automatically create a folder called “BF2142” 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:

<install path>/BF2142/Mods/BF2142/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 <map name> <game mode> <map size>

For example, to add the map “Sidi Power Plant” to the maplist to run in 64 player Conquest mode the command would be as follows:

Maplist.append sidi_power_plant gpm_cq 64

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.

Please see Appendix A for a list of all of the map names and the supported sizes and game modes.

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.

To start the server, open the “BF2142” 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.

When using the Ranked server code, it is necessary to add the following parameters to your start up command:

+provider ""
+region ""
+type 0 or 1 (0 for Ranked servers)

For example:

./start.sh +provider "Electronic Arts" +region "UK" +type 0

If these parameters are not set the server will not run Ranked and will close when a player tries to join it. Note that these parameters are only required if the server is to run Ranked; they are not necessary for Unranked servers.

=====================================
VI. Hosting a Battlefield 2142™ Server
=====================================

In order to host a Battlefield 2142™ server, you must have the following ports open in your firewall.

UDP		27900
UDP/TCP 	29900
TCP    		80
TCP     	4711
UDP     	27901
UDP     	1500-4999
UDP/TCP 	1024-1124
UDP     	29900
UDP/TCP 	27900
UDP     	17567
UDP     	55123-55125
UDP/TCP		18000
UDP/TCP		18300

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.

=================================
VII. Remote Console (rcon) Access
=================================

To setup remote console access to the server:

- On the server create a new plain text document in \admin\ called default.cfg

- Enter the following text into the new file:

port=4711
password=YourPassword

- Save the file, and start the server.

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:

- rcon login <YourPassword>
Use this command to login to the server.

- rcon users
This command lists all the users connected to the server.
Very similar to admin.listPlayers

- rcon exec <command name>
Replace <command name> with a console command you would like to execute on the server.
For example: rcon exec admin.kickPlayer 3

====================
VIII. BattleRecorder
====================

The Battlefield 2142™ 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.

To set up BattleRecorder on your server, follow the instructions below:

The Dedicated Server requires the following information:

- AutoRecord
Set AutoRecord to on (sv.autorecord 1) to enable the BattleRecorder. Every round played on the server will now be recorded to a file.

- DemoDownloadURL <http://YourServer.com/YourDirectory/>
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 2142™ 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.

- AutoDemoHook <adminutils/demo/Your_Script.exe>
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.

- DemoQuality <value>
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.
Higher settings will also increase the load on the server.

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 2142™ server will simply attempt to execute the script specified in AutoDemoHook at the end of each round.

The default script, called auto_rotate, was written in Python and then built in to an executable.

The Python script can be found here \adminutils\demo\rotate_demo.py

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.

The script is configured using a configuration file, called 'auto_rotate.cfg', found in the root of the Battlefield 2142™ Server installation root directory.

In this file you can configure:

- file_limit = <value>
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.

- target_root = <local directory path>
If you intend to transfer to a local directory, enter the path here.

- use_ftp = <bool>
Set this to 1 if you wish to FTP the DemoRecorder file to a new location.

- ftp_target_dir = <path to webroot demos>
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.

- ftp_server = <server URL or IP>
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.

For example, if the URL of your web site is:

“www.myftp.com/BF2142/Demos”

Then your “ftp_target_dir” should be “/BF2142/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/BF2142/Demos/” (again without the quotes).

- ftp_user = <FTP login username>
Enter your FTP sites login username.

- ftp_password = <password>
Enter the password for your login account.

============================================
IX. Points to note when using BattleRecorder
============================================

BattleRecorder will significantly increase your server's load; therefore we do not recommend running 64 player games with the BattleRecorder feature enabled.

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.

When you download a BattleRecorder file, using the 'Community' function in the Battlefield 2142™ front end, it is saved in:

\My Documents\Battlefield 2142\Profiles\Default\Demos\

Every profile on your computer will save BattleRecorder files to this location.

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.

=====================
X. Remote VOIP Server
=====================

Battlefield 2142™ 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.

To use the remote VOIP server, install the Battlefield 2142™ Dedicated Server onto the PC you wish to use as a remote VOIP server. There are two files to pay attention to:

BF2142VoipServer_w32ded.exe - The server executable.
voip.con - The remote server configuration file.

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:

<port> <password> <game server interface IP>

55125 no_password 123.123.123.123

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:

55125 no_password 123.123.123.123
55126 no_password 123.123.123.124
55127 no_password 123.123.123.125

Also note that all game servers that connect to a remote VOIP server must do so over unique ports.

==============================
XI. Min & Max unlocks commands
==============================

Thes commands can only be used on Unranked dedicated servers and allow the server admin to grant or restrict the use of unlocks, whether or not those unlocks have been earned by the player on a Ranked server.

The syntax for minimum unlocks is as follows:

sv.MinUnlockLevel <value>

The value range is 0 to 1. Each value has the following effect:

 0 – Players will not be given any unlocks unless they have earned them on a ranked server.
 1 – Players will receive the first tier of kit unlocks, the first player ability unlock and the first squad leader unlocks.

The syntax for maximum unlocks is as follows:

sv.MaxUnlockLevel <value>

The value range is -1 to 5. Each value has the following effect:

-1 – Turns off the feature.
 0 – Players have no unlocks regardless of how many they have earned on ranked servers.
 1 – Players are limited to the first tier kit unlocks, first ability unlock and first squad leader unlock that they have received from playing ranked servers.
 2 – Players are limited to the second tier kit unlocks, second ability and second squad leader unlock that they have received from playing ranked servers.
 3 – Players are limited to the third tier kit unlocks, third ability and final squad leader unlock that they have received from playing ranked servers.
 4 – Players are limited to the final tier of kit unlocks and fourth ability that they have received from playing ranked servers.
 5 – Players are able to use all the unlocks that they have received from playing on ranked servers.

These settings cannot be adjusted while the server is running.

Note: sv.MinUnlockLevel takes precedent over sv.MaxUnlockLevel. For example if sv.MinUnlockLevel is set to 1 and sv.MaxUnlockLevel is set to 0, players will receive all tier 1 unlocks.


==========================================
XII. Appendix A – Map Names, Sizes & Modes
==========================================

- Shuhia Taiba
Map name – shuhia_taiba
Sizes – 16, 32, 64
Modes – gpm_ti (48), gpm_cq

- Minsk
Map name – minsk
Sizes – 16, 32, 64
Modes – gpm_ti (48), gpm_cq

- Suez Canal
Map name – suez_canal
Sizes – 16, 32, 64
Modes – gpm_ti (48), gpm_cq, gpm_coop

- Verdun
Map name – verdun
Sizes – 16, 32, 64
Modes – gpm_ti (48), gpm_cq, gpm_coop

- Camp Gibraltar
Map name – camp_gibraltar
Sizes – 16, 32
Modes – gpm_cq

- Tunis Harbor
Map name – tunis_harbor
Sizes – 16, 32
Modes – gpm_cq

- Sidi Power Plant
Map name – sidi_power_plant
Sizes – 16, 32, 64
Modes – gpm_ti (48), gpm_cq, gpm_coop

- Belgrade
Map name – belgrade
Sizes – 16, 32
Modes – gpm_cq, gpm_coop

- Fall of Berlin
Map name – fall_of_berlin
Sizes – 16, 32, 64
Modes – gpm_cq, gpm_coop

- Cerbére Landing
Map name – cerbere_landing
Sizes – 16, 32
Modes – gpm_cq, gpm_coop

===================
Booster Pack 1 Maps
===================

- Port Bavaria
Map name - port_bavaria
Sizes - 16, 32, 64
Modes gpm_sl, gpm_ti (48)

- Bridge at Remagen
Map name - bridge_at_remagen
Sizes - 16, 32, 64
Modes gpm_sl, gpm_ti (48)

- Liberation of Leipzig
Map name - liberation_of_leipzig
Sizes - 16, 32, 64
Modes gpm_sl

Note - Titans Mode has a maximum supported player limit of 48.

==================================
XIII. Appendix B – Useful commands
==================================

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).

================
Maplist Commands
================

- mapList.list
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.

- mapList.configFile <new location for file>
Used to specify the location of the _mapList.con
The default is \My Documents\Battlefield 2142\ServerConfigs\

- mapList.mapCount
Shows the total number of maps in the current map list

- mapList.currentMap
Shows the map list ID number of the current map being played

- mapList.clear
Clears the current map list.
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.

- mapList.remove <map ID number>
Removes the map you specify from the map list

- mapList.append <map name> <game mode> [number of players]
Add a new map to the end of the map list.
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.

- mapList.insert <map ID number> <map name> <game mode> [number of players]
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.

==============
Admin Commands
==============

- admin.listPlayers
Lists the players connected to the server.
This command lists the players ID number, their player name and if the player is remote it also lists the players IP number.

- admin.runNextLevel
Forces the server to end the round and start the next map in the map list.

- admin.runLevel
This will add a specified map to the maplist and immediately rotate the server to that map. For example:

admin.runLevel minsk gpm_ti 48

The above example will append 48 player Minsk Titans to the end of the maplist, end the current round and load this map instead.

- admin.currentLevel
Shows the map list ID number for the current map being played.
The same as mapList.currentMap.

- admin.nextLevel <map ID number>
This allows you to set which map to run next in the rotation.

- admin.restartMap
Restarts the current map.

- admin.banPlayer <player ID number> [timeout]
Enter the player ID number you would like to ban. Bans the player from this server by using their IP address.
Bans can be set on CD key hashes.
Bans are stored as absolute times in banlist.con. Existing bans in banlist.con will be interpreted as permanent bans.
You can choose from a selection of time outs:
Entering 'perm' means that the ban is permanent. This is the default if no time out is entered.
An integral number meaning the number of seconds the ban will be active (i.e. 3600 means one hour).
Entering 'round' means the ban is active until the next map.
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).

- admin.banPlayerKey <player ID number> [timeout]
Enter the player ID number you would like to ban. Bans the player from this server by using their CD key hash.
You can also specify a time out. See admin.banPlayer for the time out list.

- admin.addAddressToBanList <IP address> [timeout]
Enter the IP number you would like to ban.
You can also specify a time out. See admin.banPlayer for the time out list.

- admin.addKeyToBanList <CD key hash> [timeout]
Enter the CD key hash you would like to ban.
You can also specify a time out. See admin.banPlayer for the time out list.

- admin.removeAddressFromBanList <IP address>
Enter the IP address you would like to remove from the ban list.

- admin.removeKeyFromBanList <CD key hash>
Enter the CD key hash you would like to remove from the ban list.

- admin.clearBanList
Clears all ban lists.

- admin.listBannedAddresses
Displays a list of the currently banned IP addresses.

- admin.listBannedKeys
Displays a list of the currently banned CD keys.

- admin.kickPlayer <player ID number>
Enter the ID number of the player you would like to kick.

=======================================
XIV. Appendix C - Hardware Requirements
=======================================

We highly recommend Battlefield 2142™ servers are run on dedicated server platforms. Currently, the best performance is on a machine with the following specifications:

=====
LINUX
=====

- Minimum Specification, based on playing a 16 player game:
  CPU: 1 Ghz
  RAM: 256 Mb

- Recommended Specification, based on playing a 64 player game:
  CPU: 3 Ghz. For AMD Athlon 64 CPU: 3500+ (2.2 Ghz)
  RAM: 2 Gb

- Recommended Specification, based on playing a 48 player Titan game:
  CPU: 3.6 Ghz. For AMD Athlon 64 CPU: 4800+
  RAM: 2 Gb

- Optimal Specification, based on playing a 64 player Conquest game:
  Only run one instance of BF2142 per physical CPU with Hyperthreading disabled
  CPU: AMD Athlon 64 4800+ or 3.6GHz Xeon.
  RAM: 2Gb per physical CPU

- Optimal Specification, based on playing a 48 player Titan game:
  Only run one instance of BF2142 per physical CPU with Hyperthreading disabled
  CPU: AMD Athlon 64 4800+ or 3.8GHz Xeon.
  RAM: 2Gb per physical CPU

=======
WINDOWS
=======

- Minimum Specification, based on playing a 16 player game:
  CPU: 1 Ghz
  RAM: 384 Mb

- Recommended Specification, based on playing a 64 player game:
  CPU: 3 Ghz. For AMD Athlon 64 CPU: 3500+ (2.2 Ghz)
  RAM: 2 Gb

- Recommended Specification, based on playing a 48 player Titan game:
  CPU: 3.6 Ghz. For AMD Athlon 64 CPU: 4800+
  RAM: 2 Gb

- Optimal Specification based on playing a 64 player Conquest or game:
  Only run one instance of BF2142 per physical CPU with Hyperthreading disabled
  CPU: AMD Athlon 64 4800+ or 3.66GHz Xeon.
  RAM: 2Gb per physical CPU

- Optimal Specification, based on playing a 48 player Titan game:
  Only run one instance of BF2142 per physical CPU with Hyperthreading disabled
  CPU: AMD Athlon 64 4800+ or 3.8GHz Xeon.
  RAM: 2Gb per physical CPU

=========
BANDWIDTH
=========

- Minimum
  2.5 Mbit

- Recommended
  5Mbit

Note that the server requires more upstream bandwidth (server to client) than downstream (client to server). The above bandwidth recommendations are upstream speeds.

As always if you can increase any of the above hardware you will improve your overall gameplay experience.

========
FIREWALL
========

The use of a software firewall on the server is not recommended, as it can adversely affect server performance and the overall gameplay experience.

====================================================
XV. Appendix D - Server settings and their functions
====================================================

- Exe – this sets which executable the server will use to run. For normal operations leave this as “BF2142_w32ded.exe”

- Provider - The name of your organisation.

- Region - The area where the server is located, eg UK or US.

- Type - Set this to 0 (zero) for Ranked servers.

The above parameters must be set for the server to run Ranked.

Note that the following commands are prefixed "sv." when use in the serversettings.con file or server console on both Windows and Linux.

- ServerName – This is the name that the server will display in the server browser.

- Password – This allows you to set a password for the server. Note that Ranked servers cannot be password protected.

- Internet – Check this box to have the server display in the “Multiplay” menu in the 2142 client. Ranked servers must have this option checked.

- 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.

- WelcomeMessage – This allows you to enter text that will be displayed on the server info window while the client is loading the map.

- 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.

- 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.

- 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).

- AllowExternalViews – This allows the players to switch between the normal internal view and the various external views while in vehicles.

- AllowNoseCam – This allows the player to use the nose camera (eliminating the vehicle model) while in aircraft.

- HitIndicator – This setting controls whether the hit indicator will be displayed to the clients when shooting enemy targets.

- 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.

- 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.

- 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.

- 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).

- EndDelay – This sets the time period between the round ending and the server rotating to the next round/map.

- SpawnTime – How long a player must wait before respawning. The default 15 seconds is mandatory on Ranked servers and cannot be changed.

- 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.

- 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.

- RoundsPerMap – How many rounds will be played on each map before loading the next map.

- 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.

- SoldierFriendlyFire – A percentage value of how much damage will be caused by direct infantry weapon fire to players on the same team.

- VehicleFriendlyFire - A percentage value of how much damage will be caused by direct vehicle weapon fire to players on the same team.

- SoldierSplashFriendlyFire - A percentage value of how much damage will be caused by indirect infantry weapon fire to players on the same team.

- VehicleSplashFriendlyFire - A percentage value of how much damage will be caused by indirect infantry weapon fire to players on the same team.

- TkPunishEnabled – Controls whether or not the punish system for team killing is on or off.

- TkNumPunishToKick – The number of times a player may be punished for team kills before being automatically kicked from the server.

- TkPunishByDefault – This setting will automatically punish players for teamkilling if the victim does not choose to punish or forgive.

- VotingEnabled – Controls whether or not players may vote for map changes, commander mutiny and player kicks.

- VoteTime – The time (in seconds) that a vote will last for before the result is applied.

- MinPlayersForVoting – How many players are required to vote for the vote to be successful.

- VoipEnabled – Controls whether or not the Voice Over IP system will be used by the clients.

- VoipServerRemote – Controls whether or not the server will use its own in-built Voip system or the Battlefield Remote VOIP Server.

- VoipServerRemoteIP – The IP address of the remote VOIP server, if one is to be used.

- VoipServerPort – The port used by the server to control VOIP

- VoipBFClientPort – The VOIP port used by the clients to communicate.

- VoipBFServerPort – The VOIP port the server uses to resend messages on to the clients.

Note – all the above ports must be unique if more than one instance is hosted on one PC.

- 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.

- VoipQuality – This sets how much bandwidth will be allocated to ensure good VOIP communication.

- 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.

- 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.

- 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.

- AutoBalanceTeam – Determines whether or not the server will force the teams to be even.

- 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.

- AutoRecord – Enables the BattleRecorder feature.

- 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.

- AutoDemoHook – Leave as default unless you are very familiar with the python scripting language.

- DemoQuality – This sets the quality of the recording.

- AdminScript – Allows the use of custom python scripts for server administration. Leave as default if you are not familiar with the python scripting language.

- SponsorLogoURL – The URL of an image that will be displayed in the server info window in the server browser when the server is highlighted.

- CommunityLogoURL – The URL of an image that will be displayed in the server info window while the client loads the map.

- 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.

- UseGlobalRank – Determines whether or not players ranks will be displayed in-game. This setting is always set to on for Ranked servers.

- 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.

- 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). Note that these slots will be available for use by anyone until a player on the reserved list joins. At that point a player will be kicked from the server to make room for the reserved player.

- BotSkill - Determines how tough the bots are in Cooperative mode.

- MaxRank - Only valid on Ranked servers. This option will only allow players of Rank 11 (Sergeant) and below to join. If players go above this rank while in-game they will be allowed to remain until they choose to disconnect. After this they will not be allowed to rejoin.

- AllowSpectators - Enables spectator mode on your server. This allows people to join the server and watch the action without actually playing. This is only available on Unranked servers and spectators will take up a player slot.

- MinUnlocks - Allows the use of Tier 1 unlocks on Unranked servers for all players whether they have earned them or not.

- MaxUnlocks - Allows the admin to set an upper limit on unlock tiers on Unranked servers.

- AllowTitanMovement - Specifies whether or not the commanders can move the Titan.

- CustomMapURL - This is the URL to be displayed when a player tries to connect to a custom map that they do not have installed. When the player tries to connect, they will be given the option to close the game and visit the URL specified here.

==================
XVI. Version Notes
==================

v1.20

- Added support for Battlefield 2142™: Northern Strike
- Added server side option to disallow Titan movement
- Fixed incorrect message when joining a full server
- Added command to support custom maps
- Friendly Fire with mines is now forced to 'off' for Ranked servers

v1.10

- Illegal Ranked servers are now unable to start. Server IP addresses must be listed in order for the server to start. This is to cut down the number of illegal snapshots sent to GameSpy.
- Improvements to server stability
- Ranked server check to avoid invalid servers showing in the browser
- Corrected error where snapshot would be sent when the round has not started
- Added non ranked server unlock control
- Added spectator mode to unranked server
- Enhanced reserved slot functionality to allow reserved slots to be filled when not required
- Increased number of reserved slots from 25% to 50% of the total number of slots
- Changed default server port to 17567
- Added server filter for Tournament servers

v1.05.21.0

- Improvements to server stability

v1.0.9.1

- Fixed issue causing large scale client disconnects
- Fixed memory leak in Linux server