Luanti logo

IRC log for #luanti, 2026-08-08

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

All times shown according to UTC.

Time Nick Message
00:05 mrkubax10 joined #luanti
00:53 xor_ghost87 joined #luanti
01:08 [MatrxMT] <Blockhead256> Figured out why the last two pages of https://forum.luanti.org/viewtopic.php?t=29923 don't load when I'm logged in. Stop forum spam plugin chokes on a user's email address that has a / in the local-part (before the @).
01:09 [MatrxMT] <Blockhead256> kind of annoying, also it creates a race condition where I check the thread in another container tab then go to front page to mark all forums read
01:54 LuantistDork joined #luanti
04:00 MTDiscord joined #luanti
04:00 est31 joined #luanti
05:50 GNUHacker joined #luanti
06:26 Juri joined #luanti
06:26 Niklp joined #luanti
06:30 FeXoR joined #luanti
07:28 MTDiscord joined #luanti
07:30 dudz joined #luanti
07:36 pgimeno joined #luanti
08:09 ___nick___ joined #luanti
08:12 mrkubax10 joined #luanti
08:47 [MatrxMT] joined #luanti
08:49 sfan5 you could try pinging c55 to patch the bug
08:50 [MatrxMT] <Blockhead256> celeron55 add it to the backlog along  https://forum.luanti.org/viewtopic.php?p=452107#p452107with reporting and password resets tyvm
08:51 [MatrxMT] <Blockhead256> oops here's the clickable URL https://forum.luanti.org/viewtopic.php?p=452107
08:53 sfan5 next suggestion: have a patch ready to fix it
08:54 SwissalpS joined #luanti
08:56 [MatrxMT] <Blockhead256> :\
08:56 sfan5 quickest fix is probably to skip the banhammer code in the affected template if an / is present
09:10 mrkubax10 joined #luanti
09:20 est31 joined #luanti
09:35 celeron55 maybe i'll spin up claude to patch it
09:59 celeron55 eh, this is not working
11:49 sys4 joined #luanti
12:21 PoochInquisitor joined #luanti
12:45 turtleman joined #luanti
12:53 trbt joined #luanti
13:09 ___nick___ joined #luanti
13:10 MinetestBot [git] sfan5 -> luanti-org/minetestmapper: Add bounds checks to block decoding code 0d40f9d https://github.com/luanti-org/minetestmapper/commit/0d40f9d47ba8a733f269d182d1ac1310ceb9fd62 (2026-08-08T13:07:37Z)
13:11 PoochInquisitor joined #luanti
13:17 ___nick___ joined #luanti
13:19 FeXoR joined #luanti
13:25 farribeiro|irccl joined #luanti
13:26 trbt joined #luanti
13:27 farribeiro|irccl Good morning, I wanted to ask about Luajit, which received some new features in the last commit. https://github.com/LuaJIT/LuaJIT/issues/1475
13:28 MTDiscord <wsor4035> To ask what?
13:28 MTDiscord <wsor4035> Don't ask to ask, just ask
13:28 farribeiro|irccl The code will incorporate these new features in the future.
13:29 MTDiscord <wsor4035> Ok?
13:30 farribeiro|irccl The latest commit already supports these things.
13:31 MTDiscord <wsor4035> Not seeing a question?
13:32 MTDiscord <luatic> yes luanti will "inherit" these features on every configuration where a recent luajit version is available
13:32 MTDiscord <wsor4035> If your asking if luanti will have these, then yes. Dependant on how its compiled, where its sourced from, etc. It's no different than goto currently, or gc64 being on or off
13:36 farribeiro|irccl Understood. I hope this will be advantageous for the project.
13:37 farribeiro|irccl It will enable the use of bitwise and other features.
13:38 MTDiscord <luatic> honestly i'm not super stoked about the new features. some will be nice but out of the door it will probably be mostly a compatibility mess and modders would be better advised to stay clear of the features.
13:39 MTDiscord <luatic> bitwise is already covered by bit.* and if i remember correctly, the runtime cost of that should be close to operators, so i'm not a big fan of that either.
13:39 farribeiro|irccl It will no longer be necessary to use the bit.*
13:39 MTDiscord <luatic> yes, i know. i'm saying that doesn't really add anything.
13:40 [MatrxMT] <Blockhead256> it would still be needed for PUC Lua and I haven't heard any plans to drop PUC Lua
13:40 [MatrxMT] <Blockhead256> Depending on LuaJIT is a great way to make you mod not portable
13:41 MTDiscord <wsor4035> Yes, but molders already use goto, math.random with 2? Args, etc
13:41 MTDiscord <wsor4035> It rarely actually matters
13:41 MTDiscord <luatic> i think realistically some games must depend on luajit simply because puc lua does not achieve acceptable performance
13:41 erbium joined #luanti
13:41 MTDiscord <luatic> math.random(a, b) is standard but some edge cases around it aren't
13:41 [MatrxMT] <Blockhead256> math.random with 3
13:41 MTDiscord <wsor4035> For pure puc to luajit, however the new features will cause more issues due to slow ass distros
13:42 MTDiscord <luatic> yeah it will be a compatibility nightmare in the transition period
13:42 [MatrxMT] <Blockhead256> and then every one of those LuaJIT-only mods will eventually get user reports of the mod not working without it, often with the author not realising it would be an issue
13:42 MTDiscord <luatic> also for tooling around lua. how slow will luacheck be to upgrade? VSC extensions? things like lua-lsp? selene? stylua? idk
13:42 MTDiscord <wsor4035> Personally I care more about brain dead distros that disable gc64
13:43 [MatrxMT] <Blockhead256> maybe it could be more of a certain thing for Luanti 6.0
13:44 MTDiscord <wsor4035> Luanti only cares about compiling luajit for non Linux platforms. On Linux it uses the system library by default so it would still get in
13:44 MTDiscord <wsor4035> Linux, non flat pack I guess
13:44 MTDiscord <luatic> honestly we should consider vendoring luajit
13:45 MTDiscord <wsor4035> Or submoduling it.....
13:46 [MatrxMT] <Blockhead256> dropping PUC Lua seems like it's dubious before a compatibility break. A lot of downstream would expect PUC Lua compatibility
13:46 MTDiscord <luatic> well yeah the specifics of how we vendor it are not that important to me, what'd be important is that luanti builds consistently use the same luajit version
13:46 MTDiscord <wsor4035> Actual submodules, not the submodules at home shit we had with iirlichtmt
13:47 MTDiscord <wsor4035> The puck lua is already vendored and a soft fork
13:47 MTDiscord <wsor4035> *puc
13:48 MTDiscord <wsor4035> But yeah, previous discussion of dropping puc lua was negative. Mainly due to the bus factor of one, and some other reasons I forget
13:48 [MatrxMT] <Blockhead256> main advantages to keeping PUC around are more cpu architectures and backwards compatibiltiy
13:49 [MatrxMT] <Blockhead256> too much asm in LuaJIT
13:51 [MatrxMT] <Blockhead256> so back to the original question: a server with a developer could use the latest version of LuaJIT and take advantage
13:51 [MatrxMT] <Blockhead256> but mod authors probably want to keep much wider/further backwards compatibility than relying on very recent features
13:52 MTDiscord <wsor4035> Once the new luajit has been out for at least two luanti versions would be a good minimum
13:52 erbium joined #luanti
13:53 MTDiscord <wsor4035> For those who dont want to be pure seedling edge/dev
13:55 MTDiscord <wsor4035> Wonder if someone will make the equivalent of whatever it is in html/js/css land for compiling in polyfills for a certain target
13:55 MinetestBot [git] sfan5 -> luanti-org/minetestmapper: More cleanups and minor improvements ec99246 https://github.com/luanti-org/minetestmapper/commit/ec99246ef3009d42421dc5e2e1e1c250dade144d (2026-08-08T13:51:45Z)
13:56 [MatrxMT] <Blockhead256> Lua Babel with transpilation to remove gotos and turn bitwise operators into bit.* calls, ..., (not sure how it could do const)
13:58 MTDiscord <luatic> const is trivial, just produce a compile error if it is violated. it's a pure load time check.
13:59 MTDiscord <luatic> related: https://hisham.hm/2026/08/04/the-lua-community-needs-to-learn-to-move-on/
13:59 MTDiscord <luatic> (teal guy, teal has babelesque qualities)
14:03 [MatrxMT] <Blockhead256> right, we're talking about local scope const and not something a bit harder like class consts in Java
14:04 MTDiscord <luatic> yep
14:04 MTDiscord <luatic> which is also why i'm genuinely not a big fan of it as i've written on the lua mailing list but eh
14:16 MinetestBot [git] sfan5 -> luanti-org/minetestmapper: Add test for malformed block c434fe9 https://github.com/luanti-org/minetestmapper/commit/c434fe92c75a84958f62cce3d1f9e83b51737ddf (2026-08-08T14:14:05Z)
14:24 [ I prefer the openresty fork of luajit because it has ppc64le support which the upstream luajit maintainer inexplicably refuses to merge
14:25 MTDiscord <luatic> ppc64le is extremely fringe, is it not?
14:26 [ it's one of the few performant options that can run with fully free firmware, plus I have one (and plan to use it as my main desktop when I get it working)
14:29 MTDiscord <wsor4035> fringe person wants fringe thing
14:32 [ software freedom is important
14:35 [ (apart from the practical issue of ppc64le support, stuff like the luajit maintainer removing old tags and refusing to merge ppc64le and loongarch support with no public explanation whatsoever makes me distrust the luajit maintainer)
14:47 MinetestBot [git] sfan5 -> luanti-org/minetestmapper: Fix build-mingw.sh 88c7381 https://github.com/luanti-org/minetestmapper/commit/88c7381a20ada1992169522d590ebad36195507e (2026-08-08T14:45:16Z)
14:52 sfan5 @wsor4035 even ignoring puc lua, relying on new luajit features can still get your in a compatibility mess with the aforementioned openresty fork, which debian uses (IIRC). no idea if they're going to pull those changes or how fast it will happen.
14:54 MTDiscord <wsor4035> ok?
14:54 MTDiscord <wsor4035> already knew that
14:54 sfan5 just saying
14:54 MTDiscord <wsor4035> as luatic said, if luanti did vendor in one way or another luajit, would make things less of a mess
14:55 MTDiscord <wsor4035> personally care about gc64 the most, since its annoying to have to deal with that issue on repeat
14:56 sfan5 there are people with disabled gc64 in the current year?
14:56 MTDiscord <wsor4035> iirc ubuntu didnt have it enabled last one i remember
14:56 MTDiscord <wsor4035> citation needed
14:57 MTDiscord <wsor4035> would be happy to be wrong
15:03 chilledfrogs joined #luanti
15:07 farribeiro|irccl One thing I remembered, the Luanti compilation using Puc Lua doesn't work well.
15:07 farribeiro|irccl Iirc
15:11 MTDiscord <wsor4035> "doesn't work well" isnt really descriptive
15:11 MTDiscord <wsor4035> whats the actual problem?
15:14 MTDiscord <jordan4ibanez> If anyone is reading this and is confused as to the response. ppc64le is only used on IBM Power super computer servers
15:23 MTDiscord <wsor4035> so did some research. testing on 24.04 looks like gc64 is on. it seems like this was first enabled in 22.04 or 24.04
15:36 TheWild joined #luanti
16:19 farribeiro|irccl Wsor Several things happen, I don't know exactly what, but it's often related to Luanti's screens.
16:39 farribeiro|irccl Forget it. Using luajit luanti works
16:46 ___nick___ joined #luanti
17:01 mrkubax10 joined #luanti
17:43 koaldsj333kkbbba joined #luanti
17:48 crazylad joined #luanti
18:39 Noisytoot <MTDiscord> <jordan4ibanez> If anyone is reading this and is confused as to the response. ppc64le is only used on IBM Power super computer servers
18:39 Noisytoot Mostly but not quite. It's also used in some RaptorCS workstations (but IBM is still the only manufacturer of the CPUs for now, hopefully that will change (there's also some embedded ppc64 CPUs made by NXP but I'm not sure those support little-endian mode, and Microwatt that runs on an FPGA)
18:40 Noisytoot )
18:50 sys4 joined #luanti
19:03 sys4 joined #luanti
19:21 MTDiscord <jordan4ibanez> So you're telling me that you're running a luanti server on a raptorcs workstation or a ibm power server?
19:21 MTDiscord <jordan4ibanez> Can I have one?
19:23 mrkubax10 joined #luanti
19:36 crazylad joined #luanti
19:54 Desour joined #luanti
20:13 pgimeno_ joined #luanti
20:58 ___nick___ joined #luanti
22:25 syl joined #luanti
22:32 panwolfram joined #luanti
22:52 mrkubax10 joined #luanti
23:00 YuGiOhJCJ joined #luanti
23:10 YuGiOhJCJ joined #luanti
23:23 YuGiOhJCJ joined #luanti
23:51 technomancy joined #luanti

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