01:02 <+bridge> [ddnet] what license has ddnet? 01:11 <+bridge> [ddnet] https://github.com/ddnet/ddnet/blob/master/license.txt 06:50 <+bridge> [ddnet] @c0d3d3v Was the HUD resized recently? My custom icons are now super stretched in the most current nightly. 06:50 <+bridge> [ddnet] @c0d3d3v Was the HUD resized recently? My custom icons are now super stretched in the most current nightly, and for what reason was the grid extended?. 06:55 <+bridge> [ddnet] Also, I'm curious what the Extras tab could be used for other than the snowflake. Are there any current plans and ideas for how this image could be used? 11:15 <+bridge> [ddnet] yes it is now 512x512... forgot to tell you 11:16 <+bridge> [ddnet] https://github.com/ddnet/ddnet/blob/master/data/hud.png 11:16 <+bridge> [ddnet] https://raw.githubusercontent.com/ddnet/ddnet/master/data/hud.png 11:21 <+bridge> [ddnet] I thought it would be interesting to use it, for the upcomming particles that could come with the material layer that @Essigautomat implements 11:21 <+bridge> [ddnet] https://github.com/ddnet/ddnet/pull/5403 11:21 <+bridge> [ddnet] 11:21 <+bridge> [ddnet] But maybe it is the best to just combine hud.png and extras.png in one. 11:23 <+bridge> [ddnet] I thought it would be interesting to use it, for the upcomming particles that could come with the material layer that @Essigautomat implements 11:23 <+bridge> [ddnet] https://github.com/ddnet/ddnet/pull/5403 11:23 <+bridge> [ddnet] 11:23 <+bridge> [ddnet] But maybe it is the best to just combine hud.png and extras.png in one, call it `extras.png`? and also add the material particles to it. And probably also the upcomming powerup particles 11:26 <+bridge> [ddnet] it is basically only one icon more, so you just have to expand your canvas 13:15 <+bridge> [ddnet] What do you think about a community art contest for a frozen tee skin, that we can use instead of the ninja skin, till we have some better idea/solution/animation? 15:32 <+ChillerDragon> ou -.- is it possible that spawns are not deterministic if there is only one? 15:33 <+ChillerDragon> https://zillyhuhn.com/cs/.1656423182.png 15:33 <+ChillerDragon> https://zillyhuhn.com/cs/.1656423197.png 15:33 <+bridge> [ddnet] what? If there's only one, you always spawn there 15:34 <+ChillerDragon> Im using the Tutorial map to test wether my clients auto reply to "where are you" is working. And sometimes it responds with "on your right" and sometimes with "on your left". First i thought its a me issue. Maybe integration test script sync issue or the bot determining the position wrong. 15:34 <+ChillerDragon> actually you dont 15:35 <+ChillerDragon> if one already spawned there you get pushed to the side but seems like which side is non deterministic 15:39 <+ChillerDragon> ok nevermind i run it with gfx on 20 times now all good its deterministic 15:39 <+ChillerDragon> that would have been weird 15:54 <+bridge> [ddnet] omg who added this stoopid check of logfile differing from stdout!??!?! we add so much CI shit it never will pass https://github.com/chillerbot/chillerbot-ux/runs/7093804998?check_suite_focus=true 15:54 <+ChillerDragon> i cant even reproduce it locally because it crashes earlier on my bugged nvidia drivers :D 15:57 <+bridge> [ddnet] good question, dunno why this check was added 15:57 <+bridge> [ddnet] git blame? 15:57 <+bridge> [ddnet] or rather, `tig blame`? 15:57 <+ChillerDragon> whats `tig` ?xd 15:58 <+bridge> [ddnet] git in rust i'd say 15:58 <+bridge> [ddnet] https://jonas.github.io/tig/ 15:58 <+bridge> [ddnet] no 15:58 <+ChillerDragon> is it some rust rewrite? xd 15:58 <+ChillerDragon> like bat vs cat etc 15:58 <+bridge> [ddnet] i noticed they all rewrote classic unix utilities in rust and named them backwards 15:58 <+ChillerDragon> eww who needs git ui 15:58 <+bridge> [ddnet] too bad they can't rewrite cat and call it tac πŸ˜„ 15:58 <+ChillerDragon> git cli is fine 15:58 <+ChillerDragon> do u use tig heinrich? 15:58 <+bridge> [ddnet] how do you git blame with the default git UI? 15:58 <+bridge> [ddnet] tig blame is much more usable 15:58 <+ChillerDragon> `git blame file` 15:59 <+bridge> [ddnet] how do you skip uninteresting commits? 15:59 <+ChillerDragon> usually `git blame $(fzf) | less` 15:59 <+ChillerDragon> i use github for that 15:59 <+ChillerDragon> okok i use a ui 15:59 <+ChillerDragon> even a web gui xd 15:59 <+bridge> [ddnet] try `tig blame` 15:59 <+bridge> [ddnet] it's local and fast πŸ˜‰ 15:59 <+ChillerDragon> okok 15:59 <+ChillerDragon> ill keep it in mind thanks 15:59 <+ChillerDragon> ok ill try rn 16:00 <+bridge> [ddnet] you can press 16:00 <+bridge> [ddnet] enter 16:00 <+bridge> [ddnet] to view the commit corresponding to the current line 16:01 <+bridge> [ddnet] or press comma to go to the commit before the one on the current line 16:01 <+ChillerDragon> i tig blame deen axaxaxaxaxax 16:01 <+ChillerDragon> https://zillyhuhn.com/cs/.1656424870.png 16:01 <+ChillerDragon> doess `-u` not need an arg? 16:02 <+ChillerDragon> i mean its not the issue im just wondering 16:02 <+bridge> [ddnet] I get chillerdragon? c951a3cb899aae63c4df65ad6e34a3f41b0565e1 16:02 <+bridge> [ddnet] `-u` is default number of context line 16:02 <+ChillerDragon> but where is the number 16:02 <+bridge> [ddnet] `-U 1` if you want one context line in unified format for example 16:02 <+ChillerDragon> https://zillyhuhn.com/cs/.1656424940.png 16:02 <+ChillerDragon> but deen did -u logfile 16:02 <+bridge> [ddnet] `-u` means it's 3 16:02 <+ChillerDragon> a 16:02 <+bridge> [ddnet] per default 16:02 <+ChillerDragon> oke 16:02 <+ChillerDragon> implicit 16:03 <+ChillerDragon> if its default why even use -u ? xd 16:03 <+bridge> [ddnet] to get the more common diff format 16:03 <+bridge> [ddnet] unified is easier to read 16:03 <+bridge> [ddnet] otherwise it's some strnage stuff with > and < 16:03 <+ChillerDragon> a 16:03 <+ChillerDragon> now i get it 16:03 <+bridge> [ddnet] https://github.com/ddnet/ddnet/commit/c951a3cb899aae63c4df65ad6e34a3f41b0565e1#diff-04a82e40ebe59c2140090275278cca1f75de61dd099b6b6ebdfaf201584fe87eR287-R288 16:03 <+ChillerDragon> ye looks hot 16:03 <+bridge> [ddnet] this looks like you added a check whether the log file differs from stdout 16:03 <+bridge> [ddnet] no? 16:03 <+ChillerDragon> yes i did 16:03 <+ChillerDragon> i was trolin a bit 16:03 <+ChillerDragon> :D 16:04 <+ChillerDragon> why dis bitch breaking on me 16:04 <+bridge> [ddnet] because threads 16:04 <+ChillerDragon> race condigtion in stdout vs logfile xd 16:04 <+ChillerDragon> bra 16:04 <+bridge> [ddnet] and each log output handles synchronization differently 16:04 <+ChillerDragon> or so do | sort | diff? xd 16:05 <+bridge> [ddnet] you can do that, actually πŸ˜„ 16:05 <+ChillerDragon> would then lose order bugs 16:05 <+ChillerDragon> but yea probably better than race condition false positives 16:05 <+bridge> [ddnet] or ignore the lines that can be in a different position before diff 16:05 <+bridge> [ddnet] timestamps are done by the logging system, so they're equal across logging targets 16:05 <+ChillerDragon> which mf wrote that threaded loggin? xd 16:06 <+bridge> [ddnet] I did 16:06 <+ChillerDragon> ye ts looks good 16:06 <+ChillerDragon> ik u did 16:06 <+ChillerDragon> im fan 16:06 <+ChillerDragon> should we actually sort and then diff? -.- 16:06 <+ChillerDragon> then reading the diff is confusing 16:07 <+ChillerDragon> because its sorted 16:07 <+ChillerDragon> how would you ignore lines? just grep -v them? but then they could be missing. also sounds like one has to update the ci everything threading stuff changes 16:07 <+ChillerDragon> omagawd 16:08 <+bridge> [ddnet] yeah, sorting is easier and at least an improvement over flaky tests 16:08 <+ChillerDragon> i wonder if its possible to show an unsorted diff afterwards 16:08 <+ChillerDragon> if that even would make any sense 16:09 <+ChillerDragon> ou 16:09 <+ChillerDragon> can we force single threaded? xd 16:09 <+ChillerDragon> lock to one cpu core whatever 16:09 <+bridge> [ddnet] not for logging coherency 16:09 <+bridge> [ddnet] just sort it πŸ˜› 16:09 <+ChillerDragon> heinrich can u fix the stdout implementation and make it not bad? 16:10 <+ChillerDragon> hrhr 16:10 <+ChillerDragon> im gonna get a shitstorm if one encounters a sorted diff issue 16:10 <+ChillerDragon> if not from others from future me for sure xd 16:10 <+bridge> [ddnet] the diff will just show if lines are missing or added one has to manually look at the text files 16:11 <+bridge> [ddnet] are the output files of the integration test uploaded as artifacts? 16:11 <+ChillerDragon> MaNuaLlY 16:11 <+ChillerDragon> na 16:11 <+bridge> [ddnet] or you print the original files when you find any mismatch 16:11 <+ChillerDragon> sure we can run it with some -v flag in the CI 16:11 <+bridge> [ddnet] would be useful if the entire integration_test folder gets zipped and uploaded 16:11 <+ChillerDragon> yikers 16:12 <+ChillerDragon> m$ will bill us 16:12 <+ChillerDragon> so much bandwith 16:12 <+ChillerDragon> nah idk honestly 16:12 <+ChillerDragon> somehow ddnet never gets into gh limits 16:12 <+ChillerDragon> im sure rich deen secretly pays 16:13 <+bridge> [ddnet] time to build our own integration test server :thonk: 16:13 <+ChillerDragon> i tried for gh 16:13 <+ChillerDragon> sucked 16:13 <+ChillerDragon> i tried for gl 16:13 <+ChillerDragon> rocked 16:14 <+ChillerDragon> i mean a own ci pipeline runner 16:14 <+ChillerDragon> not sure wat u have in mind 16:14 <+ChillerDragon> ofc we can also just schedule a cronib that does git pull && test on some raspberry pi 16:14 <+bridge> [ddnet] yeah, something like that 16:15 <+ChillerDragon> but then how to alert after push 16:15 <+ChillerDragon> lmao send a email to the commit author 16:15 <+ChillerDragon> xxxxxxxxxxxxxxD 16:15 <+bridge> [ddnet] can you not hook github actions? 16:15 <+ChillerDragon> that would be hilarious 16:15 <+ChillerDragon> wdym hook? 16:15 <+bridge> [ddnet] with git you can hook actions to trigger commands and such 16:15 <+ChillerDragon> a 16:16 <+bridge> [ddnet] so if someone pushes on master it sends a mail to some mailing list for exmaple 16:16 <+bridge> [ddnet] example* 16:16 <+ChillerDragon> so everyone is forced to run integration tests after every commit? 16:16 <+ChillerDragon> u mean post commit hook? those are pain 16:16 <+ChillerDragon> imagine waiting 30 mins to commit xd 16:16 <+bridge> [ddnet] do they work with github? 16:16 <+ChillerDragon> its gh unrelated 16:16 <+ChillerDragon> its git 16:16 <+ChillerDragon> your local git runs some script 16:16 <+ChillerDragon> after commit 16:17 <+bridge> [ddnet] ah, only locally ok 16:17 <+ChillerDragon> ye thats the worst 16:17 <+ChillerDragon> i like the pi idea tho 16:17 <+ChillerDragon> and it somehow making noise 16:17 <+ChillerDragon> maybe i should do that for my projects where i run into gh limits 16:18 <+bridge> [ddnet] just buy more raspberry pis for parallel integration tests :kek: 16:18 <+bridge> [ddnet] we are getting closer to replicating microsoft 16:18 <+ChillerDragon> 1 pi can go para af alr 16:18 <+ChillerDragon> pis are strong compuiters 16:18 <+ChillerDragon> MULTI CORE 4K DESKTOP WORKSTATIONS one could say 16:18 <+bridge> [ddnet] can we just deploy test commits to some users that opt into experiments with their game? XD 16:19 <+ChillerDragon> wot? 16:19 <+bridge> [ddnet] microsoft deploys features tests to just some systems first 16:19 <+bridge> [ddnet] you can use software to deactivate this behavior "Experiments" 16:20 <+ChillerDragon> ou ye 16:20 <+ChillerDragon> you mean like the A/B testing thingy 16:20 <+bridge> [ddnet] yeah 16:20 <+ChillerDragon> imagine in the ddnet client menu ui 16:20 <+ChillerDragon> you can checkbox pullrequests pending on ddnet repo 16:20 <+ChillerDragon> :D 16:20 <+ChillerDragon> ez remote code execution 16:21 <+ChillerDragon> i honestly thought about tuning my mergeconflict warn system bot into a auto merge pr bot 16:22 <+ChillerDragon> so then every time i boot up my pc it tries to merge in as many ddnet prs into my client and i could alpha test all the shit combined xd 16:22 <+bridge> [ddnet] zlib 16:22 <+ChillerDragon> because current master is not bleeding edge enough 16:22 <+ChillerDragon> wot zlib? 16:22 <+bridge> [ddnet] why use that license over others? 16:22 <+bridge> [ddnet] zlib ddnet license 16:22 <+bridge> [ddnet] who talks about zlib? 16:23 <+bridge> [ddnet] did some reply got lost in the bridge? 16:23 <+bridge> [ddnet] where is that coming from xd 16:23 <+ChillerDragon> i think the license is inherited from tw 16:23 <+bridge> [ddnet] https://choosealicense.com/licenses/zlib/ 16:24 <+ChillerDragon> prolly a random chil license good ol magnus came up with 16:24 <+bridge> [ddnet] nono im just suddenly here 16:24 <+ChillerDragon> wait where does it even say zlib? 16:24 <+ChillerDragon> license.txt only mentions it for external/ 16:25 <+bridge> [ddnet] it's the zlib license 16:25 <+bridge> [ddnet] i checked if the text is the same 16:25 <+bridge> [ddnet] it doesnt say it 16:25 <+ChillerDragon> i am not going to say anything further 16:25 <+bridge> [ddnet] https://www.teeworlds.com/?page=docs&wiki=licensing_misc 16:25 <+ChillerDragon> without my lawyer jopstar being here 16:27 <+bridge> [ddnet] > * It complies to the OSI definition: http://www.opensource.org/docs/definition.php 16:27 <+bridge> [ddnet] > * It complies with Debian Free Software Guidelines: http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg 16:27 <+bridge> [ddnet] > * The license is the result of a week long discussion with input from a license expert at Fedora. 16:27 <+bridge> [ddnet] > * The whole OSS thing have started to take more time then it's actually worth. 16:27 <+bridge> [ddnet] > * No, it will not get changed because you complain. 16:27 <+bridge> [ddnet] >The license is the result of a week long discussion with input from a license expert at Fedora. 16:28 <+bridge> [ddnet] > The license is the result of a week long discussion with input from a license expert at Fedora. 16:28 <+bridge> [ddnet] haha 16:29 <+bridge> [ddnet] ChillerDragon: why is your commit description shorter than the PR description? πŸ˜› 16:29 <+ChillerDragon> I am used to from the old days to do that 16:30 <+ChillerDragon> because pre bors the pr desc didnt end up in the git log and i would add my marketing talk for the merge gods there and extra details etc. but dont like that to pullte the git logs 16:30 <+bridge> [ddnet] im not into licenses, but i know gpl needs to stay gpl. mit is quite few restrictions, but what is the special about zlib? (i am forking dddnet and want to understand the license) 16:30 <+bridge> [ddnet] im not into licenses, but i know gpl needs to stay gpl. mit is quite few restrictions, but what is special about zlib? (i am forking dddnet and want to understand the license) 16:31 <+bridge> [ddnet] im not into licenses, but i know gpl needs to stay gpl. mit is quite few restrictions, but what is special about zlib? (i am forking ddnet and want to understand the license) 16:31 <+ChillerDragon> @cauldron the legal landscape in tw is chil when it comes to code 16:31 <+ChillerDragon> the artist might want you in jail for looking at their textures without buying their nft 16:32 <+ChillerDragon> but the code is pretty much do what you want 16:32 <+ChillerDragon> (THIS IS LEGAL ADVICE. I AM A LAWYER) 16:32 <+ChillerDragon> the code base is there to be used and extended. the community is small if one is sad about you raping code they will tell you. 16:33 <+bridge> [ddnet] read this: @cauldron https://en.wikipedia.org/wiki/Zlib_License 16:33 <+bridge> [ddnet] or the actual license. it's like 3 paragraphs 16:33 <+bridge> [ddnet] ok, so idk isnt there a "standard" open.source license. 16:33 <+bridge> [ddnet] can i just make my modifications licensed under MIT license? 16:33 <+bridge> [ddnet] ok, so idk isnt there a "standard" open source license. 16:33 <+bridge> [ddnet] can i just make my modifications licensed under MIT license? 16:34 <+ChillerDragon> yes u can change to MIT 16:34 <+ChillerDragon> nobody will probably ever care even if you break all of the 3 rules of the zlib license 16:34 <+bridge> [ddnet] but then i have two licenses in the repo? 16:34 <+bridge> [ddnet] why don't you just keep the old license if you don't care about it? ^^ 16:34 <+bridge> [ddnet] and how to mark what codevhas what license? 16:34 <+bridge> [ddnet] zlib is very permissive 16:35 <+ChillerDragon> maybe he wants less permissive 16:35 <+ChillerDragon> add a license comment at the top of every file xxxxxxxxxxxD 16:35 <+bridge> [ddnet] naa, i don't trust things i don't know. and i don't know zlib. i know MIT. 16:35 <+ChillerDragon> zlib is much simpler than MIT 16:35 <+bridge> [ddnet] but reading also isn't an option? 16:35 <+bridge> [ddnet] > This software is provided 'as-is', without any express or implied 16:35 <+bridge> [ddnet] > warranty. In no event will the authors be held liable for any damages 16:35 <+bridge> [ddnet] > arising from the use of this software. 16:36 <+bridge> [ddnet] no warranty that the software is useful for anything 16:36 <+bridge> [ddnet] > Permission is granted to anyone to use this software for any purpose, 16:36 <+bridge> [ddnet] > including commercial applications, and to alter it and redistribute it 16:36 <+bridge> [ddnet] > freely, subject to the following restrictions: 16:36 <+bridge> [ddnet] you can do anything with the software, as long as you do the following: 16:36 <+ChillerDragon> omagawd heinrich did you just merge my untested pr 16:36 <+ChillerDragon> u crazy bitsh 16:36 <+bridge> [ddnet] > 1. The origin of this software must not be misrepresented; you must not 16:36 <+bridge> [ddnet] > claim that you wrote the original software. If you use this software 16:36 <+bridge> [ddnet] > in a product, an acknowledgment in the product documentation would be 16:36 <+bridge> [ddnet] > appreciated but is not required. 16:36 <+bridge> [ddnet] you must not say that you created teeworlds 16:36 <+bridge> [ddnet] > 2. Altered source versions must be plainly marked as such, and must not be 16:36 <+bridge> [ddnet] > misrepresented as being the original software. 16:37 <+bridge> [ddnet] you must say that your software isn't the original teeworlds 16:37 <+bridge> [ddnet] i read that i have to mark the changes i have made to the "original" codebase with zlib 16:37 <+bridge> [ddnet] you have to abide by this condition no matter if you change the license or not 16:37 <+bridge> [ddnet] that makes sense to me 16:37 <+bridge> [ddnet] > 3. This notice may not be removed or altered from any source distribution. 16:37 <+bridge> [ddnet] you must keep the license near the software 16:38 <+bridge> [ddnet] ok 16:38 <+ChillerDragon> @cauldron i would like to use my right to receive your changed version of the code base 16:38 <+bridge> [ddnet] ChillerDragon: you have no such right πŸ˜‰ 16:38 <+ChillerDragon> please send me paper printed version or CD roms with pdf within 2 weeks 16:38 <+bridge> [ddnet] i don't know any other product released with zlib. 16:38 <+bridge> [ddnet] zlib 16:39 <+bridge> [ddnet] lol xd 16:39 <+bridge> [ddnet] it's the most widely used compression library 16:39 <+bridge> [ddnet] probably in every program that you can think of 16:39 <+bridge> [ddnet] ill use it, okok ill use it 16:39 <+bridge> [ddnet] https://en.wikipedia.org/wiki/Category:Software_using_the_zlib_license huh 16:40 <+bridge> [ddnet] not so much, but: SDL/SDL2, NSIS, Box2D and LΓΆve 16:40 <+ChillerDragon> wow there is a list of 10 entries and tw didnt even make it in 16:40 <+ChillerDragon> heinrich go edit wiki 16:40 <+ChillerDragon> im sure u got like a high elo wiki acc 16:40 <+bridge> [ddnet] but it said at choosealicense.com where they summarize the license, that you have to mark the changes you have made - i guessbto the "original" codebase 16:41 <+ChillerDragon> are you hobby law student or why u care that much? 16:41 <+bridge> [ddnet] so sdl2 is zlib too, okay thats an argument 16:41 <+ChillerDragon> well linux is gplv2 isnt it 16:41 <+ChillerDragon> doesnt mean you should ever touch that 16:42 <+bridge> [ddnet] @cauldron it seems there might be a misconception. you can choose a different license that people using your fork will additionally need to comply with. you can't remove the original license in that sense. you will always be bound by teeworlds's license as long as you modify it 16:42 <+bridge> [ddnet] no no, just try to annoy you xd 16:43 <+ChillerDragon> love it 16:43 <+ChillerDragon> u can annoy me as long as you want 16:43 <+ChillerDragon> i am getting paid per hour 16:43 <+bridge> [ddnet] so mark my changes - what does that mean? i mean git makes it quite obvious what changes you made to the code 16:44 <+bridge> [ddnet] since the new update my skins doesn't show up ingame even with these 2 settings on 16:44 <+bridge> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/991353313121550456/unknown.png 16:44 <+ChillerDragon> then add a changes.txt and write in there "git makes it obvious" 16:44 <+bridge> [ddnet] since the new nightly update my skin doesn't show up ingame even with these 2 settings on 16:44 <+bridge> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/991353313121550456/unknown.png 16:44 <+bridge> [ddnet] I think that's enough 16:45 <+bridge> [ddnet] that you put it into git 16:45 <+ChillerDragon> if you drop git tho you might end up in court 16:45 <+bridge> [ddnet] anyway ill just use it, ty 16:46 <+ChillerDragon> ill send you the bil 16:46 <+ChillerDragon> l 16:48 <+bridge> [ddnet] check the console for errors with the name of the skin; share the skin if you don't mind 16:49 <+bridge> [ddnet] oh whats this? 16:49 <+bridge> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/991354553066864650/unknown.png 16:50 <+bridge> [ddnet] my skin is "MummyBear" btw 16:50 <+bridge> [ddnet] Oh, libpng is in too 16:51 <+bridge> [ddnet] Is there a line like that for MummyBear? 16:51 <+bridge> [ddnet] no not really 16:53 <+bridge> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/991355658265964574/unknown.png 16:53 <+bridge> [ddnet] maybe this means something 16:54 <+bridge> [ddnet] Nothing about skins 16:54 <+bridge> [ddnet] its just weird 16:55 <+bridge> [ddnet] i also had a problem like that a few days ago but i fixed it with checking the setting to download community skins 16:55 <+bridge> [ddnet] but now it just doesn't show my skin at all 17:06 <+bridge> [ddnet] ``` 17:06 <+bridge> [ddnet] Then copy fng.cfg from the root directory to the build directory``` 17:07 <+bridge> [ddnet] is write on the GitHub page but I don't understand root directory and build directory(and I'm french and I'm not really good at English) 17:10 <+bridge> [ddnet] Root directory is the folder that has the src folder in it 17:10 <+bridge> [ddnet] @soitak111 keep your questions in one channel please 17:10 <+bridge> [ddnet] Build directory is the folder you created called build I presume 17:35 <+bridge> [ddnet] do u use skins.tw? 17:35 <+bridge> [ddnet] https://ddnet.tw/skins/skin/community/MummyBear.png 17:35 <+bridge> [ddnet] 17:35 <+bridge> [ddnet] its defs in the database 17:40 <+bridge> [ddnet] @heinrich5991 17:40 <+bridge> [ddnet] [2022-06-28 17:39:45][png]: color type 3 unsupported by pnglite 17:40 <+bridge> [ddnet] [2022-06-28 17:39:45][png]: refusing to load PNG because it would be unsupported by pnglite 17:40 <+bridge> [ddnet] 17:40 <+bridge> [ddnet] i assume this is false positive? 17:40 <+bridge> [ddnet] if its in the skin database 17:40 <+bridge> [ddnet] also the file name wouldnt hurt 17:41 <+bridge> [ddnet] If it used to load with pnglite it is definitely a false positive 17:41 <+bridge> [ddnet] (RC can load it) 17:53 <+bridge> [ddnet] i did add skins.tw to ddnet but my skin is from ddnet database 17:53 <+bridge> [ddnet] yeah nvm already tested 17:55 <+bridge> [ddnet] idk what the newest nightly update is supposed to do but it broke my skin 18:11 <+bridge> [ddnet] yeah bcs heinrich added trash code 18:31 <+bridge> [ddnet] is there a way to see stars that popped up when u were frozen on newest nightly build ? 18:40 <+bridge> [ddnet] no, they're server-side. They still appear on KoG for example 19:56 <+hababa_> woah 19:57 <+hababa_> its so strange to chat in quakenet wow 19:58 * hababa_ slaps hababa_ around a bit with a large fishbot 22:11 <+bridge> [ddnet] what is quakenet? 22:11 <+bridge> [ddnet] an IRC network 22:11 <+bridge> [ddnet] https://www.quakenet.org/ 22:11 <+bridge> [ddnet] you connect to it using an IRC client or using the webchat link 22:16 <+bridge> [ddnet] what does irc stand for: i'm really cool? 22:18 <+bridge> [ddnet] wikipedia could help you 22:18 <+bridge> [ddnet] hehe....i know it's internet relay chat, but i never joined the club of "irc users" 22:18 <+bridge> [ddnet] "internet relay chat" 22:19 <+bridge> [ddnet] so quakenet is the server and there is something like a channel that mirrors discord? 22:23 <+bridge> [ddnet] some day i will be irc user and use mutt for emails... 22:34 <+bridge> [ddnet] some day ? that thing is a demon from the past πŸ˜„ 23:10 <+bridge> [ddnet] xD just open a irc client, join server, and say "bye I now use Discord" ... then you was an IRC user 23:11 <+bridge> [ddnet] xD just open an irc client, join server, and say "bye I now use Discord" ... then you was an IRC user 23:12 <+bridge> [ddnet] or better \me was an IRC user, BYE! 23:19 <+bridge> [ddnet] Wait, mutt is old now? It's the modern alternative to pine... 23:24 <+bridge> [ddnet] Now I went down the rabbit hole, the manpage of mail has an interesting history part: https://man.archlinux.org/man/mail.1#HISTORY 23:43 <+bridge> [ddnet] ddnet is old too