00:00 <+bridge> <chillerdragon> Was a reply to deleted fokko message :/
00:05 <+bridge> <teero777> so no yo?
01:22 <+bridge> <fokkonaut> Heisenberg deleted it not me
01:22 <+bridge> <fokkonaut> Aswell as yours
01:26 <+bridge> <fokkonaut> chillerdragon: how do you see deleted messages from irc?
01:44 <+bridge> <alw5> freekebs
01:45 <+bridge> <alw5> sbek eerf
05:58 <+bridge> <headshotnoby> 🪀
07:52 <+bridge> <chillerdragon> irc protocol doesn’t have a delete feature. It’s also the client holding the chat log not the server. On irc I never know if a message got deleted or not. I will only notice when I check matrix after that.
08:58 <+bridge> <teero777> ladybird is looking good recently
09:15 <+ChillerDragon> > Lady Bird is a 2017 American coming-of-age comedy drama film written and directed by Greta Gerwig
09:15 <+bridge> <manikoo> T
09:16 <+ChillerDragon> i was watching klings yt videos back in the day thinking it would increase my coding skills
09:57 <+bridge> <milkeeycat> Did it increase your coding skills?
09:58 <+bridge> <milkeeycat> I was watching https://youtube.com/playlist?list=PLhJkqAQmOh5LyYOfnMy4PJB6CSZltQyTc&si=y88HtBdzpI7MuQVP thinking it would increase my coding skills
10:00 <+bridge> <melon> :justatest:
10:03 <+bridge> <boxymaloxy> how does GitHub work
10:25 <+bridge> <jxsl13> https://docs.github.com/en/get-started/start-your-journey/hello-world
10:40 <+ChillerDragon> @milkeeycat xd tbh kling actually was part of my inspiration for this series
10:40 <+ChillerDragon> idk if it did maybe a bit
10:53 <+bridge> <milkeeycat> when make a new ddnet/tw coding series :D
14:01 <+bridge> <chillerdragon> Do people still watch that? New devs just vibe it I think
14:29 <+bridge> <cellegenrih> github is a database, where projects can be stored and managed there.
14:29 <+bridge> <cellegenrih> slangs makes it harder to understand what exactly is going on on github so here's a bit cheatcode:
14:29 <+bridge> <cellegenrih> 
14:29 <+bridge> <cellegenrih> repo = main project (that can be Teeworlds' source code as an example)
14:29 <+bridge> <cellegenrih> branch = different clones of the project (where selecting a clone can let you modify anything without affecting the original version, also called 'main' most of the time)
14:29 <+bridge> <cellegenrih> pull = getting updates from projects (either by request or forcefully, almost no distinction between the two)
14:29 <+bridge> <cellegenrih> push = applying new changes to projects (when we use the term 'push', we think of 'force push' where we don't manage first hand how the change my affect the project)
14:29 <+bridge> <cellegenrih> commit = specific changes combined into one report (consider it as a list of changes on a paper)
14:29 <+bridge> <cellegenrih> PR (also known as Pull Request) = requesting your change to be present on the original version (or any selected 'branch' clone) of the project. Moderation is key.
14:29 <+bridge> <cellegenrih> issue = well... your issues of course (like creating a post where you either complain about a feature, request a new feature, or highlight some code which may be wrong or needed discussion. Either way, it's just someone or multiple people yapping.)
14:30 <+bridge> <cellegenrih> github is a database, where projects can be stored and managed there.
14:30 <+bridge> <cellegenrih> slangs makes it harder to understand what exactly is going on on github so here's a bit cheatcode:
14:30 <+bridge> <cellegenrih> 
14:30 <+bridge> <cellegenrih> repo = main project (that can be Teeworlds' source code as an example)
14:30 <+bridge> <cellegenrih> branch = different clones of the project (where selecting a clone can let you modify anything without affecting the original version, also called 'main' most of the time)
14:30 <+bridge> <cellegenrih> pull = getting updates from projects (either by request or forcefully, almost no distinction between the two)
14:30 <+bridge> <cellegenrih> push = applying new changes to projects (when we use the term 'push', we think of 'force push' where we don't manage first hand how the change might affect the project)
14:30 <+bridge> <cellegenrih> commit = specific changes combined into one report (consider it as a list of changes on a paper)
14:30 <+bridge> <cellegenrih> PR (also known as Pull Request) = requesting your change to be present on the original version (or any selected 'branch' clone) of the project. Moderation is key.
14:30 <+bridge> <cellegenrih> issue = well... your issues of course (like creating a post where you either complain about a feature, request a new feature, or highlight some code which may be wrong or needed discussion. Either way, it's just someone or multiple people yapping.)
14:31 <+bridge> <cellegenrih> That one is more of a tutorial, than an understatement
14:35 <+bridge> <reitw> + note that some keywords here are github specific
14:35 <+bridge> <reitw> not the same on other platforms
14:35 <+bridge> <reitw> actually only PR isn't the same on Gitlab
14:37 <+bridge> <aegisub> um akshually gitlab no longer has issues
14:37 <+bridge> <aegisub> they're called work items now
14:37 <+bridge> <reitw> they changed it ? :KEKSad: tf
14:37 <+bridge> <cellegenrih> With this cheatcode, I can confidently form a sentence which can be understood as multiple simple steps.
14:37 <+bridge> <cellegenrih> 
14:37 <+bridge> <cellegenrih> On my **repo**, instead of **pushing** your changes to **main**, make a new **branch** with your **commits** and make a **PR** about it.
14:37 <+bridge> <cellegenrih> 
14:37 <+bridge> <cellegenrih> Can be understood as:
14:37 <+bridge> <cellegenrih> In my project, instead of uploading your changes to the original version, create a clone of the original where your changes can be tested out safely without affecting the project, then make a request to use your changes.
14:37 <+bridge> <cellegenrih> https://cdn.discordapp.com/attachments/342454474117218334/1458623773048574054/image0.gif
14:38 <+bridge> <reitw> looks like work items is generic
14:38 <+bridge> <reitw> https://docs.gitlab.com/user/project/issues/ issues is a work items type
14:39 <+bridge> <reitw> https://docs.gitlab.com/user/project/issues/ issues is a work item
14:40 <+bridge> <cellegenrih> Ohh, inside the dashboard
14:40 <+bridge> <cellegenrih> I thought they changed the name "issues" in the github repo frontend side lmao
14:56 <+bridge> <reitw> https://docs.gitlab.com/user/project/issues/ issues is a work item
15:46 <+ChillerDragon> woke cellegen using main branch
15:47 <+ChillerDragon> master branch masterrace
16:01 <+bridge> <cellegenrih> imo depends on the person what's being considered as the "original"
16:01 <+bridge> <cellegenrih> imo depends on the person what's being considered as the "original" or "production ready"
16:02 <+bridge> <cellegenrih> github is a database, where projects can be stored and managed there.
16:02 <+bridge> <cellegenrih> slangs make it harder to understand what exactly is going on on github so here's a bit cheatcode:
16:02 <+bridge> <cellegenrih> 
16:02 <+bridge> <cellegenrih> repo = main project (that can be Teeworlds' source code as an example)
16:02 <+bridge> <cellegenrih> branch = different clones of the project (where selecting a clone can let you modify anything without affecting the original version, also called 'main' most of the time)
16:02 <+bridge> <cellegenrih> pull = getting updates from projects (either by request or forcefully, almost no distinction between the two)
16:02 <+bridge> <cellegenrih> push = applying new changes to projects (when we use the term 'push', we think of 'force push' where we don't manage first hand how the change might affect the project)
16:02 <+bridge> <cellegenrih> commit = specific changes combined into one report (consider it as a list of changes on a paper)
16:02 <+bridge> <cellegenrih> PR (also known as Pull Request) = requesting your change to be present on the original version (or any selected 'branch' clone) of the project. Moderation is key.
16:02 <+bridge> <cellegenrih> issue = well... your issues of course (like creating a post where you either complain about a feature, request a new feature, or highlight some code which may be wrong or needed discussion. Either way, it's just someone or multiple people yapping.)
16:02 <+bridge> <cellegenrih> github is a database, where projects can be stored and managed there.
16:02 <+bridge> <cellegenrih> slangs make it harder to understand what exactly is going on on github so here's a bit cheatcode:
16:02 <+bridge> <cellegenrih> 
16:02 <+bridge> <cellegenrih> repo = main project (that can be Teeworlds' source code as an example)
16:02 <+bridge> <cellegenrih> branch = different clones of the project (where selecting a clone can let you modify anything without affecting the original version, also called 'main' or 'master' most of the time)
16:02 <+bridge> <cellegenrih> pull = getting updates from projects (either by request or forcefully, almost no distinction between the two)
16:02 <+bridge> <cellegenrih> push = applying new changes to projects (when we use the term 'push', we think of 'force push' where we don't manage first hand how the change might affect the project)
16:03 <+bridge> <cellegenrih> commit = specific changes combined into one report (consider it as a list of changes on a paper)
16:03 <+bridge> <cellegenrih> PR (also known as Pull Request) = requesting your change to be present on the original version (or any selected 'branch' clone) of the project. Moderation is key.
16:03 <+bridge> <cellegenrih> issue = well... your issues of course (like creating a post where you either complain about a feature, request a new feature, or highlight some code which may be wrong or needed discussion. Either way, it's just someone or multiple people yapping.)
17:13 <+bridge> <teero777> jupsti left this server?
17:29 <+bridge> <melon> a while ago, he randomly checks in from time to time through IRC
17:41 <+bridge> <boxymaloxy> how did ddnet get made i wanna make a cool game too (except it's tiny) i have the compiler for C++ how do i get started (i dont wanna use godot, too strict on the structuring and i cant run unity)
17:42 <+bridge> <teero777> @magnus auvinen
17:43 <+bridge> <heinrich5991> if you want to write a game, it's probably best to start with a game engine
17:43 <+bridge> <heinrich5991> if you want to write a game, it's probably best to start with an existing game engine
17:43 <+bridge> <heinrich5991> if you want to write a game engine, you can start from scratch, it's also fun, but don't expect a game
17:43 <+bridge> <heinrich5991> note that magnus auvinen already had experience with writing game engines when he started teeworlds
17:44 <+bridge> <melon> ddnet is a mod for teeworlds, a game-engine that was turned into a game 0
17:44 <+bridge> <melon> ddnet is a mod for teeworlds, a game-engine that was turned into a game 20+
17:44 <+bridge> <melon> ddnet is a mod for teeworlds, a game-engine that was turned into a game 20+ years ago
17:44 <+bridge> <melon> ddnet is a mod for teeworlds, teeworlds started as a game-engine that was turned into a game 20+ years ago
17:44 <+bridge> <melon> replicating that with no knowledge in C++ is gonna proof itself rather difficult :D
17:45 <+bridge> <boxymaloxy> so ddnet already had the rendering backbone from teeworlds?
17:45 <+bridge> <melon> yes
17:46 <+bridge> <melon> yes, and it still uses quite a lot of code from back then
17:47 <+bridge> <melon> its written down somewhere. If you're interested i can dig it up later
17:47 <+bridge> <melon> but godot is a great way to get into game development, i wouldnt call it "too strict" either
17:48 <+bridge> <heinrich5991> https://wiki.ddnet.org/wiki/Timeline
17:48 <+bridge> <melon> thanks heinrich :)
17:52 <+bridge> <boxymaloxy> godot kinda evil gives me the vibes of the roblox studio workflow which i liked cause it gave me the tools and i didnt need to do much (but hated due to the mid scripting language)
17:52 <+bridge> <boxymaloxy> 
17:52 <+bridge> <boxymaloxy> so having to build everything in godot was cool and better but then i kinda hated the fact that im handed those same pre-made tools again which i doubt a lot due to the undercustomization 😅
17:54 <+bridge> <melon> godot is a playground, you can write a lot of stuff yourself without using nodes ^^ - i wouldnt focus on restrictiveness at the beginning
18:06 <+bridge> <louis> u can use C# in godot
18:06 <+bridge> <reitw> always be surprised that teeworlds was supposed to be a Ubisoft project
18:06 <+bridge> <reitw> I'll always be surprised that teeworlds was supposed to be a Ubisoft project
18:07 <+bridge> <reitw> well what was before teeworlds, teewars or some prototype
18:08 <+bridge> <reitw> I'll always be surprised that teeworlds was presented at Ubisoft as a project
19:40 <+bridge> <patiga> shootout iirc
19:41 <+bridge> <patiga> (yup)
21:57 <+bridge> <rainy_228> moderators
21:57 <+bridge> <rainy_228> i got funvoted
21:57 <+bridge> <rainy_228> where write ticket
21:58 <+bridge> <rainy_228> https://cdn.discordapp.com/attachments/293493549758939136/1523055346095231086/image.png?ex=6a4ab753&is=6a4965d3&hm=5398821f7d047fdaff63be9532154f6bc30c16094375b37b7dd0aa3a7ee4ce53&
21:58 <+bridge> <ryozuki> u can use rust
21:58 <+bridge> <rainy_228> where wrrite ticket?
21:58 <+bridge> <rainy_228> report
21:58 <+bridge> <ryozuki> i always feel like most unique ideas dont fit often generic engines
21:58 <+bridge> <reitw> #✉-create-a-ticket
21:58 <+bridge> <rainy_228> thx
21:58 <+bridge> <ryozuki> i doubt tw can play good in godot
21:59 <+bridge> <ryozuki> @reitw hey my bpf guy
21:59 <+bridge> <melon> ddnet is very nicely optimized (mostly thanks to some motivated devs like kebs and Assa) - and i doubt you could achieve that with a generic game-engine behind it all - i agree
22:00 <+bridge> <ryozuki> well kebs and assa are nice but
22:00 <+bridge> <ryozuki> i  meant more like matricks work itself
22:00 <+bridge> <ryozuki> the physics engine etc
22:00 <+bridge> <ryozuki> even unoptimized tw was already faster than what godot could do probs
22:00 <+bridge> <ryozuki> see also factorio
22:01 <+bridge> <ryozuki> i doubt u can recreate that in godot
22:01 <+bridge> <_k2d.> hi pls help me
22:01 <+bridge> <ryozuki> a generic engine is too limiting unless u do relativle generic 2d 3d platformer game
22:01 <+bridge> <melon> true, writing the engine before creating the game results in a much more performant result overall i guess
22:01 <+bridge> <ryozuki> also i think most devs can relate
22:01 <+bridge> <ryozuki> makign the engine is more fun than making the game
22:01 <+bridge> <ryozuki> i made lots of engines
22:01 <+bridge> <ryozuki> and
22:01 <+bridge> <ryozuki> stopped there
22:01 <+bridge> <ryozuki> xd
22:01 <+bridge> <melon> i never made an engine, maybe i should try that as a side-project
22:02 <+bridge> <ryozuki> i think its the most tech interesting part of the project
22:02 <+bridge> <ryozuki> the game itself is more creative and assets
22:02 <+bridge> <louis> then u have a boring game xd
22:02 <+bridge> <louis> unfortunately
22:02 <+bridge> <ryozuki> i guess
22:02 <+bridge> <ryozuki> i never been a rly creative person
22:02 <+bridge> <ryozuki> which is why i just made engines
22:02 <+bridge> <ryozuki> xd
22:03 <+bridge> <ryozuki> who doesnt like to learn opengl or vulkan
22:08 <+bridge> <reitw> wassap
22:11 <+bridge> <_k2d.> hi pls help me
22:11 <+bridge> <boxymaloxy> are those hard to learn how bad was the learning curve and what is the process for each
22:12 <+bridge> <boxymaloxy> are those hard to learn how bad was the learning curve and what is the process for rendering in each
22:12 <+bridge> <teero777> man the compile times of rust projects explode so hard
22:13 <+bridge> <teero777> workflow been running for 5 minutes compiling twgpu
22:24 <+bridge> <teero777> https://github.com/Teero888/tw-thumbs
22:24 <+bridge> <teero777> ok made this using llm real quick, it periodically checks the maps repos and generates thumbnails for ddnet, kog and unique in 1280x720 res. if you ever need thumbnails for something you can probably use this
22:32 <+bridge> <inv41idu53rn4m3> Well you can write the logic that would've normally been part of the engine and just ignore the built-ins, though for best performance you'll have to start dealing with native modules
23:50 <+bridge> <zavzagali> yo
23:50 <+bridge> <zavzagali> guess what did i do