Your prediction value is pretty high in the image. In that situation your connection probably was so bad that the client couldn't keep the prediction time smooth. It was really jumping that much. I don't think its a problem that the graph is rendered outside the box though.

Hook and unhook are filling out a full tile, a tee is just smaller than a full tile. I feel like stoppers are an excuse to make a bad designed part work somehow instead of coming up with good one, even if they were implemented correctly.

Character size is 28

Tile size is 32


32-28=4

Unfortunately I can't provide trashmap servers in other countries because I only own a server in Germany. There was the idea of hosting trashmap on the official ddnet servers some time ago but back then we only talked about GER. In my opinion this is a good idea also for the other locations. I don't...

Awesome

I'm even against breaking support for new features, but it seems like I'm in the minority there.

Nice idea, but the first part looks terrible ^^

I think vanilla client support shouldn't be dropped just because of the startline issue. Option 1 is obviously not practical and option 2 would require to drop vanilla support. I don't understand option 3, but it sounds promising. Apart from that I would suggest sending vanilla clients a game time t...

How did you solve the "startline issue"?

Seems like the client code uses the synchronized game time (the time displayed on the top of the screen, in ddrace used for the race time) if the synchronized option is on and otherwise uses the local time, which is not synchronized with the server. https://github.com/teeworlds/teeworlds/blob/3e1d02...