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
|
@ -308,16 +308,9 @@ produce_sect(int natnum, int etu, struct bp *bp, long p_sect[][2])
|
|||
sp->sct_updated = 1;
|
||||
work = 0;
|
||||
|
||||
/* do_feed trys to supply. So, we need to enable cacheing
|
||||
here */
|
||||
bp_enable_cachepath();
|
||||
|
||||
sctwork = do_feed(sp, np, vec, &work, etu);
|
||||
bp_put_items(bp, sp, vec);
|
||||
|
||||
bp_disable_cachepath();
|
||||
bp_clear_cachepath();
|
||||
|
||||
if (sp->sct_off || np->nat_money < 0)
|
||||
continue;
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue