00:06 < bridge> @fokkonaut hey did you find the way around targetx/y zoom problem? 00:50 < bridge> No tell me more 00:50 < bridge> I think something went viral a bit which increased player count. deen mentioned that iirc 00:51 < bridge> F 01:12 < ws-client> why did you add this btw @jxsl13 https://github.com/teeworlds-go/huffman/blob/b632fb8631af0ef31d72c36a9fed1e1001496b4c/.github/workflows/main.yml#L17-L22 01:14 < bridge> syntax check on readme.md changes usually not that interesting for compulation 01:15 < bridge> compilation 01:18 < bridge> so there is a global variable that is called DefaultDictionary 01:20 < bridge> that is initialized with the default teeworlds frequencies upon package initialization and is more or less global state which is reused for for every constructor that does not take a custom dictionary. 01:20 < bridge> that is why the tree/dictionary is not initialized upon every huffmann.Compress/Decompress call. 01:20 < bridge> Ah nice 01:21 < bridge> a pointer is passed around 01:21 < bridge> Well the readme was full of bugs so it’s checked in CI too now 01:21 < bridge> I don’t see the disadvantage of the default CI what’s the problem of the CI running when just a config or text file was changed? 01:22 < bridge> wasting resources 01:22 < bridge> So you are saving the planet? Xd 01:22 < bridge> I do my part 😄 01:22 < bridge> in a rational way 01:22 < bridge> Sure fine with me. Just took me 1 CI run to debug why the README.md wasn’t triggering CI 01:24 < bridge> can you release a new version if possible 01:24 < bridge> tag 01:25 < bridge> Ok 01:25 < bridge> should not exactly break the api except for the small behavioral change where empty slices are accepted as well 01:25 < bridge> and init is gone ._. 01:25 < ws-client> wot init 01:26 < bridge> breaks api lil bit 01:26 < bridge> the method 01:26 < ws-client> a 01:26 < ws-client> was never user facing 01:26 < bridge> well 01:26 < bridge> minor version bump .____. 01:26 < bridge> btw 01:27 < bridge> you can click on the godoc reference badge 01:27 < bridge> and jump straight to docs 😄 01:29 < ws-client> nono we went straight to 2.0.0 @jxsl13 the user never called Init but the api changed 01:29 < ws-client> ye i noticed its cool @jxsl13 01:29 < bridge> major updates are slightly harder 01:30 < bridge> can you remove the tag again 01:30 < ws-client> nope :p 01:30 < ws-client> why 01:30 < bridge> add a /v2 suffix in the go.mod 01:30 < ws-client> we can just tag again 01:30 < ws-client> aaaa 01:30 < bridge> and then add the tag again if I'm not mistaken 01:31 < bridge> I'm usually below v1 in order to introduce breaking changes whenever I want, cuz lazy 01:31 < bridge> 01:31 < bridge> x) 01:31 < ws-client> https://zillyhuhn.com/cs/.1720049474.png 01:31 < ws-client> you mean this? 01:31 < bridge> chillerdragon: how do I quit my job 01:31 < bridge> yes 01:31 < ws-client> axaxaxa @tsfreddie u alr did 01:31 < bridge> I mean that suffix exactly 01:32 < bridge> ok then 01:32 < ws-client> time to send heinrich an email again xd 01:34 < bridge> eeh 01:34 < bridge> all imports need also to be fixed 01:34 < bridge> what? you can do that? 01:34 < ws-client> i just noticed wtf thats annoying af 01:34 < bridge> throughout the code to have that /v2 suffix 01:35 < ws-client> thanks for the warning -.- 01:35 < bridge> that's a major change for you xD 01:35 < ws-client> i guess we ping heinrich again 01:35 < bridge> https://go.dev/doc/modules/major-version 01:36 < bridge> and update the readme D: 01:36 < bridge> /v2@latest 01:36 < bridge> ._. 01:37 < bridge> Translate yapabiliyormu 01:37 < bridge> denied 01:37 < bridge> Okey 01:39 < ws-client> i will get banned from go packages one day for sure 01:39 < ws-client> i renamed the protocol repo 3 times on github my lsp auto import was trippin hard 01:39 < ws-client> now i recreated one tag 3 times xd 01:39 < bridge> ad long as nobody pulled 01:40 < bridge> is fine xD 01:40 < bridge> or imported 01:41 < bridge> ._: 01:41 < ws-client> the latest didnt work sos 01:41 < bridge> lemme fix the readme 01:41 < ws-client> thank 01:44 < bridge> I don't even know where that's coming from 01:44 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1258206738587582505/Bildschirmfoto_2024-07-04_um_01.43.36.png?ex=668733d6&is=6685e256&hm=9f9de33ff84b3dbe6622574face687235df6680f6f082c7848f18e8fbf970f41& 01:44 < bridge> xD 01:44 < bridge> hard tabs 01:44 < ws-client> https://zillyhuhn.com/cs/.1720050267.png 01:44 < ws-client> me neither 01:44 < ws-client> discord banned me from seeing their images 01:45 < bridge> rip 01:45 < ws-client> common discord L 01:45 < bridge> gimme rot access to yout image server thingy 01:45 < bridge> root 01:46 < ws-client> <:justatest:572499997178986510> 01:46 < bridge> so that I can upload my screenshot 01:46 < ws-client> that is my vps 01:46 < bridge> xd 01:46 < ws-client> i upload with `scp` 01:47 < ws-client> i saw now 01:47 < ws-client> ye that is `go fmt` for you @jxsl13 01:47 < ws-client> if you break format in readme the CI will slap your ass now 01:48 < bridge> indeed 01:48 < ws-client> your electron editor seems opinionated about tabs vs spaces in a fakin markdown file xd 01:50 < bridge> that's vs code D: 01:50 < bridge> I literally don't even know where that's coming from 01:50 < ws-client> have you tried emacs? 01:50 < bridge> first time seeing 01:50 < bridge> I heard of emacs 01:51 < bridge> and then I used sublime text and now vs code 01:51 < bridge> will not touch anything else for now 01:51 < bridge> opened a pr 01:51 < ws-client> merged 01:52 < bridge> ci works, nice 01:52 < bridge> retag? 01:52 < ws-client> <:poggers2:1008007455936094328> 01:52 < ws-client> no 01:52 < ws-client> its only readme change 01:53 < bridge> :'/ 01:53 < ws-client> the build was already passing on the last commit 01:53 < bridge> that's godoc relevant readme 01:53 < ws-client> omagawd xd 01:53 < bridge> it's versionng the docs 01:53 < ws-client> nah we fix it in v3 01:53 < bridge> pls 01:53 < ws-client> omg i did 01:53 < bridge> lord 01:53 < ws-client> so many rlses 01:53 < bridge> xD 01:53 < ws-client> im brushing my teeth sec 01:54 < bridge> now let me do my go do url magic 01:54 < bridge> go doc 01:54 < bridge> to update go docs 01:55 < bridge> :'/ 01:57 < ws-client> i wonder if heinrich got 5 emails now xd 01:57 < ws-client> rlsd 02:00 < ws-client> @jxsl13 all good now right? 02:00 < ws-client> then ill go find some coffee 02:00 < bridge> no magic today 02:01 < ws-client> arent u tired jxsl? 02:01 < ws-client> what time is it? 1 am? 02:01 < bridge> 2am 02:02 < ws-client> woah 02:09 < bridge> importing works just fine 02:09 < bridge> https://pkg.go.dev/github.com/teeworlds-go/huffman/v2 02:21 < bridge> what are you making teeworlds-go for? just the lulz? 02:26 < bridge> saw chiller doing it, wanted to help a little bit 02:26 < bridge> found it cool 02:36 < ws-client> @learath2 im on some mission to spread teeworlds to as many languages as i can before i rq coding 02:36 < ws-client> so ppl can build tw projects in their fav language 02:37 < bridge> Noble quest 02:37 < ws-client> do i see that correctly? is the client really storing empty snapshots? xd 02:39 < ws-client> maybe after the 100 robsti refactors ddnet isnt im using tw 0.7 02:40 < bridge> who wants to play some teeworlds of any kind 02:40 < bridge> bored rn 02:40 < bridge> #developer lfg 02:40 < ws-client> but from my dbg prints it looks like it uses the m_aSnapshotIncomingData buffer as payload for snap empty and stores it xd 02:40 < ws-client> https://zillyhuhn.com/cs/.1720053493.png 02:42 < ws-client> i wonder if the server creates deltas against empty snapshots 02:43 < ws-client> i somehow do not want to store empty snapshots with some old payload xd 02:44 < ws-client> also is it weird that the hexdump kinda makes sense to me xd i stared so long at debug prints i can read most (non huffman compressed) tw traffic as hex xd 03:03 < ws-client> Nvm it doesnt use old data. That was a bug in the teeworlds engine xd. It uses the empty snapshot as incoming delta and then does store basically the old snapshot. 03:04 < ws-client> so its wasting a bit of storage imo but at least its not doing anything weird 04:15 < ws-client> https://zillyhuhn.com/cs/.1720059289.png 04:15 < ws-client> is that a bug? 06:19 < bridge> i am hitting this assert in my custom fork quite often and its pretty annoying https://github.com/ddnet/ddnet/blob/610381d29e560ec64f2f42f6be9fdddc7f6df0f9/src/engine/shared/http.cpp#L421 06:19 < bridge> 06:19 < bridge> am i doing something wrong? its either me having network hiccups or the backend dieing. Either way i dont want my client to crash. 06:19 < bridge> not sure if im just using the every changing http code incorrectly https://github.com/chillerbot/chillerbot-ux/blob/a39c3f65f65c4d90c377d68bf893526e2a3ed48f/src/game/client/components/chillerbot/chillerbotux.cpp#L43-L59 06:28 < bridge> Ok got it https://github.com/chillerbot/chillerbot-ux/commit/3204a95fd7e137151db0ddbf863692a784265023 i guess i was doing the state handling wrong 06:41 < ws-client> so much chat.zillyhuhn.com downtime these days yikes. Im bakk! 06:41 < ws-client> https://zillyhuhn.com/cs/.1720068089.png 06:48 < bridge> Забирайте S.T.A.L.K.E.R 2 предзаказ на свой Steam Бесплатно https://tinylinks.ru/i27qq не знаю баг это или нет но я забрал 06:56 < bridge> Wdym? 07:31 < bridge> gm 07:31 < bridge> gm 07:32 < bridge> TargetXY scales with the zoom nowadays which is very odd since you can hit less angles when zoomed in due to the scaling of integers. So when you zoom in/out your aim changes 07:33 < bridge> Ah, yea that thing 07:33 < bridge> No, I haven't looked into that since heinrich seems unbothered. 08:20 < ws-client> @teero777 holy shit that sounds bad 08:20 < ws-client> so if i aim lock some nasty edge and then do a quick zooz i might fail the hook? 08:30 < bridge> yes 09:08 < bridge> ddnet fps on my setup sucks so bad 09:08 < bridge> 400-500 fps but feels very choppy 09:09 < bridge> There's an issue already 09:09 < bridge> theoretically vsync is disabled and the game is renning in real full-screen mode but it doesn't feel that way 09:09 < bridge> theoretically vsync is disabled and the game is running in real full-screen mode but it doesn't feel that way 09:09 < bridge> https://github.com/ddnet/ddnet/issues/8452 09:39 < bridge> i dunno how but i made this by shooting once in tp thingy for grenade :justatest: 09:39 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1258326283948003342/image.png?ex=6687a32c&is=668651ac&hm=c164a9f05cf56835ad611ff237c3c0765f57c74c6fbe6dfbd441661bbbb74a6c& 09:41 < bridge> Duplicating entities? 09:41 < bridge> you only shot once? 09:41 < bridge> yes 09:41 < bridge> weird 09:42 < bridge> but it stops when i look away from tp thingy 09:42 < bridge> even though i didn't hold shoot 09:42 < bridge> :thonk: 09:45 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1258327879146799157/wot.mp4?ex=6687a4a8&is=66865328&hm=9ea9a89d9beba5ec12042e9602a006938d2a4fca160caddd32e9077fac20936f& 10:32 < bridge> antiping? probably the client trying to predict which teleporter next 10:35 < bridge> same happens without antiping 10:49 < bridge> Classic duplication glitch. Back in 2018 we used to do that with carpets … oh wait wrong game 10:55 < bridge> chillerdragon: you can simply keep an empty init function 10:55 < bridge> so that there's no breaking change 11:05 < bridge> I just held shoot button before pressing spec and it was shooting when I was in spec :pepeW: 11:48 < bridge> Does other player see the same thing 11:49 < bridge> would be pretty crazy if we really have a duplication glitch which seems pretty unlikely 12:27 < bridge> why did anyone want to scale it with zoom as multiplier 12:29 < bridge> having it as an unscaled world position is nice for some things 12:30 < bridge> the server knows where the client points to 12:31 < bridge> Failed to bridge media: attachment too large (48141924 > 20000000) 12:31 < bridge> 12:31 < bridge> Yum. 12:34 < bridge> Hmmm 12:38 < bridge> Do I have something to do now? 12:38 < bridge> <0xdeen> Nope 12:41 < bridge> Not even updating a translation? 12:41 < bridge> Not even updating the translation? 12:41 < bridge> <0xdeen> no, it's just a bug fix release 12:41 < bridge> <0xdeen> no translation changes 12:41 < bridge> Okaay 12:42 < bridge> https://github.com/teeworlds/teeworlds/issues/2071 12:42 < bridge> was thought to be fixed 5 years ago. but it wasn't ^^ 12:44 < bridge> is there any chance to revert this change btw? 12:44 < bridge> there's a chance to fix the bug 12:44 < bridge> but I think it's good that the server knows where the client points to 12:44 < bridge> which one? 12:44 < bridge> that your angle depends on the zoom level 12:45 < bridge> couldn't we just add zoom multiplier as extended attribute in the past xd 12:45 < bridge> why should the server do the calculation there? 12:46 < bridge> it seems much more well-defined for the client to tell the server where exactly it is pointing 12:46 < bridge> why would you need clients sending two different type of targetxy? 12:46 < bridge> up-to-date clients only send one type of targetxy, no? 12:46 < bridge> yeah but what about other clients huh 12:47 < bridge> you can recognize them based on the version number, if you need to 12:48 < bridge> anyway its strange to change players input behaviour that old servers can rely on 12:48 < bridge> is there a server that relied on that? 12:49 < bridge> i bet there was 12:49 < bridge> at least fokkonaut was mad when this came out 12:49 < bridge> I'd think the situation improved with this change 12:49 < bridge> no longer needing to rely on brittle hacks to determine the actual cursor position 12:49 < bridge> when will 0.7 support be dropped 12:50 < bridge> no plans. why do you ask? @reitw 12:50 < bridge> cuz there's no reason to still support a dead game 12:50 < bridge> so m_Pos + m_Target is hacky? 12:50 < bridge> please take your flamebait elsewhere 12:50 < bridge> and m_Zoom multiplier 12:51 < bridge> ig there might be features that anyone would love to be implemented that requires breaking the compat with 0.7 ? 12:51 < bridge> let's talk about it once we get that hypothetical feature idea 12:51 < bridge> not really flamebaits but facts, anyone knows how dead 0.7 is sadly 12:51 < bridge> this discussion isn't interesting, we've had it too many times 12:51 < bridge> vanilla players try to revive it though 12:52 < bridge> by playing only on aeon servers and refusing to enter bridge ones xd 12:52 < bridge> there's prob less than 100 or even 50 players 12:52 < bridge> please take this discussion to #off-topic if you want to continue it 12:53 < bridge> (unless you have new information, which I doubt) 12:53 < bridge> yeah true 13:01 < bridge> I don't plan to continue, but once there was mentioned stuff like a skeleton for people who wants to use ddnet base for custom mods. 13:01 < bridge> without 0.7 ddnet could have easily worked on smth to have server-side content (idk like custom guns, etc..) allowing more cool mods to be developed by the community. 13:01 < bridge> or even when you've all talked about the networking improvement part (to allow more efficient protections to be developed around). even if Davide has a workaround the most annoying thing that makes it more difficult to improve is the support to legacy clients 13:02 < bridge> > ddnet could have easily worked on smth to have server-side content (idk like custom guns, etc..) allowing more cool mods to be developed by the community. 13:02 < bridge> sounds cool, let's do that 13:02 < bridge> > even if Davide has a workaround the most annoying thing that makes it more difficult to improve is the support to legacy clients 13:02 < bridge> I don't even know if Davide has a workaround for 0.7 clients or not. but if not, that'd be fine 13:03 < bridge> I'm not sure what you're talking about. I don't think we had a feature declined because it couldn't work with 0.7 13:03 < bridge> recently you've talked about having tcp first for conn handling 13:03 < bridge> we can drop 0.7 support if it stands in the way of improvement 13:03 < bridge> yes, let's do that 13:04 < bridge> and m_Zoom multiplier would do the trick, ddnet wouldn't accept "player input changes" if it would break (ddnet) servers behaviour but this one just got through #8372 13:04 < bridge> and m_Zoom multiplier would do the trick, ddnet wouldn't accept "player input changes" if it would break (ddnet) servers behaviour but this one just got through #7512 13:10 < bridge> Is there really any benefit to that. Maybe it'll help with some firewall implementations. Do we even know if any of our hosters do it? 13:11 < bridge> davide said it'd help him tremendously 13:27 < bridge> So we just accept tcp connections then close them? Or do we need it alive? 13:27 < bridge> just open a tcp connection and that's it. we can close it immediately 13:27 < bridge> like to https://ger10.ddnet.org/ 13:28 < bridge> Oh doesn't have to be the exact port? 13:28 < bridge> no, just somewhere 13:28 < bridge> I'd just fire and forget a https request 13:28 < bridge> I think we even have an issue 13:28 < bridge> I think we even have an issue for it 13:29 < bridge> Perhaps we can also make this more generic? Allow servers to advertise a verify link 13:29 < bridge> https://github.com/ddnet/ddnet/issues/8210 13:32 < bridge> This issue says on the same port 13:33 < bridge> @davide55 does the TCP handshake need to be on the same port number as the UDP port number? 13:35 < bridge> <0xdeen> I don't think so, TCP and UDP ports are not related in any way, you can just have each server announce it's tcp-handshake-ip-port-combo 13:36 < bridge> I would also not think so, but I'd also not have guessed that a TCP handshake would help at all 13:38 < bridge> When I first heard it I assumed it's some bizarre firewall behaviour 13:43 < bridge> No 13:45 < bridge> fixed it 14:06 < bridge> You talkin go Huffman? Well the api changed from an unitialized raw go struct to the weird go styled fake constructor new function. Since I have no users I don’t mind to do breaking changes anyways xd 14:09 < bridge> Imo 0.6 should be dropped 14:11 < bridge> chillerdragon: the rules also apply to you. go to #off-topic for flamebait topics 14:14 < bridge> Yo btw when bridge off-topic? 14:14 < bridge> I thought it already was bridged 14:14 < bridge> only to matrix 14:14 < bridge> he's requesting IRC 14:14 < bridge> ah, probably never to irc 14:14 < bridge> Matrix cring 14:14 < bridge> not on my priority list right now 14:14 < bridge> although I agree that having an IRC bridge is kinda cool 14:15 < bridge> When leak priority list 14:15 < bridge> the bridges are literally only being used by 1 or 2 people for legitimate purposes and is only a tool to dodge moderation on discord 14:16 < bridge> why 14:16 < bridge> Yes 50% of those 1 or 2 ppl is me and I am a big supporter of no moderation @learath2 14:16 < bridge> its really cool 14:16 < bridge> Bugged and bloated. IRC is just so much smoother 14:16 < bridge> irc is the very best 14:16 < bridge> dont tell me you hate matrix bots 14:16 < bridge> good point. but I like having at least one non-proprietrary method to access our chat. I guess matrix is good enough for that 14:16 < bridge> thats the best part 14:17 < bridge> When non proprietary map submissions 14:18 < bridge> Matrix.org instance is basically proprietary xd 14:18 < bridge> why support an redefined and at the same time, slightly abandoned engine? 14:18 < bridge> why support a redefined and at the same time, slightly abandoned engine? 14:18 < bridge> I would setup a selfhosted matrix instance but I just don’t like it enough 14:18 < bridge> chillerdragon: ddnet matrix isn't hosted on matrix.org 14:19 < bridge> Well I am using matrix.org xd 14:19 < bridge> that's on you 14:19 < bridge> Sent from element on iOS 14:19 < bridge> Yes on me 14:20 < bridge> @cellegenrih: wat engine xd 14:20 < bridge> 0.7 14:20 < bridge> Yea it’s frustrating Oy is so inactive lately 14:21 < bridge> so inactive "lately" 14:21 < bridge> "lately" 💀 14:21 < bridge> this isn't a change 14:21 < bridge> lately 14:21 < bridge> He used to be more active imo 14:21 < bridge> brother I havent seen him since 0.7.4 14:21 < bridge> bro went missing for over a year 14:21 < bridge> https://en.wiktionary.org/wiki/lately 14:22 < bridge> "recently" "not too long ago" 14:22 < bridge> Yea I don’t recall ever waiting this long for oy return 14:22 < bridge> XDDD 14:22 < bridge> 4 years ago is still not too long ago right? 14:22 < bridge> Then another question, why wait for Oy? 14:22 < bridge> we have deen right here :owo: 14:22 < bridge> and heinrich 14:22 < bridge> because no one can be bothered to maintain teeworlds, including oy 14:23 < bridge> or chillerdragon 14:23 < bridge> deen and Heinrich don’t merge my 0.7 pr 14:23 < bridge> or chiller ye 14:23 < bridge> what 0.7 pr 14:23 < bridge> vote chiller for next engine creator 2k24 14:23 < bridge> you mean 0.7 features in ddnet? 14:23 < bridge> 0.7 support for ddnet client 14:23 < bridge> He had a sudden burst of activity there for a sec 14:23 < bridge> Which sec? 14:24 < bridge> You mean last time when he looked at 30% of the prs? 14:24 < bridge> I don't remember exact dates but I put in some work into editor2 and added the chat command menu thing 14:24 < bridge> oh cool, how would it work? 14:24 < bridge> for something to change, you need an active maintainer 14:24 < bridge> Bru that was like 2016 14:24 < bridge> if there's no one, there's no point in debating this 14:24 < bridge> oh cool, how would it work? (nvm) 14:25 < bridge> do you volunteer to maintain teeworlds? chillerdragon? 14:25 < bridge> Oy could assign some 14:25 < bridge> we would need a person first 14:25 < bridge> No 14:25 < bridge> find a volunteer and if I think they're even half-qualified I'll help you bring teeworlds back alive 14:26 < bridge> You guys need someone who knows the engine inside out and is willing to change certain ways the engine could function 14:27 < bridge> robsti 14:27 < bridge> Obv the 2 creators have different ideas in mind, they would rather just redo the engine from scratch 14:27 < bridge> have you asked whether he wants to maintain teeworlds, chillerdragon? 14:27 < bridge> this needs to be a volunteer 14:27 < bridge> not someone you assign 14:27 < bridge> I don’t recall I think we had that discussion before so I guess we don’t have anyone 14:28 < bridge> well thats fucked 14:28 < bridge> see. there's the problem. try to fix that 14:28 < bridge> No need for new teeworlds stuff anyways imo 14:28 < bridge> Just finally update ddnet to 0.7 and all good 14:28 < bridge> how so? to improve the way the engine could work, it needs to be done 14:29 < bridge> The game works well 14:29 < bridge> chillerdragon: if you mention porting ddnet to 0.7 without any new content one more time, I'm going to ban you for flamebiat 14:29 < bridge> Yes it does work, however it doesn't support things which can make it out of this era (0.6) 14:30 < bridge> 0.7 ain't some revolutionary aspect, where we can freely mod things or get more gamemodes without limitations 14:30 < bridge> The engine is no exception for this and modders or server devs have a harder time developing their own ideas without reinventing the wheel 14:30 < bridge> 0.7 isn’t about revolution or features it’s just keeping up with compatibility 14:31 < bridge> I swear to god, if I waited 6 years for a not revolutionary client, 14:31 < bridge> then it deserves not to be called a newer "teeworlds" 14:31 < bridge> Are you actively waiting? 14:31 < bridge> Still, yes, but not from ddnet developers naturally 14:31 < bridge> Yea the version breaking changes are a bit unfortunate 14:32 < bridge> porting ddnet to 0.7 in the current state of 0.7 is never going to happen 14:32 < bridge> I can guarantee you that. no current maintainer wants that 14:32 < bridge> it has been discussed with no ends 14:32 < bridge> I plan to make a new map editor, another is making a 2d to 3d render on their own engine using server data, one tried to make a rust compatibility 14:32 < bridge> Im seriously interested in a approximate priority list of yours @heinrich5991 14:33 < bridge> Where can I vote? Xd 14:33 < bridge> I plan to make a new map editor, another is making a 2d to 3d render on their own engine using server data, one still tries to make a fully functional rust compatibility 14:33 < bridge> chillerdragon: I'm currently extracting the compatibility code of ddnet 14:33 < bridge> look at this PR I just made at work, negative line count, still adds an entire feature 14:33 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1258400290357379082/image.png?ex=6687e819&is=66869699&hm=d2a1ac85dedf383a6bbcb4b0a5c00a9cc97b2ca10927e628121c57246407286a& 14:33 < bridge> even though my number one priority should be implementing QUIC 14:33 < bridge> and then accounts 14:34 < bridge> I’d like to give libtw2 snaps, ddnet proxy, ddnet ip redirects, \#7777 some priority votes hehe 14:34 < bridge> this is honestly not worth your time imo, the other two are far more important, we worked around the compatibility code for a decade now, we can handle a couple more years 😄 14:34 < bridge> I told you to proxy support instead -.- 14:35 < bridge> I know, but we're currently getting more compat code which I don't like. on two fronts, even 14:35 < bridge> add another decade to the list boys 14:35 < bridge> also, this could be reused should we want to integrate it into Jupstar's ddnet 14:35 < bridge> 10x developer 14:35 < bridge> chillerdragon: I'm accepting 20€/h to temporarily change my priority list 14:36 < bridge> btw, how are you planning on doing it? 0.7 and 128p support all require pretty intimate knowledge of the gamestate, will you be hooking in for that or will you be trying to recreate the state on a separate module? 14:36 < bridge> Xd 14:36 < bridge> Im broke 14:36 < bridge> separate module 14:36 < bridge>