Maybe changing the user ID to be a composite of the normal user ID and the websocket user id. This would mean a new connection would be treated as a new player. Could possibly cause some other issues, like one person appearing to be in the same lobby twice. This could be fixed by requiring the user ID part of the composite be unique per lobby.
Maybe changing the user ID to be a composite of the normal user ID and the websocket user id. This would mean a new connection would be treated as a new player. Could possibly cause some other issues, like one person appearing to be in the same lobby twice. This could be fixed by requiring the user ID part of the composite be unique per lobby.