> 04:40:03 BitBard: @admin: connected to game 23259, then checked out
> two other games, went back to 23259, got the game status window up,
> then an error message
> 04:40:58 BitBard: @admin: logged out, downloaded Public Test build,
> logged in, tried 23259 again, got the same error message - "problem
> connecting to game?"
> Thanks, yeah. Does not surprise me. Code was written with the use
> cases "connect first time as spectator" or "reconnect as alive player
> within 180 seconds" in mind.
>
> For anything else (e.g. reconnect as spectator, where you had been
> connected few mins before, or as dead player), might not work. This is
> because data from a previously-being-connected still lurks around in
> some variables and so the server code chooses the wrong thing to do
> when a client connects with same identity as before.
>
> I mean, there were good reasons why I didn't make a official release
> from the new source code yet - I know this was just a first shot,
> trying things out and fixing the edges is clearly still needed :>)
>
Should try out how it behaves nowadays for
- connecting 2nd time as spectator
- connecting as spectator if one is one of the players (disconnected after dying)