Teeworlds - bridge

starting to not-suck at this game, lol

I repeatedly hear that anti Ping is the biggest reason to not update to 0.7 Could some brain please look into that :/

Yeah well, it's the only large client modification that wasn't ported afaik. I'm not familiar with that at all

@trml

My understanding why this wasn't put in Teeworlds is that there is no good way to implement this for PvP. e.g. grenades push people

the one in the ddnet client works quite fine imho

the one in ddnet is very complex xd not easy to port

especially pvp players complain about missing antiping. And grenades are predicted well in ddnet 0.6

Okay :)

The ddnet antiping is quite complex. For now prediction for other players, projectiles and rocket jumps would be okay I think. Projectiles and other players shouldn't be that hard. Rocket jumps are a bit more work... You need to simulate the rocket before the server knows about it

how to create a app icon for linux and macOS ?

15:05

I used some png to ico web converter but i only get default/invalid icons

Getting very few servers on 0.7.4 master. Somehow my modified 0.7.3 client loads all the servers, consistently. weird

that reminds me i got access to a server to host another master

15:50

…in july

oh, cool...

technically if we make the simulation of the game an own module on client and server side

16:14

i could do a prediction with bsplines

You can just share all the physics related code between server and client. For the local character they already use the same code. You could also do this for projectiles but then you can't change physics after a release without breaking the prediction.

16:25

Gamecore should be migrated to lua/wasm/whatever so the server can send its code to the client

yeah

sooooo

17:33

I have a question

17:33

how hard would it be to theoretically make a browser version of this game?

17:33

that interfaces with the standard servers

17:34

I mean, what does the api look like to communicate positions of the players and trajectories etc?

No udp (except for webrtc) -> high latency -> no fun

well that's the thing

17:36

I'm thinking like a golang backend

17:36

and just offput the latency onto the browser

You could use websockets but this would also need support for it in the tw server. And because it uses tcp it would not be very responsive

if YOU want to play the probably-slightly-slower browser ver, good on you/better availability