- users were in multiple battles at the same time
- users which are offline were in some channel or battle
- other inconsitency...
i've tried to clean the code of the lobby server up, but i failed in detecting its complexity:
there is(was) duplicate code which tries to make data consistent but it still failed in some cases (which were mostly not noticed at client side, but showed up as error messages on server side):
https://github.com/spring/uberserver/bl ... nt.py#L397
i've tried to fix this by remove/rewrite that code but introduced some new bugs which caused A LOT of trouble this weekend. i thought i could fix it within time / fixed it but new errors showed up faster than i could fix it.
i've reverted the current running lobby server to a known mostly well working version.
atm i'm not sure how the lobby server can be fixed without fully rewriting it, so it is 100% consistent.
any help is welcome!
i'm very sorry about the trouble it caused

imo the problems are:
- no (good) automatic testing happens as its difficult to emulate ~200 clients
- i'm mostly working alone on this
- the code of uberserver was already a mess when i started trying to improve it