Build 31 is live on Steam, and the server changed with it — so this one is not optional. Let Steam update, and if it does not show up, exit Steam completely and start it again.
You now get a warning before the server restarts
A banner appears at the top of the screen with a live countdown, so an update no longer lands on you without notice. It shows even if you log in partway through a countdown, and it counts against the server's clock rather than your PC's, so the number is right whatever your machine thinks the time is.
It deliberately does not live in chat. Chat was the obvious place to put it and the wrong one — the chat dock slides away, and the people most likely to lose progress to a restart are exactly the ones buried in a build screen with it closed.
One honest caveat: this can only warn players who already have build 31. The next restart after this one is still worth watching Discord for.
Fleets deploy beside your base again
Deploying used to drop a fleet at a random point in a wide ring around your outpost. On a busy planet that could put it closer to somebody else's base than your own, which is exactly how it was reported. Fleets now take a berth just off your outpost, on the open side facing away from the planet, and several fleets line up beside each other instead of stacking.
Thanks to the tester who reported this twice — the first attempt put every fleet in the same sensible spot but still too far out, and the second report is what got the distance right.
The shipyard explains itself
Trying to build a second ship with no Shipyard, or with a full ship bay, used to do nothing at all. No message, no reason. It now tells you what is stopping you and what to do about it.
While fixing that we found some accounts carrying a stale value from an earlier update: a few had a build slot they had not earned, a couple had fewer than they had. That corrects itself the next time you open your base.
For reference, simultaneous ship builds come from your Shipyard: none gives you 1, a Shipyard gives you 2, Mk3 gives 3, Mk5 gives 4.
Keep it coming
Every change in this build started as a tester message. Whatever you are running into, the bug reports channel is the fastest way to get it looked at, and a screenshot is usually all it takes.