Most of SPADS code is server-bug proof to a certain extent, that's why since lobby server migration you can see a lot of non-blocking errors in logs such as (non exhaustive list):
Code: Select all
20100812205502 - ERROR - [PerlLobbyInterface] Ignoring CLIENTSTATUS command (unknown user:"SpringRTSRelaySlave1") 20100812215705 - ERROR - [PerlLobbyInterface] Ignoring LEFTBATTLE command (user already out of battle:"shrek") 20100813083040 - ERROR - [PerlLobbyInterface] Ignoring UPDATEBATTLEINFO command (unknown battle:"176") 20100813114541 - ERROR - [PerlLobbyInterface] Ignoring CLIENTBATTLESTATUS command (client "Kazalkon" out of current battle)
SPADS should operate normally anyway, however I found a part of SPADS code which wasn't totally server-bug proof and which is likely to be the cause of today's crash. This should be fixed in SPADS 0.9.2a, which has just been deployed on all SPADS releases.