Time Nick Message 00:21 MTDiscord but where is 32bit map support? 04:36 MTDiscord im afraid none of the core devs care about that 04:36 MTDiscord kinda sadly as it would be cool, though probably with little uses 15:43 sfan5 should we update the website already? android can come later 15:44 [MatrxMT] I'm merging #16468 myself later if nobody says anything. I find this radio silence highly disrespectful and I'm officially pissed of being ignored when I'm investing a lot of my time in all of this 15:44 ShadowBot https://github.com/luanti-org/luanti/issues/16468 -- Update roadmap by Zughy 15:50 sfan5 so you're ignoring Desour's review comment? 16:11 jonadab The one about dehardcoding, that got warnocked two weeks ago? 16:15 [MatrxMT] sfan5: nobody said anything about that comment, there is no reaction. How am I supposed to know if devs want that extended version or not? 16:16 [MatrxMT] There was a "meeting" yesterday and some of you, instead of bringing that up, decided to ignore it and just proceed with the release. How is this my fault now? 16:25 sfan5 finding out whose fault this is is not important 16:25 sfan5 to the topic: in every other PR the submitter just does whatever a single coredevs says (unless discussion happens). I expected that here too 16:25 sfan5 or if not then it should be stated explicitly that you're waiting for some kind of consensus 16:41 jonadab @Zughy Nobody _including you_ responded to what Desour said. He and others may have assumed this meant you had no objection to what he said. 16:47 Krock FWIW I support Desour's suggestions. 16:48 Krock and like any other (regular) PR, this one too needs two approvals (or one + you), assuming there are no objections from other core devs 16:54 [MatrxMT] Me yesterday: https://irc.luanti.org/luanti-dev/2025-10-05#i_6288805 16:54 [MatrxMT] and we're missing the point here: everyone assumed it was safe to release without bothering that a PR/issue was still left there 16:55 [MatrxMT] anyone could have tagged me asking for clarifiactions, if my IRC message was ambiguous 16:55 [MatrxMT] *clarifications 16:56 Krock please mark PRs as Blocker or High Priority if they have to be in a release. Furthermore, I don't think this has to be release-bound since the development happens on GitHub, and thus, local copies of such workflows or project decisions are best viewed online - which is the master branch. 16:57 [MatrxMT] :\ it was inside the 5.14 milestone and the whole point of that was to make it happen right after 5.14, how was that not clear enough? 16:58 sfan5 after? 16:59 Krock there is afaik no process defined for "right after" 16:59 [MatrxMT] like, put inside 5.14 and then become effective right after the launch 16:59 Krock the whole Luanti development is like "it's ready when it's ready". 17:04 Krock are there any animated tools or items, by the way? 17:07 sfan5 that's not actually supported, I think 17:07 sfan5 except for nodes, then: flowing water? 17:08 Krock hmm. I thought I had seen a glowing pickaxe once.. might be misremembering. 17:08 Krock ah #15979 17:08 ShadowBot https://github.com/luanti-org/luanti/issues/15979 -- Add `inventory_image_animation` and `wield_image_animation` by cx384 18:23 SFENCE Is it expected behaviors, that if I set in on_timer time to lesser value than server step, it calls on_timer function multiple times in one server step? 18:23 SFENCE Luanti 5.13 18:27 sfan5 probably not 18:29 SFENCE So, possible bug. I will try if it work same in 5.14. 18:36 Krock that should not happen at all 18:53 SFENCE Ok, looks like false alarm. Error was in mod code. 20:25 [MatrxMT] Krock: the whole point of me, the roadmap, the schedule and the aspiring Comms team is to avoid "it's ready when it's ready" and if I remember correctly a similar discussion already happened in the past with you and GreenXenith (can't bother to look for it) 20:27 [MatrxMT] Anyway, still missing the point here: yesterday I remembered in -dev about that PR missing. My message was ignored, the PR wasn't touched (as in, also kept in the milestone), LT 5.14 released and the milestone closed 20:28 [MatrxMT] Around 11 PM I posted another message, but again, nothing. Now, instead of a "my bad", I hear people clutching at straws. Like, for fuck sake, I don't accept that 20:29 [MatrxMT] I respect what you do, have some respect for what I do as well 20:33 sfan5 what I don't understand is why it's a big deal for the PR to not be in 5.14 20:34 [MatrxMT] from the original issue: https://imgur.com/a/ZdvVEW4 20:36 sfan5 then aren't we a whole release cycle overdue? or do you mean "after 5.14"? 20:36 [MatrxMT] more straightfowardly: if we (silently) agree on something, I expect that something to be respected. Now the risk is seeing that PR merged in a week or so, and what am I supposed to as a triager? Use the old or the new roadmap as a reference? It only creates confusion 20:37 sfan5 but putting that aside because it's not relevant: so what? this isn't a critical bug, or anything that impacts the finished product at all 20:38 sfan5 handling of issues during a roadmap "transition" is something I trust you can handle reasonably with your intuition 20:38 sfan5 s/something/a mere edge case that/ 20:39 sfan5 we should not delay updating the roadmap any further of course 20:40 sfan5 I could understand if you were upset that we mostly ignored the PR for the whole September, but I don't understand how the 24 hours after 5.14 are somehow much worse 20:40 [MatrxMT] Because I expected that to be discussed in a meeting or something, within 5.14 20:41 sfan5 I think this is also why nobody in -dev reacted, because we were busy with more important things (the release) 20:42 [MatrxMT] actually, right before releasing, as it should have become effective from 5.15-dev onwards 22:40 MTDiscord Zughy: #16208 is a bug. I will test again tonight but I believe it is still an issue 22:40 ShadowBot https://github.com/luanti-org/luanti/issues/16208 -- Negative glow does not work as advertised 22:40 MTDiscord (Acc sfan5 I guess) 22:40 MTDiscord -A