01:31 <+bridge_> [ddnet] isnt noby banned LOL 01:31 <+bridge_> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/946202564372873246/unknown.png 01:51 <+bridge_> [ddnet] @noby 01:51 <+bridge_> [ddnet] why would he be banned 01:54 <+bridge_> [ddnet] from ddnet? 01:57 <+bridge_> [ddnet] ? 02:05 <+bridge_> [ddnet] yeah hes banned i banned him 03:00 <+bridge_> [ddnet] :nouis: 04:01 <+bridge_> [ddnet] ye he bots all the time 04:01 <+bridge_> [ddnet] if u see him in-game dm me 06:16 <+bridge_> [ddnet] No, but if u just say that I can not know u mean anything with dummy xd 10:59 <+bridge_> [ddnet] @heinrich5991 what do you think about writing the assert messages to disk somehow, else the information is often lost (if not ez to reproduce it might be useful) 11:00 <+bridge_> [ddnet] sounds good. best would be to also write the log to disk somewhere recoverable 11:11 <+bridge_> [ddnet] @deen\: Im sorry if i upset you i will never say anything about putin or russia again so please unban me 11:56 <+bridge_> [ddnet] Maybe we should scan our logs regularly 11:57 <+bridge_> [ddnet] what would be great for the assert message would be to also print a stacktrace 11:59 <+bridge_> [ddnet] drmingw will print a stack trace for windows 11:59 <+bridge_> [ddnet] but sadly no textual information 12:00 <+bridge_> [ddnet] for linux it should be relativly easy to print a stacktrace 12:00 <+bridge_> [ddnet] wait, or do we create a coredump on dbg_assert? 12:00 <+bridge_> [ddnet] that's even better then, no need for stacktrace 12:01 <+bridge_> [ddnet] i dont think we do that rn 12:01 <+bridge_> [ddnet] drmingw just catches illegal instructions 12:01 <+bridge_> [ddnet] but yeah coredump sounds good 12:01 <+bridge_> [ddnet] I mean on Linux, for official servers 12:01 <+bridge_> [ddnet] oh i guess linux does that automatically, if you enable core dumps? 12:01 <+bridge_> [ddnet] because with coredump we have the message, stack, and all context 12:02 <+bridge_> [ddnet] and the core.$pid files are not overwritten a day later 12:04 <+bridge_> [ddnet] yep, works: 12:04 <+bridge_> [ddnet] ``` 12:04 <+bridge_> [ddnet] Core was generated by `./DDNet-Server'. 12:04 <+bridge_> [ddnet] Program terminated with signal SIGILL, Illegal instruction. 12:04 <+bridge_> [ddnet] #0 dbg_break () at /home/teeworlds/src/master/src/base/system.cpp:168 12:04 <+bridge_> [ddnet] b168 __builtin_trap(); 12:04 <+bridge_> [ddnet] [Current thread is 1 (Thread 0x7f6f98d5fb80 (LWP 2357762))] 12:04 <+bridge_> [ddnet] (gdb) bt 12:04 <+bridge_> [ddnet] #0 dbg_break () at /home/teeworlds/src/master/src/base/system.cpp:168 12:04 <+bridge_> [ddnet] #1 dbg_assert_imp (filename=, line=, msg=msg@entry=0x5568b207b8c8 "TEST", test=0) at /home/teeworlds/src/master/src/base/system.cpp:161 12:04 <+bridge_> [ddnet] #2 0x00005568b1fb7ee1 in dbg_assert_imp (filename=filename@entry=0x5568b207bf30 "/home/teeworlds/src/master/src/engine/server/server.cpp", line=line@entry=520, test=test@entry=0, 12:04 <+bridge_> [ddnet] msg=msg@entry=0x5568b207b8c8 "TEST") at /home/teeworlds/src/master/src/base/system.cpp:163 12:04 <+bridge_> [ddnet] #3 0x00005568b1fc5f15 in CServer::Init (this=0x7f6f97fbe010) at /home/teeworlds/src/master/src/engine/server/server.cpp:520 12:04 <+bridge_> [ddnet] #4 0x00005568b1fb82bd in CreateServer () at /home/teeworlds/src/master/src/engine/server/server.cpp:3607 12:04 <+bridge_> [ddnet] #5 main (argc=, argv=) at /home/teeworlds/src/master/src/engine/server/server.cpp:3653 12:04 <+bridge_> [ddnet] ``` 12:04 <+bridge_> [ddnet] https://github.com/ddnet/ddnet/issues/1 12:04 <+bridge_> [ddnet] https://github.com/ddnet/ddnet/issues/2 12:04 <+bridge_> [ddnet] https://github.com/ddnet/ddnet/issues/3 12:04 <+bridge_> [ddnet] https://github.com/ddnet/ddnet/issues/4 12:04 <+bridge_> [ddnet] https://github.com/ddnet/ddnet/issues/5 12:04 <+bridge_> [ddnet] One other thing I wanted to do about this was to keep around the old builds 12:05 <+bridge_> [ddnet] because sometimes I only look into a coredump a few days later, and then we already run a new server version 14:32 <+bridge_> [ddnet] Hey! 14:32 <+bridge_> [ddnet] 14:32 <+bridge_> [ddnet] Would it be possible to perhaps display upcoming map releases on the website? 14:33 <+bridge_> [ddnet] Not so easy with how it's set up at the moment, would have to be manually maintained 14:34 <+bridge_> [ddnet] Aww, thought so \:( 14:35 <+bridge_> [ddnet] can't the bot just read map-releases channel 14:35 <+bridge_> [ddnet] i mean i guess you want it for yourself? 14:36 <+bridge_> [ddnet] the matrix bridge also links to wiki, so doesnt sound so hard to add more channels 15:02 <+bridge_> [ddnet] I'm fine with that aswell, I'm guessing Zwelf is the one in charge of it? 15:03 <+bridge_> [ddnet] yeah, that would be easier, I don't know who runs the bridge bot 15:11 <+bridge_> [ddnet] #ddnet-map-releases\:matrix.org already bridges those map releases. (You can see all currently bridged channels in #ddnet\:matrix.org 15:12 <+bridge_> [ddnet] I plan to selfhost the bridge at some point to bridge the remaining channels to matrix and have more moderating control over it. 15:13 <+bridge_> [ddnet] that would be nice, then i can join back without these insane delays sometimes ^^ 15:14 <+bridge_> [ddnet] Thanks Zwelf, didn 15:15 <+bridge_> [ddnet] Thanks Zwelf, didn't know about that channel as I couldn't find it when searching for it \:D 18:52 <+bridge_> [ddnet] https://blog.rust-lang.org/2022/02/24/Rust-1.59.0.html 18:52 <+bridge_> [ddnet] poggers 18:53 <+bridge_> [ddnet] :PepeA: 18:53 <+bridge_> [ddnet] https://cdn.discordapp.com/attachments/293493549758939136/946464778077999154/unknown.png