1. Open a baseplate
2. Navigate to the “Test” tab at the top of the Studio window
3. Set the player count to be any player count of 2 or more. For this report I set it to 2 players.
4. Once all the clients have loaded, press the “Cleanup” button in one of the client windows. Pressing it in Server or in your development window will allow them to all close properly.
Expected Behavior
All of the test windows will close successfully.
Actual Behavior
One of the client windows will be stuck open. As you can see in this screenshot:
I guess Test Servers and Play Solo function differently, Test Servers are designed to simulate actual client/server behavior, Play Solo is just for quick test or for playing the game so the server and client is run the same (tho server/client processes have been changed to make server and the client have different threads) it just still a listen server so the moment play solo session stops by the host leaving the game, server dies. Similar to a how singleplayer modes for non roblox games work that are built with server/client in mind.
Test Servers are run by having the server and the clients run as seperate instances
Still kinda annoying bug but luckily you can ALT+F4
This happens to me on my Windows PC. Roblox hasn’t fixed this bug along with the bug that prevents you from changing UserInputService.MouseBehavior to Enum.MouseBehavior.LockCenter, so I wouldn’t recommend using the test server until both of these issues are fixed.
From what I have found, it seems that if you cleanup the client, then just that client closes. If you want to clean everything up, click on the cleanup button in the main window where you started the test from. That will cleanup the server and all clients.
However, with that being said, there is a bug. If you close the individual clients, sometimes on subsequent tests if you hit the cleanup button on the main window, it will close the server but not the clients. You have to manually close the clients. The only way to recover from this is to restart studio. That’s been my observation, and that is a bug.
Wow, I didn’t even know there was a forum post for this. This issue has frustrated me for years now, and I never got around to actually making a report for it. Now that Studio is down (again ) I actually made my way over to the forum and saw this!
I don’t believe this is intended behavior. As far as I know, if you press the CleanUp button from anyone of the clients, it shuts down the hosting server, but not all the clients. Then you have to close them all individually. You can close a single client by just closing the window. CleanUp button should ALWAYS clean up ALL test windows.
) I actually made my way over to the forum and saw this!