Hold the lay ship through a construction delay instead of restarting the lay (#322)
A delay that hit your own subsea cable while it was being laid moved the whole laying stretch later: the ship vanished, the laid km went back to zero and the survey and factory could be hurried and paid for again. The delay now holds the ship where it is (l.lay: start, share laid, resume day), so laying picks up after the delay. Old saves without the field lay as before; sanitize() repairs or drops it.
This commit is contained in:
parent
4292cd4c74
commit
d971ded259
6 changed files with 88 additions and 5 deletions
|
|
@ -6,6 +6,7 @@ All notable changes to this project are documented here. The project follows
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
- A delay while your own subsea cable is being laid now holds the lay ship where it is, instead of sending it back to port and starting the laying over. The cable already on the seabed stays there, the build simply finishes later, and there is nothing to pay twice (#322).
|
||||
- While nothing moves on the map but its animations (packets, waves, clouds), it is drawn 30 times a second instead of at the screen's full rate, half the work on most screens and a quarter on 120 Hz phones. Moving the map, pointing at something or anything changing on the network still gets every frame, and the animations keep their speed.
|
||||
- A paused game no longer rewrites its save every 5 seconds when nothing has changed. On a big network each of those writes held the page for 20 to 30 milliseconds.
|
||||
- At ×8 a big network's autosave no longer holds the page: the game is packed, turned into text and compressed in the background, and less of each day's routing has to travel back to the page. The game plays exactly as before.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue