New Atomic Bomberman version 2.10 (network protocol version 13) is now available (via auto-updater or get it from my homepage at www.goldencode.de )
This update mostly contains the first pile of stuff which we noticed yesterday evening when doing an intense atomic session

- new gameplay option: no sleepy players. If a player has been inactive for 15 seconds, it will auto-drop a bomb... Highly recommended, especially for network games!

- networking: the master can now manually increase / decrease the waiting-for-clients-countdown by tapping left / right. Yesterday we had a situation where I missed exactly that feature: Erhard was about to join but only 15 seconds remained, so he just missed it and everybody had to quit and rejoin.

- Fix (was uncritical, but...): "toilet mode" isn't a configurable input mapping anymore Forgot to set the non-editable flag for this fixed mapping, which is why the auto-configuration system of my framework made it configurable in the controls menu.

- (maybe) fix, networking: ddni and Erhard reported a weird issue that to me looks as if their network connection was sometimes so instable that some crucial state change packages would pile up - and then suddenly be executed one after the other without any delay. That resulted in situations where it looked as if the scenery was changing all of a sudden - although other players experienced it as what it was: matchend, result-screen, next round. But for them it was more like matchend (or shortly before matchend) -> next round, the result-screen would essentially be skipped or visible as a black screen for one frame. Well, that's my guess because I don't have another explanation So to work around that I extended the network protocol by dedicated sync-commands for those screen-changes. Crossing fingers, untested
Thanks to ddni for recording a video of that phenomenon!

- (maybe) fix, networking: for some Amiga players at least a hard master drop would result in their client to appear frozen. It didn't crash though, it was simply waiting for a TCP timeout on the socket which was closed by the master. Apparently it's no good idea to rely on the TCPIP stack's error handling here. Therefore the master now sends an explicit "server-death"-message to all clients before shutting down. Only tested on Windows so far.
Thanks to Erhard and ddni for reporting!

- made 4711 the default network port for no particular reason other than that I chose it for testing Yes, I know that it's used by other services (just like probably every TCP port) and I don't care at all.

- Windows, auto-updater: the self-deletion of the update installer eventually triggered some stupid antivirus software Disabled the self-deletion step, hope that does the trick.
Thanks to Valentin for reporting and analyzing!

- Windows, auto-updater: now 64 bit executable.

Cheers to Peter Parker, Nico Lichtenberg, Erhard Furtner, ddni and Robert Wahnsiedler (who was a bit too late, but there was a will!), kill you soon!

And don't forget to join the Atomic Discord channel @ https://discord.gg/f2bTg6s !

Tchatching,
Daytona675x / Inqui / Daniel