Title: UPDATED! (1.42)
Size: Date:
Download location:
Note:

*** IMPORTANT - OPERATION FLASHPOINT STANDALONE DEDICATED SERVER README ***
21st September 2001

UPDATED! What's new in version 1.42:
=====================================

1.42 - Added: parameter "voiceOverNet" added to dedicated server config (default = true)
1.42 - Fixed: Debugging message shown when AI preparing to release LG bomb.
1.42 - Fixed: AI used binocular too often.
1.42 - Fixed: Repeated ".. is down" message when player was killed.
1.42 - Fixed: AI units cannot get in ships since 1.40
1.42 - Fixed: KickOff for Game In Progress screen
1.42 - Added: browsing in chat history using Page Up and Page Down in chat line
1.42 - Fixed: Cessna AI pilot swinging up and down when flying slow.
1.42 - Fixed: Helicopter took off after landing even when no waypoint was active
(bug since 1.40).
1.41 - Fixed: Support for Windows Me ICS, Windows XP ICS, and UPnP-compliant NATs
1.41 - Fixed: Buffer overflow in XML parsing
1.41 - Fixed: limit for size of GameSpy Q&R SDK answer is respected now
1.41 - Improved: Expression evaluation optimized (faster script execution).


--------------------


Required: v1.42.
The OFP_Server.exe file will enable you to set up dedicated Operation Flashpoint
servers without requiring the original CD or CD Key.


INSTALLATION INSTRUCTIONS
Firstly, ensure the entire contents of an Operation Flashpoint game directory are present on the target server machine. The original directory structure must be maintained, but the files can either be copied from an existing installation, or freshly installed.

*NOTE* The game must have been started at least once, in order to create a Flashpoint.cfg file which will instruct the application to skip the Preferences-setting dialog box. A sample of this file is included in the download package.

The new OFP_Sever exe file should then be copied into the root Flashpoint directory. Run this file to create a dedicated server.


DEDICATED SERVER INSTRUCTIONS

You can set up a config file for your server, to assign passwords and mission cycles. Call it with an additional command line parameter: for example, OFP_Server.exe -config=sample.cfg.

There's a sample config file included in this download package, along with a batch file to launch it into the game. Install both files in the same directory as the new exe, then launch the configured server by double-clicking on OFP_Server.bat.

You can edit a config file in any text editing application. In the server config file, text after "//" marks is comment only.

In the first line, you can assign a session password, which will be required of all players who wish to connect to this game. In the sample config file, no session password is assigned.

In the second line, an Admin password is set. This is the password that will be used to remotely log on to the server, and to control it once it is running.

The main section of the config file details the map cycle. The easiest way to add new missions or change the current mission cycle is to copy a section and then just change the mission name.

Here's the basic structure for each mission in the cycle:

class Mission02 ***Add a number for each new mission; the next would be 03***

{

template = 2-8_t_capturetheflag1.eden;

***the name of the mission - make sure you type it accurately***

cadetMode = 0;

***0 = difficulty veteran, 1 difficulty cadet***

param1 = 600;

***a parameter specific to the mission; param1 is usually time***

param2 = 50;

***sets another mission-specific paramter, usually score***

};


NOTE: you can specify a port number for the game to use by adding a further parameter to the exe's command line: -port=xxxx.


REMOTE ACCESS TO THE SERVER
Once you have joined the server, open the chat box ("/" key) and type:
#login [Admin Password]. By default, this password is "pwdgamemaster". If you
use the sample config file, it is "login".

This will log you in as the server admin and allow you to change settings remotely.

Remote commands are all entered in the chat box and are preceeded by a # Useful commands include:

#logout
#kick "playername" ***kick named player***
#restart ***restart the current mission***
#mission ***switch to the next mission in the config file***
#missions ***select a new mission from the list of available missions***