When running a dedicated server in the background, opening the client on the same computer and selecting "Singleplayer" at the main menu locks up the game until windows asks to kill the process. Notably while the application is hanging it has stopped responding to winapi events and cannot be alt-tabbed or killed.
How to reproduce
Start a dedicated server
Start a client on the same host
Try to open the singleplayer menu in the client
Expected behavior
There are a couple options here. At a minimum the work being done that currently hangs the thread should be moved off of the UI thread to prevent the application from hanging.
An ideal option would be to show the list of saves, but indicate that the save being loaded by the dedicated server is "unavailable" with maybe an explanation why.
Alternatively, just a hard notification that singleplayer is unavailable while a dedicated server is running would bandaid this.
Game Version: 1.15.2
Platform: Windows Modded: No
Description
When running a dedicated server in the background, opening the client on the same computer and selecting "Singleplayer" at the main menu locks up the game until windows asks to kill the process. Notably while the application is hanging it has stopped responding to winapi events and cannot be alt-tabbed or killed.
How to reproduce
Expected behavior
There are a couple options here. At a minimum the work being done that currently hangs the thread should be moved off of the UI thread to prevent the application from hanging.
An ideal option would be to show the list of saves, but indicate that the save being loaded by the dedicated server is "unavailable" with maybe an explanation why.
Alternatively, just a hard notification that singleplayer is unavailable while a dedicated server is running would bandaid this.