empserver/src/lib
Markus Armbruster 8ccad0d779 Units no longer die from lack of maintenance
Damage due to lack of maintenance is now limited by the unit's minimum
efficiency.

Before, units could die.  Unfortunately, the update left any embarked
units on their dead carrier.  Should have seen this when I fixed a
related bug in commit c2c0d1ff, v4.3.22.  Broken for ships and land
units when Empire 2 added their maintenance cost, and for planes when
commit 2e40a4bb (v4.3.4) replaced nuclear stockpiles by nuke units.
The common root cause of these bugs is the update bypassing pre-write
functions (bug#1010856).

If another unit with the same number got built, it picked up the stuck
cargo, triggering the oops from commit 6fb5caf6, which see.

In "stuck on dead carrier" state, units pretty much behave as if their
carrier was still alive, with additional protection from the fact that
a dead carrier can't be damaged or boarded.

The server detects this state on startup since commit 7da9aab5, and
refuses to start.

Only a deity can take units off a dead carrier.
2011-07-10 21:08:50 +02:00
..
commands Avoid false positive generation oops in navigate and march 2011-07-09 15:16:21 +02:00
common Fix xundump's "value must match" check for split tables 2011-06-25 17:12:40 +02:00
empthread Update known contributors comments 2011-04-14 20:21:23 +02:00
gen Update known contributors comments 2011-04-14 20:21:23 +02:00
global Remove option LANDSPIES, customize table land-chr instead 2011-06-25 16:53:02 +02:00
lwp Update known contributors comments 2011-04-14 20:21:23 +02:00
player Avoid false positive generation oops in navigate and march 2011-07-09 15:16:21 +02:00
subs Oops when stuck cargo snaps to new ship, plane or land unit 2011-07-10 11:43:44 +02:00
update Units no longer die from lack of maintenance 2011-07-10 21:08:50 +02:00
w32 Fix compile under Window MinGW environment 2011-04-18 19:17:12 +02:00