Don't use automatic supply to avoid starvation at the update
Food supply during update adds complexity to the update. How much good it does to players is highly doubtful; certainly nobody can rely on it. It isn't covered by the starvation command. Starving ships or land units can steal enough food from their sector to make it starve, too. Finally, the supply code is notoriously hard to use correctly. We don't know of issues with the update's use, but we haven't convinced ourselves that there aren't any either.
This commit is contained in:
parent
c0b300d875
commit
7da69c92e0
9 changed files with 9 additions and 85 deletions
|
@ -27,14 +27,10 @@ This document gives a rough order of events during the update.
|
|||
a) if the sector is a cap, it costs $1 per etu since
|
||||
the last update
|
||||
b) people in non-sanctuary sectors eat
|
||||
1) If not enough is available, the sector
|
||||
uses the supply routines to draw more.
|
||||
2) If still not enough is available,
|
||||
the excess people will starve off.
|
||||
a) No more than 50% of the people
|
||||
in a sect can die;
|
||||
the uw's die first, then
|
||||
the civs, then the mil.
|
||||
If not enough is available, the excess people will
|
||||
starve off. No more than 50% of the people
|
||||
in a sector can die; the uw's die first, then
|
||||
the civs, then the mil.
|
||||
c) if there was starvation, the work percentage is set
|
||||
to 0, otherwise the work rate rises by
|
||||
8+(1-15), max of 100
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue