Navigation
  Battlefield 2
  Special Forces
 
 Battlefield 2 Server Setup
Battlefield 2 server setup instructions
DEDICATED SERVER

We highly recommend Battlefield 2 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: 1 Gb

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: 1 Gb

BANDWIDTH

- Minimum 2.5 Mbit

- Recommended 5Mbit

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.


SERVER ADMIN COMMANDS


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 2 Demo\ServerConfigs\

- mapList.load
Makes the server reload the _mapList.con

- mapList.save
Saves the current map list on the server to the file _mapList.con

- 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. The players ID number is also available on the Scoreboard / Manage Tab

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

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

- admin.nextLevel
Shows the map list ID number for the next map to be played.

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


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

Now you can access the server remotely by using the following commands
from a client:

- 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

For more advanced server management features we recommend you download one of the many tools available for Battlefield 2.


VoIP


STANDALONE VoIP SERVER

Battlefield 2 supports running a remote VoIP server. Running the VoIP server remotely takes load off the main game server, and so increases performance.

SETUP

In the Battlefield 2 Server Launcher:

- VoIPEnabled
Enables VoIP in Battlefield 2.

- VoIPServerRemote
Enable this if you would like to run VoIP via a remote server.

- VoIPServerRemoteIP
Enter the IP address of the remote VoIP server.

- VoIPServerPort
Specifies the Battlefield 2 server socket used to communicate with the Remote VoIP Server.

- VoIPBFClientPort
Specifies the Battlefield 2 client socket used to communicate with the Remote VoIP Server.

- VoIPBFServerPort
Specifies the socket on the Remote VoIP Server used to communicate with the Battlefield 2 client and the Battlefield 2 server.

- VoIPSharedPassword
Here you can specify a password to be used to access the VoIP server.

- VoIPQuality
Here you can specify the VoIP quality. Higher values will increase the quality of the transmitted sound, and will also require more bandwidth.
- LAN servers started via the front end have a default quality setting of 5, the highest.
- The Battlefield 2 Server Launcher defaults to a quality setting of 3. This is best for internet games. For LAN games you can increase this to improve the transmission quality.

The Battlefield 2 Standalone VOIP Server can be installed on a separate machine by following the install procedure; select custom install and select BF2 VOIP server.

You may need to edit the 'voip.con' file on the standalone VoIP server. By default this file contains:

55125 no_password

- '55125'
This is the default port assignment the Battlefield 2 Server will use to communicate with the Standalone VoIP Server. This number must match the one in VoIPServerPort, set in the Battlefield 2 Server Launcher.

- 'no_password'
This password must match the one set in VoIPSharedPassword in the Server Launcher.


MULTIPLE INSTANCES

You can have multiple instances of the Battlefield 2 Server connected to the Battlefield 2 Standalone VoIP Server. To do this you must ensure that each instance connects via an unique port. For example:

- Instance 1
VoipServerPort 55127
VoipBFClientPort 55128
VoipBFServerPort 55129

- Instance 2
VoipServerPort 55130
VoipBFClientPort 55131
VoipBFServerPort 55132
bf2awards.com 2005 - 2017
 
 Miscellaneous
 
 File Downloads
 
 Maps
 
 Army and Kits