More 4.2.20 changes.

This commit is contained in:
Markus Armbruster 2005-03-22 21:10:44 +00:00
parent 2cf7bacf03
commit 2af6fcd78e
2 changed files with 26 additions and 2 deletions

View file

@ -1,4 +1,16 @@
Changes to Empire 4.2.20 - Thu Mar 17 21:34:13 UTC 2005 Changes to Empire 4.2.20 - Tue Mar 22 21:07:18 UTC 2005
* When units in different sectors marched, only units in the sector
with the highest-numbered unit were interdicted. A marching
non-spy made all marching spies visible to interdiction regardless
of location.
* Fix crash when interdiction sinks second ship in a sector. Broken
in 4.0.10.
* Fix an ancient bug in simulation of level production that clobbered
stack and could lead to low predictions, typically zero, which
screwed up budget. The bug had no effect until 4.2.19.
* When a sector revolts, and there wasn't enough space to liberate
all uw, the number of remaining uw got the wrong sign. Broken in
4.2.14.
* Log and abort when LWP stack check detects stack smash. Server * Log and abort when LWP stack check detects stack smash. Server
option -s no longer implies -p. option -s no longer implies -p.
* The native Windows build now supports -p and -s. * The native Windows build now supports -p and -s.

View file

@ -7,7 +7,19 @@ new Empire4 Server. This outlines the various changes and how they
will affect you, the player. These were coded as the Wolfpack project, will affect you, the player. These were coded as the Wolfpack project,
and bug-reports should be sent to <wolfpack@wolfpackempire.com>. and bug-reports should be sent to <wolfpack@wolfpackempire.com>.
.NF .NF
Changes to Empire 4.2.20 - Thu Mar 17 21:34:13 UTC 2005 Changes to Empire 4.2.20 - Tue Mar 22 21:07:18 UTC 2005
* When units in different sectors marched, only units in the sector
with the highest-numbered unit were interdicted. A marching
non-spy made all marching spies visible to interdiction regardless
of location.
* Fix crash when interdiction sinks second ship in a sector. Broken
in 4.0.10.
* Fix an ancient bug in simulation of level production that clobbered
stack and could lead to low predictions, typically zero, which
screwed up budget. The bug had no effect until 4.2.19.
* When a sector revolts, and there wasn't enough space to liberate
all uw, the number of remaining uw got the wrong sign. Broken in
4.2.14.
* Log and abort when LWP stack check detects stack smash. Server * Log and abort when LWP stack check detects stack smash. Server
option -s no longer implies -p. option -s no longer implies -p.
* The native Windows build now supports -p and -s. * The native Windows build now supports -p and -s.