Version of OpenTTD

Tested on f9d24ff

Expected result

When the server crashes right after loading a savegame and the client (that is reconnecting at the time) gets disconnected, autosave/netsave.sav contains a copy of the old network game before the server restarted.

Actual result

When the server crashes right after loading a savegame and the client (that is reconnecting at the time) gets disconnected, autosave/netsave.sav contains a copy of the title screen game.

By contrast, when the server crashes while loading a savegame, the client is disconnected and autosave/netsave.sav contains a copy of the old network game before the server restarted.

Steps to reproduce

1. Start a server (openttd -D ::1).
2. Start the client (openttd).
3. Client: Connect to the server (connect ::1).
4. Server: Load a savegame that causes the server to crash while the client is reconnecting. For example, the crash.sav from Crash during vehicle unload #5995.
5. The server restarts as it prepares to load the save, causing the client to save the current game state to autosave/netsave.sav and exit to the title screen (which replaces the game state with that of the title game).
6. When the error window pops up, click the "OK" button as fast as you can.
7. The server will close while the client is downloading the map, causing the client to save the current game state again (title game this time) to autosave/netsave.sav.

Alternative steps to reproduce

1. Set map_x and map_y in openttd.cfg to at least 11.
2. Start the server.
3. Start the client.
4. Client: Connect to the server.
5. Server: Generate a new map using restart or newmap.
6. The server restarts as it prepares to generate a new map, causing the client to save the current game state to autosave/netsave.sav and exit to the title screen (which replaces the game state with that of the title game).
7. While the client is downloading the map, close the server.
8. The client is disconnected while download the map, causing the client to save the title game to autosave/netsave.sav.