kick issue with windows build

[StarryWisdom]

Hermes bug report from Donovan:
I was able to successfully test the GM-Comms from my system, so I know it's supported with my AWS server (port is open). However, when I did that and kicked the Weapons console, I had issues respawning the ship. I had one computer running the GM Console, and another that was connected to all stations on the ship. When I kicked Weapons, it took the one computer back to console selection. Even when I disconnected and reconnected, I couldn't get the original ship to respawn in the simulation.

[StarryWisdom]

attempt at reproduction of bug on local machine was as follows

start server, 2 clients & hermes
client 1 -> ship 1 all stations
client 2 -> ship 2 all stations
start a game with the TSN sandbox (version about a week old)
spawn in sabre and horizon via mainscreen
connect gm client
kick weapons on ship 1
kick weapons on ship 2
as expected client 1 & client 2 now are in the "we are connected but cant do anything" (like after a server crash)
disconnect & reconnect client 1 & 2 both connect correctly and ships control correctly

as such I was unable to reproduce it locally, ideally I need a explict step by step reproduce the bug so as to remove moving parts in this

[astrolamb-gaming]

Update from Donovan :
I'm going to hazard a guess that the culprit was the screen_connect.lua file. It probably prevented the ship from respawning as a legitimate ship type? I updated the file this morning, and I'm unable to duplicate the issue tonight.

[StarryWisdom]

I would be very surprised if it was hermes_connect.lua
My suspicion is that its lag and the artemis sync bugs we have seen before
If we cant reproduce it then it probably doesnt matter regardless
I will leave this open until I get a point to try to reproduce myself, if I cant and no one else manages to in the mean time I will close it

[StarryWisdom]

current GM client and hermes works in testing, will test on the AWS server before I close this