The bf2_patch_1.4.exe file you have requested: GameFront Clan / Patches / Battlefield Patch Client Files - 530.98MB is not available. Perhaps try browsing all files for the game GameFront Clan and upload any files you want to share or are missing.
We are calling on our community to help submit files that were previously hosted on GameFront / FileFront but are now missing.
If you have this file, please upload it using the form below (please ensure the filename and filesize match) and we shall do the rest.
Here is the full client files! This includes all the games tweaks, and fixes. Do not forget, the new map! Hope you all enjoy. Check the read me for all the changes.
======================================================== Battlefield 2™: V1.4 ReadMe File June 30, 2006 ======================================================== ======================================================== Patch v1.4 ======================================================== GAMEPLAY TWEAKS - The vehicle drop has been modified to help prevent exploits such as blocking enemy vehicles, destroying vehicles and commander assets, or as an alternative to artillery. - C4 tossing distance has been reduced. - A prone->crouch delay has been added. BUG FIXES - Fixed the Linux server hangs when trying to load a Special Forces Co-Op map. - Another attempt at fixing the Red/Blue nametag bug. - Fixed the missing server info on the map briefing screen. - Fixed the server browser issues with updating info. - Fixed the filter by maps size option in the server browser. - Fixed a low reproducibility crash bug related to the vehicle drop. - Fixed a crash in Co-op after a player is revived without a kit. - Fixed a server crash on Linux 32 when trying to rotate maps in Coop Mode. - Fixed the occasionnal red distance marker appearing on the ground. - Fixed the bug that caused the player's arms to become invisible when switching weapons. - Co-Op bot console commands now function on local servers. - Fixed the excessive damage taken by the Muscle Car. - Adjusted the minimum number of players to start the round on ranked servers. The new values for 16, 32 and 64 players are 6, 8 and 8 respectively. - Re-enabled unlocks on unranked servers. - Commander options are no longer available whilst commander is dead. - Fixed bug where a spawn point is shown as selected when it is not if player has spawned in during the preview round. - Co-Op (Local Server) - Fixed the issue where no other players may join the server if the server host is kicked and banned. - Ranked Servers now force unlocks. - Added support for multiple gamemodes in single maplist for mods . ======================================================== Patch v1.3 ======================================================== NEW FEATURES - Air dropped vehicles: Squad members can now send a request up the chain of command for a vehicle to be dropped at their location. - Co-op: 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. Number of Bots: This setting allows you to determine the total number of bots that will spawn in game. 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. Bot Difficulty: This setting determines the skill level of the bots. 10 is easiest, 100 is the most difficult. - Default Kit Selection: The kit that you used last is remembered at the beginning of the round and between maps. BUG FIXES & GAMEPLAY TWEAKS - Fixed issues with remote console and linux server - Prevented ban list from being cleared in the event of a server crash. - Fixed the bug where helicopters abandoned in the air would continue flying. - Fixed issue with player not properly ranking up on servers where they continuously play. - If the player joins a squad while dead, the player will not be able to use the squad leader as a spawn point until they have respawned once. - Flag Capture bar now reacts accurately to players entering the capture radius. - Fixed bug where friendly vehicles showed as valid targets - Friendly Vehicle lock: Lock-on weapons do not lock on to friendly vehicles. The box with an X through it will still appear, but a lock tone will not sound and then if fired, the missile will not track the friendly target. - Fixed bug that altered mini map functionality - Adjusted missile count on BF2SF helicopters. - Fixed bug with Special Forces rank names. - Fixed repairing HUD for the engineer when in a vehicle - Adjusted award criteria - Fixed a client crash after entering 300 characters into the IP address using "connect to IP" - Fixed a tech hang when creating a single player account from an offline account - Fixed crash when switching from BF2 to BF2:SF (or vice versa) - Fixed a crash caused when a player is joining a map and another player logs into the same account - Fixed a Dragon Valley exploit - Fixed a bug on Zatar Wetlands where AA missiles would not lock onto oil towers - Fixed a bug that caused the Eurofighter explosion to appear as a Mig-29 wreckage - Armor Bar removed from occupied machinegun emplacements - Fixed a bug on Kubra Dam and Zatar Wetlands that caused enemy AA sites to not display in bombing HUD - Special Forces - Firing crossbow from open vehicle position causes others to see player weapon firing - Fixed Repair Hud for the engineer when in a vehicle and repairing a team mate vehicles - Fixed a bug on Strike at Karkand where players were able to get inside a building by Train Accident when FF is turned off - Fixed the commander toys on Wake Island 2007 so that the US can no longer disable the Chinese artillery - Fixed a bug in Zatar Wetlands 32 where commander assets were not being properly dropped to the location specified by the User. ======================================================== Patch v1.22 ======================================================== BUG FIXES - Improved Server Stability - Adjusted handling of the Tiger attack chopper - Added delay for aiming reticule when going prone to all support weapons - Adjusted deviation on MG36 and PKM to be in line with other support weapons - Increased rpm from 600 to 900 on the P90 - Fixed Lock on error on certain Oil towers - Fixed a Great Wall Exploit - Fixed exploits on Dragon Valley and Karkand ======================================================== Patch v1.21 ======================================================== BUG FIXES - Fixed the Hmmwv with TOW crash on Battlefield 2: Special Forces maps - Fixed the Battle Recorder crash - Fixed the screen capture - Fixed the issue with Pixel Shader 1.4 video cards - Fixed the issue that caused heat seeking missiles to stick to oil towers - Fixed the issue that caused heat seeking missiles to zigzag - Reduced the maximum number of claymores that can be dropped to 2 - Fixed the Server Browser filter to enable search by map name - Fixed the error in Client - Server communication causing sound, animation and other sync issues. ======================================================== Patch v1.2 ======================================================== Hard Drive Space Windows will require additional free hard drive space for its operating system (virtual memory). If you encounter the following message in an error dialog: "Ran out of virtual memory", free up some more hard drive space. To install Battlefield 2 Version 1.2 you will need approximately 2.0 GB free hard disk space for the full patch or 1.5GB for the incremental patch, plus space for saved games. If you have Battlefield 2 installed to a different hard disk than where you have Windows installed then approximately 375Mb (full patch) or 100Mb (incremental patch) of the required free space must be available on the hard disk where Windows is installed. To install Battlefield 2: Euro Force you will need approximately 800Mb free hard disk space plus space for saved games. BATTLEFIELD 2: SPECIAL FORCES AND THE PATCH - It is very important to remember that the Special Forces executable is an earlier version of the game. If you have purchased Battlefield 2: Special Forces after you have installed the patch, you will need to reinstall patch 1.2 after installing Special Forces. BUG FIXES & GAMEPLAY TWEAKS - Dolphin Diving is no longer possible - Players can no longer jump and shoot at the same time - "Prone Spamming" is now fixed - "Sprint exploit" is now fixed - Helicopters now carry 8 missiles rather than 14 - TV-Guided missile now have a shorter range - Damage decreased from M134 - Hit points on all air vehicles has been reduced - AA missile lock has been improved - All support kit weapons have been adjusted - All Sniper rifles have been adjusted - Sa80 has been adjusted - G3A3 has been adjusted - Reload while sprinting has been enabled - Medic defibrillator paddles have been adjusted. They now reload while not in use. - SCAR-L reload sound has been fixed - Server setting to allow friendly fire to be off on mines without affecting other weapons. - Server search filters now work properly - Mines can no longer be destroyed with other explosives - Bug in MP7 fire rate fixed. Ammo count increased and mag count and damage decreased - Flash bang effect radius decreased - Added unlocks for Sniper and AT kits - Fixed a bug in terrain rendering with night vision, whereby terrain was still dark in dark areas. - Fixed a bug whereby mods that are not bf2 or not xpack permutate shaders every time a level is loaded. - Fixed a bug whereby non-xpack mods cannot use xpack shaders. - Fixed bug in TV guided missiles of Havoc helicopter - The LAV25 no longer shoots through penetrable materials. - Vehicles no longer disappear when viewed from some vehicles with a HUD (e.g. Tanks). - Performance gain found in static mesh rendering. - Detonation radius from grenade launcher explosions has been reduced. - Grenade launcher projectiles now have a minimum distance. - Decreased Flashbang count from 4 to 3 - Replaced the existing Czech Flag with the correct one in the front end EXPANSION OF RANKS - Ranks have now been expanded to allow for players to rank up to General NEW FEATURE VISIBLE UAV - The UAV that is placed by Commanders will now include a visual element. An actual UAV will appear within the UAV detection radius and circle the area. Players will be able to shoot it down, bringing the UAV detection to a premature end. The Commander will be able to continue placing UAVs once the timer resets, as per current design. KNOWN ISSUE ATI CROSSFIRE CARDS - CROSSFIRE cards with 256 Megs of memory, running in CROSSFIRE mode will run out of memory at very high resolution settings. On very high resolutions, such as 1920x1440 with 6x antialiasing. In CROSSFIRE mode the ATI drivers are more restrictive about where resources are allocated, and as a result run out of memory sooner than with a single board. This running out of memory causes the device context creation to fail. The result is that the game just sits in a loop with a black screen. If you experience a context creation failure change your resolution to a lower setting (e.g. 1024x768 or even lower). ======================================================== Patch v1.12 ======================================================== BUG FIXES - Fixed a crash when users switch weapons using the mouse wheel while piloting a bomber (SU-34, F-15 and J10) in core BF2 maps. - Removed the Grappling Hook and the Zip Line from kits from "The Iron Gator" map. - Fixed single player loading screens to match map selection image. - Fixed an issue in the menus so that users can click on BF2:SF ribbons to view the descriptions. - Fixed an issue in the Browser so that BF2:SF servers are now represented with a green "2" icon. - Global improvement of collision detection on the Grappling Hook and the Zip Line. - Fixed damage state artillery icon on the 3d map when an artillery is destroyed. CHANGE of VIDEO SPECS - NVIDIA GeForce FX 5900 family: GeForce FX 5900 Ultra GeForce FX 5900 GeForce FX 5900XT GeForce FX 5950 Ultra GeForce FX 5900ZT GeForce PCX 5900 - For these cards, the default video settings have been changed to LOW. UPDATE TO GRAPPLING HOOK AND ZIP LINE DESCRIPTION GRAPPLING HOOK - The GRAPPLING HOOK is part of the Assault and Anti-tank kits. Throw it using the fire or alternate fire buttons. Press "E" to get on and off of the rope. Use the direction keys to climb the rope. The rope will connect to any static object in the world, which means it will not work on terrain or vehicles. Any Assault or Anti-Tank kit can pick up any grappling hook, even those from other teams, as long as you do not already have one in your kit at the time. ZIP LINE - The ZIP LINE is part of the Special Forces and Sniper kits. Use the fire button to shoot the line and use the alternate fire button to check if the target is a viable connection point or not. Once the line is in place, use "E" to get on. You will slide down the line automatically. Any Spec-Ops or Sniper kit can pick up any zip line, even those from the other team, as long as you do not already have one in your kit at the time. ======================================================== BATTLEFIELD 2™: SPECIAL FORCES SPECIFIC FEATURES ======================================================== IMPORTANT MESSAGE REGARDING EXPANSION PACK AND MULTIPLAYER When Battlefield 2: Special Forces is installed, a new update is applied. However, with this new content it is not possible to play on the Internet or LAN with Battlefield 2 1.03 users. To be able to play together with Battlefield 2 core users, you need to have update 1.1 or later. - In order to play Special Forces in multiplayer on the internet you will need to download the latest patch from EA. NIGHT VISION - The NIGHT VISION is bound to the "7" key by default. When it is enabled, it will allow you to see better in dark areas. There is a battery life on the goggles that will deplete with usage and replenish when not in use. GRAPPLING HOOK - The GRAPPLING HOOK is part of the Assault and Anti-tank kits. Throw it using the fire or alternate fire buttons. Press "E" to get on and off of the rope. Use the direction keys to climb the rope. The rope will connect to any static object in the world, which means it will not work on terrain or vehicles. Any Assault or Anti-Tank kit can pick up any grappling hook, even those from other teams, as long as you do not already have one in your kit at the time. ZIP LINE - The ZIP LINE is part of the Special Forces and Sniper kits. Use the fire button to shoot the line and use the alternate fire button to check if the target is a viable connection point or not. Once the line is in place, use "E" to get on. You will slide down the line automatically. Any Spec-Ops or Sniper kit can pick up any zip line, even those from other teams, as long as you do not already have one in your kit at the time. FLASH BANG - The FLASH BANG is used to stun other players. The FLASH BANG is part of the Assault kit. Use it like a hand grenade. When it detonates, anyone in the effect area will be deafened and those looking at the explosion will be blinded as well. TEAR GAS - The TEAR GAS will linger in an area for a short time. The TEAR GAS is part of the Support kit. While active, anyone in the cloud will become affected. While affected, players will be blind and unable to sprint. Use the GAS MASK (default key "8") to avoid being affected by the gas. Once affected however, the gas mask will not cure you. It will only prevent further affects. UNLOCKS - By playing on a Battlefield 2™: Special Forces map, you will gain the privilege of being able to unlock some of the Battlefield 2™: Special Forces weapons for use in regular BF2 maps. These unlocks are considered to be tier 2 unlocks, where as the original unlocks are considered to be tier 1. You must first have unlocked the tier 1 weapon for a particular kit before you can access and unlock the tier 2 weapon. As an example, if you must unlock the G3A3 for the assault kit before you can unlock the F2000 for the assault kit. GRAPPLING HOOK AND ZIP LINE RELOAD TIME - The grappling hook and zip line take roughly 15 seconds to reload at the resupply crate. ================================================ System Requirements ================================================ - Operating System Windows XP (32 Bit Version) - CPU Battlefield 2 supports the following processors: Intel Pentium 4 Intel Xeon Intel Pentium Extreme Edition Intel Celeron D AMD Athlon XP AMD Athlon 64 AMD Athlon 64-FX AMD Sempron processor - Minimum Specification: CPU: 1.7 Ghz RAM: 512 Mb Video Card: NVidia GeForce FX 5700, ATI Radeon 8500 or ATI Radeon 9500 with 128 Mb of RAM - Recommended Specification: CPU: 2.4 Ghz RAM: 1 Gb Video Card with at least 256 Mb of RAM - Video Cards Battlefield 2 only supports the following video cards: Radeon X700 (PCIe) Radeon X600 (PCIe) GeForce 6600 (PCIe) GeForce PCX 5900 (PCIe) GeForce 5800 Series (AGP) ATI Radeon X800 XT Platinum Edition ATI Radeon X800 PRO ATI Radeon 9800 Series ATI Radeon 9600 Series ATI Radeon 9550 (RV350LX) ATI Radeon 9500 / 9700 Series ATI Radeon 8500 Series ATI Radeon X300 Series NVIDIA GeForce 6800 Ultra NVIDIA GeForce 6800 GT NVIDIA GeForce 6800 NVIDIA GeForce FX 5950 Series NVIDIA GeForce FX 5900 Series NVIDIA GeForce FX 5700 Series ======================================================== Hard Drive Space ======================================================== To install Battlefield 2: Special Forces you will need approximately 3.0 GB free hard disk space, plus space for saved games. In addition to the installed game, Windows will require additional free hard drive space for its operating system (virtual memory). If you encounter the following message in an error dialog: "Ran out of virtual memory" Free up some more hard drive space. ======================================================== Patch v1.03 ======================================================== NEW FEATURES - Wake Island Map Included a remade version of this popular BF1942 map. Battlefield 2 version includes a 64 player layout and is configured for multiplayer only. - Server Favorites / History There is a new tab in the MULTIPLAYER menu that holds a list of the last 20 internet servers you have connected to, plus a list of servers you have selected as favorites. * Added a button to the other multiplayer tabs that adds the currently highlighted server to your favorites list. * Added buttons in the in-game server info menu (press TAB to access) that will add or remove the server you are currently playing on to / from your favorites list. - Account Login Welcome Screen After you login to an online account, a message appears that contains BF2 news and information which updates periodically. - Stat Compare By clicking the COMPARE button in BFHQ, you can search for another players name and load their current stats into BFHQ. Using the arrow buttons next to the name in the top-left corner of the menu, you can toggle between your stats and their stats. You can also load a player's stats by double-clicking on their name in any leaderboard. - Nickname Prefix You can add a 6-character prefix (such as a clan tag) to your account nickname which will be displayed in-game next to your nametag in the score menu, in game messages, and above your player in the game world. * This prefix does not change your account name or statistic information (e.g. the prefix does not appear next to your name on the leaderboards). * You can change this prefix at any time at the account login menu. - Server Reserved Slots You can define a list of player nicknames that will act as a "reservation list" for your server. * The list is located in modsf2settingsReservedSlots.con * You can add player names to the list by editing the file and adding the following text for each player : reservedSlots.addNick where is the player's registered account name, not including a nickname prefix (see above). * You can define the number of slots to set aside for reserved players in the dedicated server launcher, or with the setting sv.numReservedSlots in your serverSettings.con file. * The number of players on the list and the number of reserved slots does not necessarily have to be the same. - Mod Support There are several new changes that improve support for mods. * When connecting to a server that is running a mod that you have installed but not activated, it will be automatically activated and you will load into the server. * Added a filter on the server browser for servers running the currently activated mod. * Fixed dedicated server launcher to properly handle launching mods. * Improved support for mods sharing archives with bf2 - Improvements to in-game HUD / Map * The viewable area of the spawn menu / commander map is now scaled based on the out-of-bounds area so that only the playable area takes up the majority of viewable map space. * The names of CPs are now displayed on the spawn menu / commander map and minimap * The minimap zoom level now changes dynamically depending on the type of vehicle you are in. If you zoom in or out manually, that zoom level is remembered for that vehicle type next time you use it. * The names of players in your vehicle are displayed in the HUD when someone enters the vehicle or switches positions. * There is a new element in vehicle HUDs that displays the reload time for countermeasures (smoke and flares). * Flags for each team are now displayed below their ticket count on the minimap to make it easier to tell what team you are assigned to. GAMEPLAY CHANGES - Many criteria for ranks and awards have changed. If you are immediately eligible for a new promotion, unlock, badge, award, or ribbon, it will be awarded the next time you receive points on a ranked server. - Only 1 player in a vehicle will get credit for or speed up capturing a flag at a CP. The other passengers must exit the vehicle to increase the speed of capture or receive capture score. - Commanders no longer accrue a TK when artillery hits teammates. - The commander's supply drop now has an icon on the minimap and a 3D- map icon in the world. - Auto team balance no longer moves players to the other team if they are a team commander or a squad leader. - The wrench repair rate on helicopters has been decreased. - You now receive 1 support point for destroying an enemy commander's artillery, UAV or Radar station. - If you have received a point for healing, repairing, or resupplying a teammate, you will not receive another point from them for the same action for a set period of time. - Singleplayer enemies use the knife more effectively. - New engine sounds for the T98 tank. - New engine sounds for the China/MEC light jeep. - New cannon sounds on APCs. BUG FIXES - Fixed physics of vehicles against soldiers so that soldiers are not killed so easily by moving vehicles. - Fixed a physics issue that can cause you to be stuck when falling into shallow water - Fixed an issue with soldier armor when spawning on a squad leader in a vehicle - Fixed some objects that caused vehicles to take massive collision damage - Fixed erroneous message stating that you punished a TK when auto- punish is OFF on the server. - When a vehicle explodes due to external forces, the driver is no longer mis-credited for the kills. - Added turret movement sounds to several vehicles. - Fixed an issue that caused crosshairs to stay on the screen when switching camera views. - Fixed an issue that caused the time limit status of the server not to be sent to clients when it is changed by the server. - Fixed server setting sv.allowExternalViews. Setting this to 0 will disallow external views. - Added setting for interfaceIP to the server launcher - Changed automatic TK banning to ban by cd-key instead of IP address - Improved the stability of secondary position turrets to reduce jerkiness during movement. - Fixed spawning on squad leaders to prevent players from spawning where they should not. - Fixed issue with auto team balance not sending new players to the team with less players. - Set T90 top hatch armor to "Front Armor". - Set some wheels on jets and helicopters to stronger armor to prevent them from being destroyed instantly by AT missiles. - Adjusted wheeled vehicle engines on hills to improve climbing. - Changed the Commo-rose behavior so that player does not leave crouch when using it. - Passwords entered to join password protected servers are now cleared after use. - Improved PLAY NOW functionality. - Fixed some memory usage issues in the front end. - Fixed an issue allowing color changes in player name text. - When you click on a server in the server browser, the information from that server is updated to be more accurate. - Fixed a crash in the Ranked Linux server when communication with stats back-end ceased. - Improved the behavior of AA missiles when locked on an enemy. - Fixed an issue where parachuting soldiers could not be healed. - Added the server port to the SERVER INFO tab. - Removed the SERVER INFO tab when playing singleplayer - Fixed an issue causing some soldier & vehicle control keys to be used for in-game menus. - Added new soldier artwork in BFHQ - Added name of video director to credits ================================================ Patch v1.02 ================================================ Fixed a server memory leak ================================================ Patch v1.01 ================================================ Fixed an issue that caused the Multiplayer Browser to become unresponsive. Fixed an issue where some game controls were not available to be rebound within the Options menu. Fixed an issue with increasing performance degradation on servers. Fixed a problem with shader caching on client/host : after the first map in a rotation, shaders would be loaded on the fly during gameplay. Fixed a crash with rebinding LMB Fixed a problem that caused environment mapping to not appear on reflective surfaces. Fixed a crash that happened when a client picks up a kit that doesn't exist anymore. Fixed a problem with AI when the game was paused for a long time: bots would become unresponsive and also shoot more accurately. LOD distances tweaked on certain objects. ================================================ Improving Gameplay Performance ================================================ Some machines will benefit from experimenting with your Network / Video / Sound options: INTERNET / NETWORK PERFORMANCE This section is very important to experiencing good internet play! - JOINING MULTIPLAYER GAMES: To get the best performance on your computer we recommend you follow these guidelines: HARDWARE Minimum systems - Join servers that have up to 16 players Recommended systems - Join servers that have up to 32 players High end systems - Join servers that have up to 64 players BANDWIDTH ISDN users - Join games with a maximum of 16 players. ADSL/Cable users - Join games with a maximum of 32 players. T1/LAN users - Join games with a maximum of 64 players. ================================================ 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: 2 Gb - Optimal Specification (as of Patch 1.3), based on playing a 64 player game: Only run one instance of BF2 per physical CPU with Hyperthreading disabled CPU: AMD Athlon 64 4800+ or 3.66GHz 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 - Optimal Specification (as of Patch 1.3), based on playing a 64 player game: Only run one instance of BF2 per physical CPU with Hyperthreading disabled CPU: AMD Athlon 64 4800+ or 3.66GHz Xeon. RAM: 2Gb per physical CPU 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. ================================================ CLIENT AND SERVER PORTS ================================================ Battlefield 2 Account Creation NOTE: In order to create a Battlefield 2 multiplayer account, you must have the following ports open in your firewall. Client Ports: UDP 27900 UDP/TCP 29900 TCP 80 TCP 4711 TCP 29901 UDP 1500-4999 UDP/TCP 1024-1124 UDP 28910 UDP 16567 UDP 55123-55125 Hosting a Battlefield 2 Server In order to host a Battlefield 2 server, you must have the following ports open in your firewall. Server Ports: UDP 27900 UDP/TCP 29900 TCP 80 TCP 4711 UDP 27901 UDP 1500-4999 UDP/TCP 1024-1124 UDP 29900 UDP/TCP 27900 UDP 16567 UDP 55123-55125 ================================================ 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 Used to specify the location of the _mapList.con The default is My DocumentsBattlefield 2ServerConfigs - 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 Removes the map you specify from the map list - mapList.append [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 [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 [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 [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 [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 [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 Enter the IP address you would like to remove from the ban list. - admin.removeKeyFromBanList 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 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 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 Replace 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 ================================================ BATTLE RECORDER ================================================ USAGE The BattleRecorder allows a round to be recorded and distributed. The system is very flexible, and the current implementation can be easily changed. We recommend you have a good knowledge of Python before you edit the scripts used here. There are two components to BattleRecorder. First is the Dedicated Server Launcher. The Dedicated Server Launcher requires the following information: - AutoRecord Set AutoRecord to on to enable the BattleRecorder. Every round played on the server will now be recorded to a file. - DemoDownloadURL 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. - AutoDemoHook The server runs this script at the end of every round where AutoRecord is enabled. - DemoQuality 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 2 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 adminutilsdemo otate_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 2 installation root directory. In this file you can configure: - file_limit = 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 = If you intend to transfer to a local directory, enter the path here. - use_ftp = Set this to 1 if you wish to FTP the DemoRecorder file to a new location. - ftp_target_dir = Enter the path on the FTP site where you want the DemoRecording transferred to. - ftp_server =
There are no comments yet. Be the first!