00:32 < bridge> [teeworlds] u better wait 0.9 01:42 < bridge> [teeworlds] 1.0 KEK 02:49 < bridge> [teeworlds] 0.8 should be a rework of the protocol from ground up 14:30 < bridge> [teeworlds] what do you envision? 14:35 < bridge> [teeworlds] probably tcp for serverinfo/registration/initial connection 14:37 < bridge> [teeworlds] you still need to receive udp for input and gamestate 14:37 < bridge> [teeworlds] http masters? ^^ 14:37 < bridge> [teeworlds] would be great :) 14:38 < bridge> [teeworlds] looks like a huge task though 14:39 < bridge> [teeworlds] i think several people already invested some work into this 14:41 < bridge> [teeworlds] https://cdn.discordapp.com/attachments/490150878934990850/742724271377219604/unknown.png 14:41 < bridge> [teeworlds] hey, i am getting this error constantly on my server for 0.6 master, any ideas? 14:41 < bridge> [teeworlds] yes udp would be used for game packets on tees that have already connected properly 14:41 < bridge> [teeworlds] but the packets that are flooded and spoofed are rarely ever game packets 14:41 < bridge> [teeworlds] theyre inforequests and connect rquests and to a lesser extent master requests 14:41 < bridge> [teeworlds] aah 14:41 < bridge> [teeworlds] and those three things can be tcp 14:41 < bridge> [teeworlds] @fokkonaut disable that message. it's spoofable 14:42 < bridge> [teeworlds] but only on master4 14:42 < bridge> [teeworlds] ? 14:42 < bridge> [teeworlds] then the attackers just use spoofed input messages? 14:42 < bridge> [teeworlds] why would they do that? 14:42 < bridge> [teeworlds] these packets still hit your server 14:42 < bridge> [teeworlds] @heinrich5991 i dont see my server in the 0.6 master 14:43 < bridge> [teeworlds] you can block them earlier in the tw server but best would be in the firewall 14:43 < bridge> [teeworlds] i will just force not to use master4 14:43 < bridge> [teeworlds] but you should also disable that message 14:43 < bridge> [teeworlds] why? 14:43 < bridge> [teeworlds] because it's spoofable 14:44 < bridge> [teeworlds] anyone can send it to you and then your server thinks it's not registered 14:44 < bridge> [teeworlds] so i should completely ignore the packet for 0.6 registering? 14:44 < bridge> [teeworlds] yes 14:44 < bridge> [teeworlds] thanks alot 14:48 < bridge> [teeworlds] worked, thx aagin 14:51 < bridge> [teeworlds] i am getting alot of these now tho, but that is still due to the attack i believe: 14:51 < bridge> [teeworlds] https://cdn.discordapp.com/attachments/490150878934990850/742726856826028092/unknown.png 14:52 < ChillerDragon> @heinrich5991 if the server thinks its not registered does this have some effect on anything? Or just printing error messages? 14:52 < bridge> [teeworlds] yes, it stops the registering process 14:52 < ChillerDragon> @fokkonaut lmao master ban because of the troll dummy report :D 14:52 < ChillerDragon> oh that is crazy! 14:53 < bridge> [teeworlds] xd 14:53 < ChillerDragon> so one can sucessfuly dos a master connection by spoofing master and claiming it didnt work?! 14:53 < bridge> [teeworlds] in 0.6, on master4, yes 14:53 < bridge> [teeworlds] yes 14:53 < bridge> [teeworlds] on all masters 14:53 < bridge> [teeworlds] anderson said only on 4 14:53 < ChillerDragon> 0.7 masters use tokens tho? 14:53 < bridge> [teeworlds] because 1-3 are at servercompass and they have a protection @heinrich5991 14:53 < bridge> [teeworlds] ChillerDragon: yes 14:54 < bridge> [teeworlds] how can they be protected against that? 14:54 < bridge> [teeworlds] i dont know 14:54 < ChillerDragon> servercompass masterrace 14:54 < bridge> [teeworlds] @Mr_Anderson 14:54 < bridge> [teeworlds] then I can't believe that 14:54 < bridge> [teeworlds] or did i misunderstand? 14:54 < bridge> [teeworlds] without evidence 14:54 < ChillerDragon> go attack em and try heinrich xd 14:54 < ChillerDragon> ill report you for attacking masters heueueu 15:07 < bridge> [teeworlds] master 1-3 cant be spoofed, as they're also located at ovh as your server 15:07 < bridge> [teeworlds] ah, that's fine 15:08 < bridge> [teeworlds] master 1-3 cant be spoofed, as they're also located at ovh as your server @fokkonaut 20:50 < bridge> [teeworlds] anyone tried the macos artifacts from github actions? unlike the `make_release.py` variant, cmake does not embed libpng in the dmg file 20:52 < bridge> [teeworlds] doesn't cmake call make_release.py? 20:56 < bridge> [teeworlds] no, does not