Teeworlds - bridge

Hardest to understand is probably the stuff in network.cpp. One of the few times I had to pull out a pen and paper to keep track of the packet flow

07:21

Sdl stuff you can usually grasp, if you know sdl to start with

I agree with jxsl, if stuff were commented, it'd way easier tu understand whats going on.

Commenting is harder

Any thought on this? https://github.com/teeworlds/teeworlds/issues/2788

Well I wouldn't call the ddnet tile system easy to extend

It's just hard coding additional layers with a specific functionality

19:24

Allowing multiple game layers that can have additional parameters per tile (like teleport number) would be a start. Mods could use some identifier (uuid?) to actually use these parameters. That would at least reduce the required code but you still need a custom client to modify the maps and ofc a server that can make use of the parameters

i just mean extensible tiles

19:27

just for game layer for start

19:27

thats better in ddnet than in vanilla

well okay... one could restructure the collision code a bit yeah

Do you have any good ideas for that?

19:30

Ah well, you said you dont have so much time yesterday :D

didn't look at that code for quite some time =\

i am working on a """kinda api""" (not really an API, just code exporting xd) for teeworlds modding, so merging with master works better and the whole source doesnt get bloated. For this, i of course also want tiles to be extensible in an easy way

19:34

My work for now https://github.com/fokkonaut/teeworldsmodhook