Obtain the latest FORMULAS.HTM file -- see changes below.
Instructions for Hosts
Replace the PHOST program
Bug Fixes
Segmentation violation while reading TRN files on Linux systems
has been fixed. (v3.2c)
The TONS.HST file was not being written out. (v3.2a)
An assertion failure could result when an add-on program removed
a base from the game (e.g., after TKF combat) but did not remove a
pending build order for that base from the build queue. (v3.2d)
Cloak missions raised yellow alerts when the controller of a
remotely-controlled ship was not allowed to cloak the ship via the
HULLFUNC.TXT interface, even though
the true ship owner did have this ability. (v3.2e)
Cheat checking did not trap cargo dumps to non-existent planets,
possibly leading to assertion failures during host processing.
(v3.2c)
Comments following an assignment for array-type config options in
the PCONFIG.SRC file led to either strange error messages or
segmentation violations. Now, they are ignored as they should be.
(v3.2b)
The PCONFIG.SRC file was being opened in binary mode
instead of text mode on PC-based systems, meaning that a trailing
end-of-file character (^Z) would cause PHOST to reject the file.
(v3.2b)
New Features
None
Miscellaneous Changes
The formula describing the number of base torps used to aid in
planetary combat was slightly incorrect.
The formula describing ship fuel
consumption now describes the
meaning of the FuellessShipMass quantity.
Obtain the new MISSION.INI file from your host and place
it in your game subdirectory.
Instructions for Hosts
Replace the PHOST program and the PLANG*.HST files
Distribute the new MISSION.INI file to your players.
Add the new
AntiCloakImmunity
config option to your PCONFIG.SRC file. For backwards compatibility,
set:
AntiCloakImmunity = Yes, Yes, No, No, No, No, No, No, No, No, No
Bug Fixes
A bug prevented players from changing build orders after the
500-ship limit had been reached. The new
build order would not be recorded and the old build order would
persist but without ever gaining priority. (v3.1b)
Player-initiated config modifications (e.g.,
AllowMoreThan50Targets) were not correctly reflected in the
PCONFIG.SRC file when AUXHOST programs were used during hosting.
(v3.1c)
Some of the example PCONFIG*.SRC files had an incorrect
default value of the FighterFiringRange
config option. The files listed a value of 100000 while the suggested default
value (and the one implied in PHOST v2.x) is 3000.
PHOST would fail with an assertion error when a wormhole's mass
became exactly 0, either due to a manual setting or by programmed changes.
Now, a wormhole mass of 0 on an active wormhole generates an appropriate
error mesage. (v3.1c)
Ships travelling too fast for their damage level had their warp
speeds reset to 0 instead of to the maximum allowed speed. (v3.1c)
Host data consistency checks falsely flagged problems due to
ownership issues caused by remote control. Specifically, a Lizard ship
under remote control had its damage-limited speed calculated without the
Lizard bonus. (v3.1c)
Host data consistency check diagnostics no longer appeared in the
HOST.LOG file (although they were displayed on-screen during the host
run). (v3.1c)
The -f flag of PVCR was broken so that PVCR could not be
used to view HOST-generated battles (as interpreted by PVCR). (v3.1c)
The build queue ordering reported in the player messages (and
UTIL.DAT files) was incorrect since the build queue
was not sorted after TAL/PAL adjustments were incorporated. The build queue
is always sorted prior to each ship building stage so this bug did not
affect the order in which ships were built; only the view that players had
of the build queue was slightly distorted. (v3.1c)
Fixed "Wraparound Maps" page to
consistently indicate that planets outside the wraparound region are
ignored. In one place, the documentation indicated that the planets are
remapped into the wraparound region.
New Features
Two new extended missions, Lay
Mines In and Lay Web Mines In were
added. These missions allow control over which existing minefield is to be
augmented with new mines. These missions are only available to registered
players. (v3.1c)
The Scoop Torpedoes From
Minefield extended mission now takes a second parameter indicating a
specific minefield to scoop from. (v3.1c)
New
AntiCloakImmunity config
option changes anti-cloak immunity from a racial option to a
per-player-configurable option (added for HOST 3.22.022 compatibility).
(v3.1c)
PHOST now writes a CLOAKC.HST file to the game directory
prior to running an AUXBC.INI file (if one exists), and also reads
it back to update cloaking information after the AUXBC.INI program
returns. This interface works identically to the one introduced in HOST
3.22.017. (v3.1c)
The remote control forbid
and allow commands can now be
used to set the default forbid/allow state for all newly-built ships.
Previously, all newly-built ships were allowed to be remotely controlled.
(v3.1c)
The SBQPointsForAging
config option has had its allowable range increased to 0-10000, up from the
previous range of 0-500. (v3.1c)
Added an entry in the
Planetary Combat section of the
"Detailed Operation"
page for the number of natives remaining after a planet is conquered in battle.
Added an entry in the
Wormhole Formulas section of the
"Detailed Operation"
page for the possible exit points of a ship travelling through a wormhole.