Luanti logo

IRC log for #luanti-dev, 2026-08-16

| Channels | #luanti-dev index | Today | | Google Search | Plaintext

All times shown according to UTC.

Time Nick Message
04:00 MTDiscord joined #luanti-dev
08:13 Krock will merge #17435 #17443 #17444 #17447 in 15 minutes
08:13 ShadowBot https://github.com/luanti-org/luanti/issues/17435 -- Clarify behavior of `InvRef:remove_item()` by OgelGames
08:13 ShadowBot https://github.com/luanti-org/luanti/issues/17443 -- ContentDB: Validate package author and name characters by rubenwardy
08:13 ShadowBot https://github.com/luanti-org/luanti/issues/17444 -- Explain the 'item' field of the inventory HUD in more detail by DMBuce
08:13 ShadowBot https://github.com/luanti-org/luanti/issues/17447 -- DevTest: Remove invalid visual_scale test nodes by Wuzzy2
08:22 Warr1024 joined #luanti-dev
08:31 Krock "Checking for the ability to merge automatically..."  GitHub, are you OK?
08:47 Warr1024 joined #luanti-dev
12:07 dv^_^6 joined #luanti-dev
12:24 egb joined #luanti-dev
15:29 Panquesito7 joined #luanti-dev
16:52 pgimeno joined #luanti-dev
16:55 book` joined #luanti-dev
17:39 rubenwardy for a main menu redesign, how would we feel about shipping flow officially in the engine? It matches what the GUI framework might be in the future https://content.luanti.org/packages/luk3yx/flow/
17:41 egb joined #luanti-dev
17:44 MTDiscord <wsor4035> scoped only to the main menu so it can be removed/replaced/changed later?
17:54 rubenwardy most likely
17:55 Krock I have yet not worked with that mod. However, if that dependency makes up 50% of the new main menu code, then I'd be slightly opposed. Aside from that - we could give it a try.
17:56 Krock however, the engine is also the place where new formspec elements are born, thus this is guaranteed to result in multiple versions of formspec_ast and flow.
17:58 Krock furthermore, I suspect it becomes more difficult to debug engine bugs when there's another layer of translation in between
17:59 rubenwardy I guess my idea is to make the mainmenu easier to write and also reduced required changes when the new GUI framework comes around
17:59 rubenwardy I don't want to use fst_api
18:04 rubenwardy Ideally we would have had a new GUI API in the last 4 years
18:05 crazylad joined #luanti-dev
18:05 Krock formspec follows the KISS-principle from the engine's perspective, on the cost of modder's sanity to handle states and edge-cases
18:06 MTDiscord <wsor4035> formspec has no principle other than the most basic wrapper over irrlichts gui i thought?
18:06 rubenwardy A DOM-like Lua DSL try wouldn't be that much more complicated for us
18:07 rubenwardy proper layouts, sure
18:07 sfan5 we can just bundle chromium
18:07 Krock that would help the JavaScript API request too
18:08 MTDiscord <ggepic64> Goodbye Luanti's "low RAM usage"
18:08 [MatrxMT]_ <birdlover32767> "forgot to disable telemetry"
18:08 Krock Chromium surely has more lines of code than all our direct dependencies
18:10 MTDiscord <ggepic64> Chromuim is a professional RAM eater
18:11 MTDiscord <ggepic64> Also i heard you really don't want to give up the spec technology
18:11 MTDiscord <ggepic64> You invented it from scratch, out of nowhere, thinking it would be convenient for such a game engine...
18:12 MTDiscord <wsor4035> if you want html/xml like. rmlui. as mentioned in chatrooms and the gui replacement pr. however getting away from rubens original point/request
18:12 MTDiscord <ggepic64> And trying to reinvent this technology will cause compatibility issues ig
18:13 MTDiscord <ggepic64> If new spec features get released, how to ensure they work in older clients for example
18:16 egb joined #luanti-dev
18:17 rubenwardy easy, forced updates
18:18 MTDiscord <ggepic64> At least everyone would have to play with the same possible bugs and glitches :trollface:
19:32 crazylad_ joined #luanti-dev
20:46 egb joined #luanti-dev
21:07 Panquesito7_ joined #luanti-dev
21:27 crazylad joined #luanti-dev
22:32 panwolfram joined #luanti-dev

| Channels | #luanti-dev index | Today | | Google Search | Plaintext