Changed server options: * lockOtherTeam, pausedFPS and waitingFPS The meanings of allowViewing and lockOtherTeam options were confused in earlier versions, with both having some effect on whether you could watch the opposing team after you were out of the game yourself. Now allowViewing is removed. Options pausedFPS and waitingFPS can be used to specify a maximum FPS for pausing and waiting (dead) players. Option lockOtherTeam tells whether you can watch an opposing team if you're out of the game but your whole team isn't (so you could spy for them). New server options: * gameSpeed (real, default 0) The gameSpeed determines how fast the game proceeds. A gameSpeed of x means that the game proceeds at the same rate as on a standard XPilot server running at x FPS. A gameSpeed of 0 means that the game speed equals the FPS value. The value of gameSpeed cannot exceed that of FPS. * baselessPausing (boolean, default off) This option can be used to turn team number 0 into a pause only team. Pausing players automatically get swapped to team 0. * recordMode (integer, default 0) * recordFileName (string, no default) recordMode 0: The server will run normally. recordMode 1: The server saves the game in the file specified by the recordFileName option. recordMode 2: The server replays the game saved as described above. Clients can connect to the server and change the player they are watching with the lock next/previous keys. The recordMode option should be set when starting the server. Recording (mode 1) can be finished either by setting recordMode to 0 or by shutting down the server. * constantScoring (boolean, default off) If this option is set on, the scores awarded from various things are constant instead of changing depending on current points. This option can be changed at any time. * elimination (boolean, default off) Setting this on enables a new race mode (normal race mode must still be on). For each lap, the last player to finish it drops out of the race. NOTE: This is currently broken. * dataURL (string, default "") The purpose of the option is to tell the client where to find additional data about the map that is not transmitted inside the normal xpilot messaging. The option should be a URL that points to a file on an HTTP server containing the data. The client issues an HTTP GET request to fetch the file and extracts it into the local texture directory. Currently the additional data contains only the textures used by the map but it could well be used for other things like map specific sounds. The data file is basically just a concatenation of all the files separated by file length header and compressed with zlib. The format is "documented" in the xpilot/contrib/mapzip/mapzip.c utility http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/xpilot/xpilot/contrib/mapzip/mapzip.c?rev=1.1&content-type=text/vnd.viewcvs-markup that can be used to create and extract data archives. * clientPortStart & clientPortEnd (integer, default 0) These options are meant to be used when running a server inside a firewall that allows a limited range of UDH ports. If clients can connect without using these options, they should be left to 0. When these are set, the server chooses the client-specific UDH socket between clientPortStart and clientPortEnd (inclusive). At least one port is required for each client; if a free port cannot be found in this range, new clients cannot connect. When these options are set, clients will only send packets to contactPort and ports in this range. (These options are in old-style XPilot too now, they were ported from this version to the official one after this page was initially written).