So at least between the three of us there seems to be agreement that there should be two options:
(1) Track players who were connected to a game by the time it was started, and allow only these players to reconnect during this game should they get disconnected. This should be active by default (?).
(2) Allow any player to take any CPU or network player slot while a game is in process. This option is off by default and needs to be enabled by the time the game is setup.
With both options, the server admin (whether headless or not) is able to block a client from reconnecting to the in-progress game, so that clients with bad server connectivity cannot spoil the other players' fun
Did I sum this up properly? Do we agree on this summary?
About (1), we need to define how the tracking works. Titi says he's thinking of IP address and pseudo unique (randomly generated number) identifier based bans. I guess this is good enough for now. It could be changed into global player IDs once we have them. It's yet unclear whether with this option, (1), a reconnecting player is allowed to only take the slot she used to have, or may choose any CPU or netork slot. Assumely the intended bahaviour would be that only the original slot can be reused by this player. To be able to enforce this, the server would need to track which user, identified by IP address + unique ID, started in which slot, too.