Not sure which section to post this in, but at any rate, I was wondering if there was any way to prevent the closing of one client closing all other clients and ending a PIE test.
Essentially, whenever I’m testing, if I try to close out of one client to simulate what happens when someone “quits” or an unexpected network disconnect, it closes all clients and ends PIE - much like pressing ESC on any of them or manually stopping PIE. Is it possible to stop this or should this not be happening?
This is a few months old, but no one answered, and this came up as my first google result on the issue…
You can use the disconnect command to make the user disconnect. This will not close their window, but they will leave the server, and load whichever the start level is, but in single player.
In 4.12.5 running “disconnect” on one client disconnects all clients.
Has anybody found another way to do this? It would immensely help us test & reproduce bugs.
I have a pretty decent solution for this. You can make a blueprint callable function in C++ that calls Logout on the game mode. One note: your not really logging out so you need a “bIsLoggingOut” to track once the player “starts logging out” so you can switch off that logic. Lets me test all my disconnect/reconnect logic easy enough though
The onStartTurn event was just me forcing a logout when the player turn started. Suggest makign a “Force Logout” event and call it from wherever.
