01:26 < bridge> winter depression is a serious illness! 01:39 < bridge> <_voxeldoesart> good 08:54 < bridge> https://bughunters.google.com/blog/4805571163848704/llvm-cfi-and-cross-language-llvm-cfi-support-for-rust 10:11 < bridge> morning 10:26 < bridge> morn 10:27 < bridge> ing 11:20 < bridge> gni 11:21 < bridge> nrom 11:22 < bridge> 🚗 11:50 < bridge> Choo Choo 12:59 < bridge> Hello ! 12:59 < bridge> 12:59 < bridge> I have a little problem, my hook ingame have a delay. 12:59 < bridge> It's not anti-ping, i also try to off/on my pc and is not working :/ 12:59 < bridge> I have a delay of 200 ms on my hook ... 13:17 < bridge> turn off vsync 13:17 < bridge> Hello 13:17 < bridge> i have a problem 13:17 < bridge> so i refreshed DDNet and i have so low fps idk why 13:18 < bridge> how low? 13:18 < bridge> i had 200FPS before 13:18 < bridge> 20FPS 13:18 < bridge> do you know nightly builds? 13:18 < bridge> and its locked so it stucks at 20 max 13:18 < bridge> no 13:18 < bridge> The vsync is off 13:18 < bridge> its off 13:18 < bridge> https://ddnet.org/news/nightly-build-revived/ 13:18 < bridge> 13:18 < bridge> can you try this ^ ? 13:19 < bridge> was the delay always there? 13:19 < bridge> no 13:19 < bridge> i didn't play on my pc since 5 month and when i cb the delay was there but only on my hook the mouvement ect are normal 13:20 < bridge> mh dunno, reset config maybe 13:20 < bridge> rename ddnet in %appdata% for that 13:20 < bridge> else look in your mouse settings 13:20 < bridge> wow i have 340FPS thx 13:51 < bridge> Windows 10 13:51 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1184115357598875768/image.png?ex=658acc5d&is=6578575d&hm=9794e2f5f278fa5f3b6b45b639fe1fa14168a43f4a85d2009a2ea0ebf342555e& 13:53 < bridge> <_voxeldoesart> chad windows 10 user 13:55 < bridge> help pls ❤️ 13:59 < bridge> that's a warning not an error 13:59 < bridge> if you dont show the error nobody here can help 14:02 < bridge> someone really ought to go through and find all inappropriate c style casts and replace them 14:03 < bridge> there is very very very rarely an instance where you need a c cast 14:05 < bridge> c style casts are simpler to type 14:06 < bridge> i rarely ever used c++ casts 14:12 < bridge> c++ make it easier to avoid errors, and they more clearly state the intent 14:12 < bridge> c++ casts make it easier to avoid errors, and they more clearly state the intent 14:14 < bridge> @learath2 do u think a malloc done within a JIT engine from llvm needs to be freed manually (the process calling the jit engine is alive all time) or when the jit engine is done its fred 14:14 < bridge> i wonder if llvm jit has some docs on this 14:14 < bridge> i dunno, i'd not agree with that tbh 😄 14:15 < bridge> @jupeyy_keks best casts are pointer method casts in rust 14:15 < bridge> they are type checked 14:15 < bridge> i mean .cast() ans .const_cast() 14:15 < bridge> Hm, I have no idea on how llvm jit works. You'll have to dig around it's docs 14:16 < bridge> Modern C++ casts look so ugly and are so annoying to type, but they are better in every other aspect 14:16 < bridge> https://doc.rust-lang.org/std/primitive.pointer.html#method.cast_const 14:16 < bridge> my grip is there are lot of types of casts and they have long names 14:16 < bridge> and also ub 14:17 < bridge> i dislike dynamic cast, bcs it's simply overhead. 14:17 < bridge> 14:17 < bridge> const_cast is basically c cast 14:17 < bridge> 14:17 < bridge> and reinterpret cast should be avoided anyway 14:17 < bridge> or static cast 14:17 < bridge> isnt const cast for constness? 14:18 < bridge> i forgot 14:18 < bridge> does it even exist? 14:18 < bridge> oh u mean rust? 14:18 < bridge> its named cast_const xd 14:18 < bridge> *mut to *const 14:18 < bridge> `*mut T ` to `*const T` 14:18 < bridge> `*mut A ` to `*const T` 14:19 < bridge> You almost always want a static_cast, if you are a polymorphism enjoyer a dynamic_cast, if you are an opaque datatype enjoyer a reinterpret_cast and if you are doing blackmagic a bit_cast 14:19 < bridge> @learath2 do u think its sensible to expect the jit malloc and rust libc dep to be same 14:19 < bridge> and would a malloc from inside jit be ok with free from rust with libc 14:19 < bridge> Oh and when you hate that the type system doesn't have nice sane const, you use const_cast 😄 14:20 < bridge> evil answer: garbage collected 14:20 < bridge> <_voxeldoesart> polymorphism fan vs opaque datatype enjoyer 14:20 < bridge> https://cdn.discordapp.com/attachments/293493549758939136/1184122554047283280/image.png?ex=658ad310&is=65785e10&hm=5f1f192bac4342c8d77498ce11c0edcc2e08eaaa2056f15ce5f3f4d0eca896fa& 14:20 < bridge> mmh where you hear that 14:20 < bridge> funny how fast one can forget c++ 😬 14:20 < bridge> i used too much rust lately 14:20 < bridge> Uhh, this is something I have no idea about. If they really both use dynamically linked libc and the same libc, yes 14:20 < bridge> hear what? 14:21 < bridge> i think const cast is used when u face a badly designed api not using const 14:21 < bridge> same bro 14:21 < bridge> Problem is due to how const and overrides work some apis just cant be const correct 14:21 < bridge> actually implementing garbage collection can be orders of magnitude harder 14:21 < bridge> specially if u want a competitive gc 14:21 < bridge> Overloads* 14:21 < bridge> const T *const_ptr; 14:21 < bridge> auto ptr = const_cast(const_ptr); 14:21 < bridge> ill probs just refcount mallocs or smth 14:22 < bridge> Implement mark and sweep gc, go 14:22 < bridge> at my free time i started a weird project 14:22 < bridge> im implementing pascal in mlir 14:22 < bridge> cuz im bad at designing a language 14:22 < bridge> i picked a easy one 14:22 < bridge> avoid reinterpret and static cast 14:22 < bridge> those are the 2 safest 14:23 < bridge> avoid c++ 14:23 < bridge> thats the safest 14:23 < bridge> shut up pls 14:23 < bridge> :3 14:23 < bridge> reinterpret 14:23 < bridge> the word alone is unsafe xD 14:23 < bridge> There are a scant few legit uses of reinterpret cast 14:23 < bridge> hmmm 14:24 < bridge> hard to get much done without it when you have a base type and your derived objects are managed as points of the based type 14:24 < bridge> You almost always want a static_cast 14:24 < bridge> e.g. every object oriented system 14:24 < bridge> that sounds more like dynamic cast 14:24 < bridge> you are casting the ptrs 14:24 < bridge> and dynamic casts have: 14:24 < bridge> - overhead 14:25 < bridge> - can return null ptrs (kinda bcs of above) 14:25 < bridge> @learath2 is there a way to "try to free" a pointer but not segfault if u cant? 14:25 < bridge> bcs they do type checks 14:25 < bridge> dynamic casts arw 100% runtime overhead avoid them 14:25 < bridge> You mean upcasting? 14:25 < bridge> yes 14:26 < bridge> Static casts work just fine there if you already know for sure the type 14:26 < bridge> Someone: »today I made me a toast hawaii« 14:26 < bridge> Ryozuki: »but in rust …« 14:26 < bridge> And a dynamic cast just uses rtti to make sure the type is correct if you dont have another mechanism to figure it out 14:27 < bridge> i mean if the roaster would write "software written in rust" 14:27 < bridge> 14:27 < bridge> i'd buy it just for that 14:27 < bridge> ngl xd 14:27 < bridge> would be insanely funny 14:27 < bridge> Nope 14:27 < bridge> rusty toaster 14:27 < bridge> <_voxeldoesart> funniest rust advocate 14:28 < bridge> that's why when freeing a pointer you shoud set it to nullptr afterwards 14:28 < bridge> The issue with c style casts is the fallback behaviour that no one really knows off the top of their head 14:28 < bridge> that's why when freeing a pointer you should set it to nullptr afterwards 14:28 < bridge> that's why when freeing a pointer you should set it to `nullptr` afterwards 14:29 < bridge> or simply use unique_ptr 14:29 < bridge> welcome to #developer home of rust 14:29 < bridge> non zero cost 😬 14:29 < bridge> <_voxeldoesart> ddnet is still 90% cpp 14:29 < bridge> debugging ptr stuff is also not zero cost 14:29 < bridge> 😏 14:30 < bridge> 😬 14:30 < bridge> rust 14:30 < bridge> I mean I know it off the top of my head but most people just put a cast there and dont care. But you usually dont want it to fallback to reinterpret cast since at that point it's usually a mistake 14:30 < bridge> 😬 14:30 < bridge> 😬 14:30 < bridge> omg learath i wanted to surround it with faces 14:30 < bridge> Nooo bad timing 14:30 < bridge> @learath2 please delete your message 14:30 < bridge> repeating it over and over again does not make it right, you know 14:30 < bridge> xd 14:30 < bridge> lmao 14:30 < bridge> Fixed 14:30 < bridge> @learath2 lmao 14:30 < bridge> we shown u its right tho 14:31 < bridge> <_voxeldoesart> https://tenor.com/view/brick-wall-talk-gif-5290288 14:31 < bridge> i mean tbf, when using LTO, i am not sure 14:31 < bridge> it might or might not be zero cost, depends on how the compiler performs 14:31 < bridge> super low % 14:31 < bridge> It's still not 0 cost but it's like 0.00000001 cost 😄 14:31 < bridge> i see 14:31 < bridge> You get unlucky with caching and it's even 0.000001 cost 14:32 < bridge> my question is when will this actually matter. like who the hell cares. it’s so negligible you’re spending more effort talking about it than people will ever spend trying to counteract it 14:32 < bridge> If you also are still running ancient dram modules it might even be 0.1 cost 14:32 < bridge> idc i use it on my holy fight for rust 14:32 < bridge> :NekoEvil: 14:32 < bridge> <_voxeldoesart> guys be silent im going to become funny to ddnet devs 14:32 < bridge> i like rust but people behaving the way you are is what makes people dislike it 14:32 < bridge> that alone 14:33 < bridge> xDD 14:33 < bridge> is what gives the lang a bad rep 14:33 < bridge> <_voxeldoesart> what even is 100 cost 14:33 < bridge> im trolling a bit but ok 14:33 < bridge> <_voxeldoesart> 😂 😂 windows : 😂 😂 😂 😂 14:33 < bridge> ill fix it for you 14:33 < bridge> c++ best lang 14:33 < bridge> thank god we code in c++ 14:33 < bridge> i see it more as comedy 14:33 < bridge> cpp isn’t usually the best choice 14:33 < bridge> just be realistic 14:33 < bridge> you can’t do rust everything 14:33 < bridge> <_voxeldoesart> comedy involves it being funny 14:33 < bridge> At the scale of cost we are talking about with unique_ptr windows would be like TREE(3) cost 14:34 < bridge> you don't find it funny, how brainwashed he is? 14:34 < bridge> @learath2 realloc moving the ptr to a new addr doesnt mean i got to free the old addr right 14:34 < bridge> ur my libc docs now 14:34 < bridge> <_voxeldoesart> me when i dont find the same joke told 2763 times funny 14:34 < bridge> No, if realloc gives you a new addr that's the one ur responsible with freeing 14:34 < bridge> pointer points to same spot 14:35 < bridge> it's like in animes.. the joke was never funny. it will still be done 50000 more times 14:35 < bridge> thats the neat part, u can do rust everywhere u do c++ 14:35 < bridge> you can’t 14:35 < bridge> only limitation is maybe gcc on a weird platform 14:35 < bridge> that no one uses 14:35 < bridge> but soon thats fixed 14:35 < bridge> with the rust gcc 14:35 < bridge> or maybe existing code and standards and knowledge and experience and unit tests and other infrastructure 14:35 < bridge> you can’t just “”use rust”” anywhere 14:36 < bridge> ah u mean legally bound? i give u that 14:36 < bridge> technically rust can be used everywhere c++ is used 14:36 < bridge> sure 14:36 < bridge> depending upon the revision 14:36 < bridge> thats what i meant 14:36 < bridge> u should learn rust already 14:36 < bridge> i like cpp better 14:36 < bridge> jupstar was rly pro cpp 14:36 < bridge> i remember 14:36 < bridge> bad memory 14:37 < bridge> no 😬 14:37 < bridge> 100% 14:37 < bridge> Well Rust and C++ are both turing complete. You can technically do everything with them 14:37 < bridge> ryo u ask rudimentary cpp questions so i think your perception of pro cpp is a bit different 14:37 < bridge> <_voxeldoesart> you better dip asap 14:37 < bridge> <_voxeldoesart> every second you're around them they're just gonna poke at yoy 14:37 < bridge> It's just that the cost of migrating 2 decades of legacy code is extremely prohibitive 14:37 < bridge> <_voxeldoesart> you better dip asap 14:37 < bridge> <_voxeldoesart> every second you're around them they're just gonna poke at you 14:37 < bridge> im asking this basic stuff cuz i havent used libc for long xd and im lazy to check 14:38 < bridge> just saying 14:38 < bridge> He used to be good. Then he got enlightened by the rust tree and deleted his knowledge of other inferior languages 14:38 < bridge> u rly think my definition of someone pro at a programming lang is knowing library functions 14:38 < bridge> i think u misunderstood what i said 14:38 < bridge> but i am too tired to repeat myself 14:38 < bridge> ok 14:39 < bridge> i will hardly have advanced cpp questions because i literally dont use cpp 14:39 < bridge> and dont want to anymore 14:39 < bridge> advanced rust is more fun 14:39 < bridge> i looked into reinterpret cast and i suppose it’s only uniquely good for opaque data types like incomplete types or void ptrs 14:39 < bridge> but otherwise equivalent to static cast 14:40 < bridge> void ptrs are safe to cast from/to with static too. So only opaque data types and some very niche tricks 14:40 < bridge> i suppose 14:41 < bridge> i don’t see the harm anyway 14:41 < bridge> i feel like in some circumstances casting between void ptrs can get you in trouble with more pedantic compiler settings 14:42 < bridge> strict aliasing? 14:42 < bridge> that reminds me of something but ppl will get too mad 14:43 < bridge> <_voxeldoesart> ryo knowing limits? crazy 14:43 < bridge> @mpft do u know about pointer provenance 14:43 < bridge> "quick google" 14:43 < bridge> yea idk the term lol 14:43 < bridge> https://www.ralfj.de/blog/2020/12/14/provenance.html 14:43 < bridge> is this just about ptr arithmetic 14:44 < bridge> void and char ptrs are allowed to alias anything. So I'm unsure whether it can cause a strict aliasing issue, but even if it can the type of cast won't save you there 14:44 < bridge> true 14:44 < bridge> Pointer provenance is arcane black magic that you will almost never have to care about. I wouldn't even read about it 14:44 < bridge> Especially in C++ 14:45 < bridge> isn’t it just like uint8_t * != uint16_t * because sizeof() for each is different? 14:45 < bridge> It only ever is an issue if you use a placement new 14:45 < bridge> placement new is bonkers stuff that nobody in their right mind should use 14:45 < bridge> 😬 14:45 < bridge> use your words 14:46 < bridge> I’m not reading this blog post 14:46 < bridge> except for the time I recommended it be used for the ddnet kernel object or something 14:46 < bridge> If you are tight on memory there are some uses to it 😄 14:47 < bridge> perhaps 14:47 < bridge> Pointer provenance becomes an issue if you construct a new object of a different type in place of another 14:48 < bridge> provenance distingishes different pointers to the same address, its cuz due to optimizations u can get unexpected results 14:48 < bridge> right 14:48 < bridge> so it’s basically what i said 14:48 < bridge> this one is a rust definition 14:48 < bridge> > The provenance of a pointer is used to distinguish pointers that point to the same memory address (i.e., pointers that, when cast to usize, will compare equal). Provenance is extra state that only exists in the Rust Abstract Machine; it is needed to specify program behavior but not present any more when the program runs on real hardware. In other words, pointers that only differ in their provenance can not be distinguished any more in the final b 14:48 < bridge> The old pointer you held refers to a lifetime that has already ended, thus is technically invalid to access through. Which the compiler can optimize out causing UB 14:49 < bridge> no not exactly 14:50 < bridge> ```c 14:50 < bridge> char p[1], q[1] = {0}; 14:50 < bridge> uintptr_t ip = (uintptr_t)(p+1); 14:50 < bridge> uintptr_t iq = (uintptr_t)q; 14:50 < bridge> if (iq == ip) { 14:50 < bridge> *(char*)iq = 10; 14:50 < bridge> print(q[0]); 14:50 < bridge> } 14:50 < bridge> ``` 14:50 < bridge> this is the example from the blog 14:50 < bridge> i see 14:50 < bridge> As far as C++ is concerned it's about a way to break strict aliasing without invoking UB 14:50 < bridge> preposterous 14:50 < bridge> any way of circumventing optimizations may as well be IB 14:51 < bridge> ub 14:51 < bridge> https://youtu.be/5HXCbLilIzs?si=9YxrUMbpbXZOOONw if you wanna hear about a C++ feature you'll never have any use for 14:51 < bridge> i think i read about it 14:51 < bridge> novice cpp 14:51 < bridge> 😬 14:52 < bridge> what are you talking about 14:52 < bridge> nothing 14:52 < bridge> you know what is funny. 14:52 < bridge> All concepts i now use in rust, were ideas i had long before i've ever touched rust: 14:52 < bridge> 14:52 < bridge> https://discord.com/channels/252358080522747904/293493549758939136/994267418220306462 14:52 < bridge> 14:52 < bridge> https://discord.com/channels/252358080522747904/293493549758939136/966359790672556144 14:52 < bridge> 14:52 < bridge> https://discord.com/channels/252358080522747904/293493549758939136/997967609863602207 14:52 < bridge> 14:52 < bridge> I often agreed that rust solves the memory related stuff. Tbf i did not expect that proc macros solve a few of my issues for logic errors. Besides that i never am _really_ pro any language that exists yet. 14:52 < bridge> I'd need a language that is preventing logic errors to be as fanboy as you are about rust 😬 14:52 < bridge> 14:52 < bridge> I do think rust is better than cpp (with few exceptions), but i am defs less of a fanboy of rust than you think xD 14:52 < bridge> @ryozuki thanks for reading my ted talk 14:52 < bridge> 😬 14:53 < bridge> i also always said if a lang with better borrow checker or same idea comes 14:53 < bridge> My 3 favourite things about rust are: 14:53 < bridge> - Sum types/Error handling 14:53 < bridge> - Traits 14:53 < bridge> - proc_macros 14:53 < bridge> ill be first to switch 14:53 < bridge> 😬 14:53 < bridge> trur 14:53 < bridge> tsur* 14:53 < bridge> I'm not a huge fan of the whole fearless concurrency and automatic memory management. I'm an old man 14:53 < bridge> tsur > rust 14:53 < bridge> invent tsur 14:54 < bridge> Send + Sync, borrowck too smart for me 14:54 < bridge> i just like how it makes so much sense 14:54 < bridge> i leave since it seems ryo is just trying to troll 14:54 < bridge> ??? 14:54 < bridge> xd 14:54 < bridge> get someone’s goat. not sure whose 14:54 < bridge> good night 🌙 14:55 < bridge> If I were to make a language it'd take these 3 and transplant it into a clean version of C 14:55 < bridge> i was just making a snark remark at u for the pro cpp thing 14:55 < bridge> good night! 14:55 < bridge> what do you like about traits, if i may ask? 14:55 < bridge> I'd also steal namespaces from C++ 14:56 < bridge> I like the idea of methods acting on objects. I don't enjoy polymorphism that much though 14:56 < bridge> Traits are a nice compromise 14:56 < bridge> yeah i agree, i still try to generally minimize using them, except for containers or other "global" structures 14:57 < bridge> It gives me methods and a way to define shared behaviour 14:58 < bridge> I probably would also omit the automatic dereferencing in my language. It's just too much to think about for me 14:58 < bridge> uh why 14:58 < bridge> i find modules on rust best 14:58 < bridge> i think my top 3 are: 14:58 < bridge> - enum structs (and ofc the resulting pattern matching) 14:58 < bridge> - proc macros 14:58 < bridge> - easier ecosystem (e.g. adding deps etc.) 14:58 < bridge> actually includes in c c++ are thing of past 14:58 < bridge> well headers are from hell 14:58 < bridge> lets face it 14:58 < bridge> I could take Rust modules too yeah. I need some way to group things together the one namespace in C is so dirty 14:58 < bridge> i never in my life thought: oh now write the shit in headers is so much fun 14:59 < bridge> its harder to parse a header than anything else 14:59 < bridge> what u mean b enums is ADT algebraic data types 14:59 < bridge> <_voxeldoesart> when remove header files 15:00 < bridge> https://en.wikipedia.org/wiki/Algebraic_data_type 15:00 < bridge> this should be basis for any new lang 15:00 < bridge> yep, but e.g. in typescript it completely sucks 15:00 < bridge> without pattern matching it's kinda useless 15:00 < bridge> ye 15:00 < bridge> pattern matching is important 15:01 < bridge> strong typing 15:01 < bridge> 1 thing I like about header files is how they are like a summary of the class. I might have to figure out some way to separate that in my language too 15:01 < bridge> ts has a ez escape hatch from type system 15:01 < bridge> as any 15:01 < bridge> `as any` 15:01 < bridge> true, sometimes reading the functions of a class in headers is easier 😄 15:01 < bridge> rust is also more grepable than c 15:01 < bridge> grep fn 15:01 < bridge> but not smth an editor could not do 15:01 < bridge> to list functions 15:02 < bridge> I might steal the modern function declaration syntax too, but I also don't really want to break "declaration follows use" 15:05 < bridge> i also like i64 15:05 < bridge> vs int 15:05 < bridge> I can also takes lambdas from C++. I'll also need to patch together an async system. Something less fearless 15:08 < bridge> Maybe the idea of executors from rust, impeccable usability of ES6 promises, multiple executors from folly, and a Stream wrapper inspired by rxjs Observable, might make a nice unholy combination 15:09 < bridge> Some sort of coroutines would also be cool but it's a bit difficult to do 15:09 < bridge> do es6 promises finally add yield? 15:10 < bridge> i die without it 15:10 < bridge> No yield still 15:11 < bridge> i mean i only have like 3-4 use cases 15:11 < bridge> Wait which sort of yield are you talking about? 15:11 < bridge> Like yielding a value? 15:11 < bridge> it just hard without a notifier/notify system 15:12 < bridge> since js also doesnt have this 15:12 < bridge> i could live with a yield 15:12 < bridge> Are Observables perhaps what you are looking for? 15:13 < bridge> They are pretty enjoyable to use 15:13 < bridge> i'll look into it 15:13 < bridge> is nodejs thread safe? 15:13 < bridge> well webworkers have only limited functionality 15:14 < bridge> so you dont really have multi threading i'd say 15:14 < bridge> What does it mean for a js runtime to be thread safe? 15:14 < bridge> Chillerdragon you know of an js / ts lib to connect a client with acess to rcon? If not id rather do Network sniffer. If both dont work ill try writing something for reading remote dumps (then ill be sad tho) 15:14 < bridge> You really might have an easier time just building a client that does this 15:15 < bridge> Learning c++ from scratch is easier? 15:15 < bridge> the problem already is: 15:15 < bridge> js / ts have no udp support 15:15 < bridge> i dunno if nodejs has modules for it... maybe 15:15 < bridge> then you could maybe built ddnet to wasm 15:15 < bridge> and use it with js xd 15:15 < ws-client> @Bota yea as jopsti said if it is in the browser it wont work. Are you doing it in the frontend or backend? 15:16 < ws-client> @Bota also nudel said he did not add rcon so it might not work 15:16 < bridge> Ah, I thought you knew C++. Then that's a no go 15:16 < ws-client> @Bota i think my ruby client has rcon and it is really easy to use. Does the server you want it for accept 0.7 connections? 15:17 < bridge> @alex0006 have you ever checked how often log.txt is written by the client? 15:17 < bridge> 15:17 < bridge> i bet u can just add a `flush` somewhere and read from it live 15:17 < ws-client> https://github.com/ChillerDragon/teeworlds_network/blob/97de34f1518018292aa81aae3e0fb7d3ea91d6e0/docs/classes/TeeworldsClient.md#on_rcon_line 15:17 < bridge> then u _almost_ have to not alter the client 15:17 < bridge> Log probably doesnt contain rcon though 15:17 < bridge> I have a web framework for displaying 15:18 < ws-client> yea regular log does not contain rcon 15:18 < ws-client> there is console dump but it is not live 15:18 < bridge> Getting data outside the project is only possible via requests 15:18 < bridge> @alex0006 didnt u just want chat? xd 15:18 < bridge> I need chat data 15:18 < bridge> so no need for rcon right? 15:18 < bridge> I need ips 15:18 < bridge> lmao 15:19 < ws-client> @Jupstar ✪ no need for flush its pretty live 15:19 < bridge> isnt there a e-con? 15:19 < bridge> yeah but you on the master race linux 15:19 < ws-client> o 15:19 < bridge> There is but it's not enabled on ddnet servers and it wouldn't really be available to mods anyway 15:19 < bridge> makes sense 15:19 < bridge>