The static compare methods are significantly
faster than scala's Rich<Prim> compare methods,
and they are equivalent speed to subtraction but
handle edge cases correctly.
- Create a new runtime setting for socket debug info
- When setting is active, bad VersionCheck messages will send additional
info. The client can then report this info together with their current
version. Client reporting not implemented yet, but will be a simple
GET or json post.
* master:
tweak deploy script
Manually apply translations
Socket optimizations
evaluation refactoring: move a few methods around
No 'highly consistent move times' for ultra (except for streaks because highly-premoved sequences are excluded anyway)
Revert "Consistent move time streak assessment: only mid-game"
Consistent move time streak assessment: only mid-game
highly --> moderately where appropriate
Add extra cheating assessment rule
Assessment: take flat move time streaks into account
Assessment simplification: combine blurs and chunk blurs in one player flag
Remove first move time for flat time detection
Remove unnecessary code
Be stricter on highly consistent move times
Assessment: take blur streaks in account
All socket hubs were listening to NbMembers and forwarding
to their sockets.
All websockets pings were containing the members count.
Now only the lobby websocket has it.
Also round count is merged in the pong message
Thibault Duplessis