Jan

I want to refactor my code, so that XStream does not need to use reflection as much. I get `Illegal reflective access by com.thoughtworks.xstream.converters.collections.TreeMapConverter`. I guess it's caused by reflection-based...

+1 Font colours itself are fine for me (same as in js editor), but variable highlighting and bracket highlighting do not seem to be customizable (vars / brackets unreadable with...

@manuelmanhart I'd advise you to switch to something that uses tsserver, like https://github.com/angelozerr/typescript.java or VSCode (even better, dark theme included). With tsserver, you will have a much easier life getting...

@Askaholic Wouldnt it make sense to have the "ready" flag in the message from the client too? That way it would be possible for the client to detect sombody dropping...

Soo... what exactly is the conclusion? Keep match_ready? Add flag? Remove the others? And while we are at it, i find the command name a bit confusing, but i guess...

Yeah i feel it would be cleaner with a flag, so like this: ``` { "command": "match_ready" "ready": true } ```

What format is this `2020-06-18 20:30:26.677218` exactly? Are there other commands where the client receives a date in this format? From what i can see, an ISO 8601 needs a...

Isnt delta time a bit overkill here? The worst thing that happens is that client doesnt understand that match is expired, should not be a big problem i think. I...

Sendiing both relative and absolute times whenever you need to send a time is really the solution to that problem? How often does this problem happen? Should we not make...

Telling the user to fix his time settings is much more reasonable than fixing broken time sync in every time related API call that will ever be added to this...