| Time |
Nick |
Message |
| 00:31 |
|
Sokomine joined #luanti-dev |
| 00:53 |
|
Sokomine joined #luanti-dev |
| 02:29 |
|
aliasstilltaken joined #luanti-dev |
| 04:00 |
|
MTDiscord joined #luanti-dev |
| 04:49 |
|
YuGiOhJCJ joined #luanti-dev |
| 06:02 |
|
alias joined #luanti-dev |
| 06:15 |
|
alias joined #luanti-dev |
| 08:03 |
Krock |
will push https://pastebin.com/raw/xtfUayKW in 20 minutes to fix https://github.com/luanti-org/luanti/issues/16475 FYI sfan5 |
| 08:21 |
sfan5 |
sure |
| 08:22 |
|
Warr1024 joined #luanti-dev |
| 08:23 |
Krock |
done |
| 08:38 |
|
fluxionary_ joined #luanti-dev |
| 08:47 |
|
Warr1024 joined #luanti-dev |
| 09:06 |
|
Desour joined #luanti-dev |
| 10:41 |
[MatrxMT]_ |
<Zughy> Reminder meeting today |
| 10:51 |
sfan5 |
debian is apparently still shipping luanti 5.10.0 |
| 10:52 |
sfan5 |
also I'll delete the AAB file from here <https://github.com/luanti-org/luanti/releases/tag/5.13.0> if nobody has any complains, because it's useless for end users. |
| 12:43 |
|
Dragoni joined #luanti-dev |
| 14:53 |
|
wrrrzr joined #luanti-dev |
| 15:19 |
|
wrrrzr joined #luanti-dev |
| 15:44 |
|
Dragoni joined #luanti-dev |
| 16:25 |
sfan5 |
soo when's the meetin |
| 16:25 |
sfan5 |
g |
| 16:39 |
|
pmp-p joined #luanti-dev |
| 17:16 |
|
loggingbot_ joined #luanti-dev |
| 17:16 |
|
Topic for #luanti-dev is now Luanti (fka Minetest) core development and maintenance. Chit chat goes to #luanti. https://dev.luanti.org/ https://irc.luanti.org/ https://github.com/luanti-org |
| 17:27 |
|
cx384 joined #luanti-dev |
| 17:32 |
|
Desour joined #luanti-dev |
| 17:34 |
Desour |
at 18:00 UTC (= in 26 min) |
| 18:00 |
Krock |
Did I make it just in time? |
| 18:01 |
|
y5nw joined #luanti-dev |
| 18:01 |
Krock |
sfan5: which file do you mean? |
| 18:01 |
sfan5 |
deleted it already |
| 18:01 |
Krock |
alright |
| 18:02 |
Krock |
So if we're going by the meeting points: |
| 18:02 |
Krock |
> FF now and RC on September 21 (Zughy) |
| 18:03 |
Krock |
The milestone isn't even half done |
| 18:03 |
Krock |
And it's been only 5 weeks since the last release |
| 18:04 |
sfan5 |
what was out release schedule again |
| 18:04 |
Krock |
If 4 releases are wanted each year, then they should have a 13 week interval, where 11 weeks are the merge window |
| 18:04 |
sfan5 |
have the dates maybe been set like that to accomate the game jam? |
| 18:04 |
Krock |
yes |
| 18:05 |
sfan5 |
accomodate* |
| 18:05 |
Krock |
> https://docs.luanti.org/for-engine-devs/releasing-luanti/ |
| 18:05 |
sfan5 |
then I'd ask do we even have game-jam relevant features in this release yet? |
| 18:05 |
Krock |
> Goal: January, April, July, October |
| 18:06 |
Krock |
I do not remember any feature that would be a game-changing novelty. |
| 18:07 |
Desour |
*pinging* @Zughy luatic y5nw |
| 18:08 |
Krock |
anyway, there's another cleanup PR I have in mind, which I might start working on next week - it should free up min. 1k lines |
| 18:09 |
y5nw |
Wouldn't it make sense to move the feature freeze to (at least) the next meeting? IMO a release in mid-October (e.g. 19 Oct) should be fine and that would be 6 weeks away |
| 18:09 |
Krock |
y5nw: that would also be my preference. |
| 18:09 |
sfan5 |
sounds good |
| 18:10 |
Krock |
also, the RC should happen after entering feature freeze |
| 18:10 |
Krock |
like.. right afterwards, if not at the same time. |
| 18:12 |
Krock |
by the way - does the translator tool yet support the gettext format, or how are the strings collected there? |
| 18:13 |
Krock |
> https://github.com/luanti-org/modtools/issues/7 probably not yet supported. |
| 18:14 |
y5nw |
There's https://github.com/luanti-org/modtools/blob/main/luanti_xgettext.sh but it only creates the template file |
| 18:15 |
y5nw |
i.e. you would still need to perform the .tr -> .po conversion (should be doable with a script) and optionally update it with the template (msgmerge?) |
| 18:15 |
Krock |
then we're already half way there. mgsmerge can be used to update those |
| 18:15 |
Krock |
*msgmerge |
| 18:15 |
Krock |
> https://github.com/luanti-org/luanti/blob/master/util/updatepo.sh |
| 18:18 |
Krock |
Perhaps someone's got the time to implement that. Anyway. Since we're here - Are there any open questions about issues, PRs? Asking for directions, inputs? |
| 18:19 |
y5nw |
https://git.sr.ht/~gpcf/advtrains/tree/bed66e0f901ae9f8e21675035f174292120fea4f/item/advtrains/locale/topo.sh << I think I used this for converting from .tr to .po for Advtrains, but this does not handle certain edge cases |
| 18:20 |
Krock |
In a way I am impressed and for another reason somewhat scared. |
| 18:20 |
|
SFENCE joined #luanti-dev |
| 18:25 |
|
jstein joined #luanti-dev |
| 18:26 |
sfan5 |
what are the points we have to discuss today |
| 18:26 |
Krock |
sfan5: only the RC+FF of 5.15.0 and the usual one approval PRs |
| 18:26 |
Krock |
* 5.14.0 |
| 18:27 |
sfan5 |
first one is solved already |
| 18:27 |
sfan5 |
I guess we could go through the list |
| 18:28 |
Krock |
I'd like to re-review the shaders PR but unfortunately it might need adoption to rebase |
| 18:29 |
sfan5 |
yeah |
| 18:30 |
sfan5 |
#16479: no discussion needed probably |
| 18:30 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16479 -- Builtin profiler: Capture Tracy zones; And small improvements by Desour |
| 18:30 |
sfan5 |
same for #16472 |
| 18:30 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16472 -- [no squash] Make node break particles visible to all players by sfan5 |
| 18:30 |
sfan5 |
#16458 not sure, but I maintain my position on the serialization details |
| 18:30 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16458 -- Network: Batch individual particle packets by appgurueu |
| 18:31 |
sfan5 |
namely that we should serialize ParticleParameters with a length field to avoid the future need to lock-step client/server once any further fields are added |
| 18:32 |
Krock |
sfan5: I agree that the count should be included. u16 should be sufficient, I hope? |
| 18:32 |
sfan5 |
sure |
| 18:36 |
sfan5 |
next then: #16329 has been mentioned above |
| 18:36 |
Krock |
left a comment just to be sure |
| 18:36 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16329 -- OpenGL3 shadows shaders by PtiLuky |
| 18:36 |
sfan5 |
waiting for a rebase and changes |
| 18:36 |
sfan5 |
#16075: waiting for my review |
| 18:36 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16075 -- Support skybox transparency by MirceaKitsune |
| 18:37 |
sfan5 |
#16053: I guess this is not going anywhere at all, not worth discussing here now? |
| 18:37 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16053 -- Change default inventory key to E, default Aux1 key to F by minlemon |
| 18:37 |
Krock |
yes. mostly a dead end IMO |
| 18:38 |
sfan5 |
will mark as possible close |
| 18:38 |
|
Desour joined #luanti-dev |
| 18:38 |
sfan5 |
next: #15035 uhh |
| 18:38 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/15035 -- DOCS: clarify `stepheight` upper limit by Zughy |
| 18:38 |
sfan5 |
could technically be merged but I'd like a second look |
| 18:39 |
Krock |
according to the code, that should be what's happening, thus LGTM. |
| 18:40 |
Krock |
IMO this can be merged as-is. Feel free to double-check. |
| 18:40 |
[MatrxMT]_ |
<birdlover32767> speaking of the milestone i addressed the #16480 reviews |
| 18:40 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16480 -- Fix world buttons not appearing by birdlover32767 |
| 18:40 |
sfan5 |
next: #14916 |
| 18:40 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/14916 -- Add minetest.register_on_item_drop callback by zmv7 |
| 18:40 |
sfan5 |
not sure about that one |
| 18:41 |
Krock |
sfan5: our API should be KISS, thus I'd argue that it should be closed. |
| 18:42 |
sfan5 |
i'll close it then. no point keeping it open even longer. |
| 18:42 |
Krock |
if this were a filter function of some sorts, then it would make sense to have a callback for that |
| 18:42 |
Krock |
yet it sits at the beginning of the function, which can be extended in a trivial way |
| 18:43 |
sfan5 |
next: #14267 |
| 18:43 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/14267 -- Add per-node climb speed modifier (try 2) by Wuzzy2 |
| 18:44 |
sfan5 |
anticheat not working right sounds like a blocker to me |
| 18:44 |
sfan5 |
or is that purely and edge case? |
| 18:44 |
sfan5 |
an* |
| 18:46 |
Krock |
Anti-cheat should be implemented there to avoid false-positives. |
| 18:46 |
Krock |
I even proposed an implementation below |
| 18:46 |
Krock |
> Patch: 0001-Anticheat-respect-climb_factor.patch.zip |
| 18:47 |
sfan5 |
ok, commented. |
| 18:48 |
sfan5 |
I guess we could quickly go over milestone issues too |
| 18:48 |
|
YuGiOhJCJ joined #luanti-dev |
| 18:48 |
sfan5 |
#16362: someone needs to do this or we can't upload to google play |
| 18:48 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16362 -- Android: Update to SDK 35 by August 31 |
| 18:48 |
[MatrxMT]_ |
<Zughy> Frankly I wonder what's my role if every time we change our plans. What's the point of even try scheduling? The goal was to avoid creating issues with the game jam. I guess I'll let GreenXenith say something if he wants to (I meant FF today and RC after two weeks) |
| 18:49 |
sfan5 |
i haven't looked closely but I think there's no actual changes needed beyond increasing the api ver |
| 18:49 |
sfan5 |
@Zughy the problem is we're wondering why we're supposed to hurry something that doesn't have relevance for the game jam (or does it?) |
| 18:50 |
sfan5 |
did we write the exact reasoning down anywhere, by chance? |
| 18:50 |
sfan5 |
next #16197: could not be reproduced yet as it looks, we'll have to wait |
| 18:50 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16197 -- Player can glitch up the wall by walking towards it |
| 18:51 |
sfan5 |
next #16234: already tagged "help needed" |
| 18:51 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16234 -- Extreme lag when moving camera and running through Steam (on Steam Deck) |
| 18:51 |
sfan5 |
not much point keeping those two in the milestone is there? |
| 18:53 |
Krock |
not really no. Who knows what's happening on the Steam Deck |
| 18:53 |
Desour |
I was able to reproduce 16197, fyi. I just didn't think it was necessary to write it down |
| 18:53 |
Desour |
idk much about collision code though |
| 18:54 |
sfan5 |
next: #15992 I think this is also waiting for me |
| 18:54 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/15992 -- Make ABMs changeable by sfence |
| 18:54 |
sfan5 |
we should have this feature |
| 18:55 |
sfan5 |
next: #16384 no hurry but anyone could do this soon-ish |
| 18:55 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16384 -- Remove non-SDL Irrlicht devices |
| 18:56 |
sfan5 |
#16162 and #16468: needs input from us |
| 18:56 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16162 -- Roadmap brainstorm (5.14+) |
| 18:56 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16468 -- Update roadmap by Zughy |
| 18:56 |
Krock |
I don't see the potential of 15992, thus neglected it. |
| 18:56 |
sfan5 |
I think just being able to turn ABMs on or off would go a long way |
| 18:57 |
sfan5 |
but of course having them fully dynamic is best |
| 18:57 |
sfan5 |
finally #16469 has a fix pending |
| 18:57 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16469 -- World buttons may not appear after switching tabs |
| 18:57 |
Krock |
true - assuming that they can be turned off. |
| 18:57 |
Krock |
> chance = 0, |
| 19:00 |
Krock |
already found a few flaws in 15992 |
| 19:02 |
sfan5 |
I haven't reviewed it (again) but I am considering maybe doing my own implementation |
| 19:02 |
[MatrxMT]_ |
<Zughy> sfan5: I don't remember, I can't check the log right now. Either way, by choosing to postpone it after the jam we're saying that future releases (in future years) will happen after the jam. I don't know, I think having game creators experimenting with a new version is better (more in-depth testing) |
| 19:03 |
sfan5 |
Krock: mind approving #16267? |
| 19:03 |
ShadowBot |
https://github.com/luanti-org/luanti/issues/16267 -- Allow scaling nametag by distance and to set font size by sfan5 |
| 19:03 |
Krock |
will do |
| 19:03 |
sfan5 |
@Zughy I see. That specifically could be fixed at any pointer by just moving the schedule a bit. Doesn't have to be now. Or in fact the game jam itself could also be moved. |
| 19:04 |
sfan5 |
regarding "having game creators experimenting": I agree, but as of now it doesn't look like 5.14.0 has any exciting features |
| 19:04 |
sfan5 |
(especially not if we were to freeze now) |
| 19:06 |
[MatrxMT]_ |
<Zughy> Mmm, I think that the less effort the better. Changing this aspect in the future means more annoyance incoming. (Afk, I'll check everything later) |
| 19:09 |
sfan5 |
i mean you just have to move the schedule forward by 2 weeks, at any point in the next 12 months |
| 19:14 |
|
SFENCE joined #luanti-dev |
| 19:18 |
|
imi joined #luanti-dev |
| 19:28 |
|
Desour joined #luanti-dev |
| 20:31 |
|
SFENCE joined #luanti-dev |
| 21:40 |
MTDiscord |
<greenxenith> sfan5: This has already been discussed at length. Having a release schedule itself has nothing to do with the jam. The only reason I wanted it moved for the jam is because releasing mid-jam is annoying for everyone. December is a terrible month for the jam being too many holidays and pushes the results into the next year. October is the Ludum Dare jam which many people participate in, so I have no interest in colliding with that. |
| 21:40 |
MTDiscord |
January would force us to miss a year, which I also refuse to do. |
| 21:40 |
MTDiscord |
<greenxenith> And September is the start of the school year for many countries |
| 21:41 |
MTDiscord |
<greenxenith> Moving the Jam to a (northern) summer month would technically allow a lot more time for participation, but then I still have to either do a shorter gap or skip a year. |
| 21:42 |
MTDiscord |
<greenxenith> You guys were already following a release schedule, it was a lot easier to shift that by one month. And that already happened last release, so the spacing for this release has nothing to do with the jam anyway. If there is nothing ready that is not the fault of the schedule shift. |
| 21:42 |
MTDiscord |
<greenxenith> I dont care if there are new/useful features, I just dont want a new version mid-jam |
| 21:43 |
MTDiscord |
<greenxenith> Frankly, 3 months might have been too small of a dev period when taking feature freezes into account |
| 22:16 |
sfan5 |
I see. |
| 22:20 |
sfan5 |
was this discussed in some meeting? |
| 22:21 |
MTDiscord |
<greenxenith> https://irc.luanti.org/luanti-dev/2025-04-06#i_6253997 https://github.com/luanti-org/docs.luanti.org/issues/225 |
| 22:23 |
MTDiscord |
<greenxenith> (In reference to the shift; the schedule itself has existed for almost a year now, and there are far more conversations surrounding that) |
| 22:30 |
sfan5 |
I think the main problem is the new expectation that we release on time and can't allow delays? |
| 22:30 |
sfan5 |
or did I misunderstand? |
| 22:31 |
MTDiscord |
<greenxenith> That expectation is not new |
| 22:31 |
MTDiscord |
<greenxenith> The expectation as of about a year ago is "release what you have and move on" |
| 22:34 |
|
panwolfram joined #luanti-dev |
| 22:58 |
[MatrxMT]_ |
<Zughy> which basically never happened, to be clear |
| 23:00 |
[MatrxMT]_ |
<Zughy> which frustrates me, because my job here is to keep things going as smooth as possible but we always postpone |
| 23:05 |
|
Eragon joined #luanti-dev |
| 23:05 |
[MatrxMT]_ |
<Zughy> it is true that we had summer holidays in the middle of this upcoming release, but seriously, there's always something not working. This time I had thought about playing it safe by scheduling FF with a lot of margin (3 weeks, with 1 of RC, since we definitely struggle both with time and with releasing RCs), but if in the end it takes core devs going "naah" during a meeting, then I can't help you |
| 23:07 |
[MatrxMT]_ |
<Zughy> *it only takes |
