Time  Nick             Message
00:03 MTDiscord        <luatic> farribeiro: can you get a backtrace? i can grep for clamps in the last couple commits and i have some callsites i suspect but it would be helpful to know which one it really is.
00:07 MTDiscord        <luatic> ok i have a likely culprit
00:08 Sheriff_U3       amazing how engine development has moved over here...
00:29 MTDiscord        Command sent from Discord by luatic:
00:29 MTDiscord        !tell farribeiro|irccl please try #17306
00:29 MinetestBot      MTDiscord: I'll pass that on when farribeiro|irccl is around
00:29 ShadowBot        https://github.com/luanti-org/luanti/issues/17306 -- Fix remaining issues with multi-track animations by appgurueu
01:25 farribeiro|irccl commented at #17306
01:25 MinetestBot      farribeiro|irccl: Jun-30 00:29 UTC <MTDiscord> please try #17306
01:25 ShadowBot        https://github.com/luanti-org/luanti/issues/17306 -- Fix remaining issues with multi-track animations by appgurueu
01:25 farribeiro|irccl LGTM
13:43 MinetestBot      02[git] 04cx384 -> 03luanti-org/luanti: Formspec: Fix model element flickering 1387eed0b https://github.com/luanti-org/luanti/commit/87eed0b860272eca592a54cc1a4227f1b46640b7 (152026-06-30T13:42:06Z)
13:43 MinetestBot      02[git] 04cx384 -> 03luanti-org/luanti: HUD: Use smart pointers to store elements 136744c6c https://github.com/luanti-org/luanti/commit/6744c6c03036bc1572f1504d7fe57398ab75c50c (152026-06-30T13:42:29Z)
13:43 MinetestBot      02[git] 04cx384 -> 03luanti-org/luanti: HUD: Divorce SSM and CSM 1399a609d https://github.com/luanti-org/luanti/commit/99a609d9d6da8c52ee83120bf7da03312d4b7a21 (152026-06-30T13:42:29Z)
16:47 Bombo            is 'load_mod_foo = mods/foo' in world.mt still valid? or just '= true' which is better? i noticed i get an error when i got a different dir than ~/.minetest, i use ~/luanti/ with LUANTI_MOD_PATH="/home/luanti/luanti", it complains (ERROR) that it can't find mods/foo, but found it nevertheless in ~/luanti/mods/foo
16:50 Krock            Bombo: = true selects whatever mod is found first. The other notation is a clear identifier. If you replace LUANTI_MOD_PATH with MINETEST_MOD_PATH, does it show a warning?
16:51 Krock            if not, then your Luanti version is either too old or the env var is not applied.
16:52 Krock            chaotic good feature check: `grep LUANTI_MOD_PATH /path/to/luanti`
16:56 Krock            works for me: LUANTI_MOD_PATH=/XXXX/mods/ ./luanti --server --worldname devtest
17:10 Bombo            Krock: with MINETEST_* i get deprecation warning AND error about the mod not found so i switched to LUANTI_* (5.16.1)
17:10 Bombo            but do you have 'load_mod_foo = mods/foo' in world.mt?
17:11 Krock            load_mod_unified_inventory = mods/unified_inventory
17:11 Krock            oh. it did actually find the mod in my ordinary mods/ directory
17:12 Krock            this variable does not work
17:12 Krock            > load_mod_unified_inventory = /XXXXXXXXX/mods/unified_inventory <  this does the trick. On startup, Luanti shows the error " However, it is available in the following locations: ...."
17:20 Bombo            yes = true works too, without complains
18:39 Sheriff_U3       I kinda wish that there was a list of introduction dates for each of the api's... Attempting to create a program that can parse through a mod and determine what versions of Luanti/Minetest it is compatible with.
19:18 Bombo            how much does a client need to load before joining a server? is it 'du -sch games/minetest_game/ mods/ worlds/' ?
19:26 sfan5            the media. that is textures, audio, models
19:27 sfan5            but it doesn't need to download them every time, because they end up cached
19:27 Sheriff_U3       so that's why it always takes longer to join the first time...
19:45 Bombo            so *.png *.ogg *.b3d *.obj
19:45 Bombo            but second time it takes time too
19:46 Bombo            how many MB does it load i wonder ;)
19:46 Bombo            or how many MB the client from the cache loads
19:57 Krock            Bombo: https://github.com/luanti-org/luanti/blob/master/src/server.cpp#L2669-L2679
19:58 Krock            so you better remove or rename unused media files because Luanti does not know which one are (or will be used)
20:13 Bombo            ok so all od the supported_ext wil be loaded
20:14 MTDiscord        <luatic> not necessarily loaded, but transfered and stored, yes
20:14 MTDiscord        <luatic> many things are loaded on demand
20:15 Bombo            hm iirc log says some ogg files are ignored bevause of unsupported characters, artisat - title.ogg for the jukebox ;)
20:16 Bombo            tramsfered from server to client and stored but nut loaded in the clients ram?
20:29 Bombo            did anyone yet make a script to scan a mod and display all textures, like an inventory, but in html? so one could put it on a webserver, to see what exact items this mod contains ;)
20:29 Bombo            prob needs to parse some lua?
22:12 bgstack15        Sheriff_U3: I don't know how you feel about AI, but summarizing large datasets like that sounds suited for a computer to me. Parse probably git tags of Luanti/minetest, and then build a lookup table of app version and new/removed API calls.
22:14 MTDiscord        <luatic> my suggestion to most modders would be: pick a reasonable target version, then check out the doc/lua_api.md of the luanti version you target via git.
22:15 MTDiscord        <luatic> it is possible to do a lot of funky stuff like targeting a new server and an old client but honestly it's mostly nonsense deep down
22:16 Sheriff_U3       bgstack15: I'm using it for that, I got it to create a update script that can then be run to update a .json file with the needed data
22:16 MTDiscord        <luatic> the way it should be is definitely with clients being only a few versions behind most of the time as is fairly standard for games. unfortunately it isn't for luanti for a variety of reasons. a while ago the update checker was added to at least make users aware of the problem.
22:18 bgstack15        luatic: yeah, if you could expect a single doc would have valid info for each point release, that would make that easier. Maybe not even AI would be needed; just a fancy shell script.
22:19 Sheriff_U3       luatic: I'm wanting a program that can find the min version that a mod requires, it would help me in modernizing a lot of the old mods. But in order to create such a program I needed a list of api's and methods with their introduction and depreciation version numbers.
22:20 MTDiscord        <luatic> ah, i see. well, honestly something like what bgstack15 suggested might very well be the way to go. i would even go as far as to suggest an LLM do a (heuristic) static analysis of the code based on that information.
22:21 MTDiscord        <luatic> (tools like luacheck can do relatively reliable static analysis for simple scenarios like global namespaces, but they get tripped up by a variety of slightly more tricky ones.)
22:22 bgstack15        Sheriff_U3: that tool to produce such a report for a mod sounds really neat. If you end up with a script that analyzes minetest code/docs, or at least a json table, would you please publish that for others! And the tool for analyzing a mod too, if possible.
22:23 bgstack15        "Find your earliest compatible Minetest client here! Step right up! Find out how Grandma's Minetest can run your mod, no need to be shy"
22:23 Sheriff_U3       What I'm doing currently is having an AI create a python script that parses through every tagged version of lua_api.txt/lua_api.md for new api's and ones that are marked as deprecated/removed. I'm running it against a bunch of mods that I have locally from mt-mods and minetest-mods
22:23 bgstack15        mod-client-minmaximizer
22:24 bgstack15        (or would you need mod-server-minmaximizer)
22:24 bgstack15        since mods run on a server
22:24 Sheriff_U3       Then that's used in a standalone application in go to find the min and max luanti/minetest versions
22:24 bgstack15        I'm envious of people who can think in Go.
22:24 Sheriff_U3       So far it's in very early beta (especially since I only started today).
22:27 Sheriff_U3       bgstack15: I'm using the AI for creating the program lol. As a test of an AI's ability to create a standalone go package. I've tried them before with luanti mods, but have found that they lack enough knowledge about luanti to be useful.
22:27 bgstack15        Lol, I'd like to think it's the strict licensing of Luanti mods that kept the copyright expungement engines from ingesting their contents.
22:27 Sheriff_U3       For the most part it's been feeding it information and cutting out the slop.
22:28 bgstack15        I suspect that's how computing will end up over the next 10-15 years: it spews out garbage and it's up to the user to whittle it down to the good bits, like sculpting, or Geordi's instructions to make an enemy capable of defeating Data.
22:29 Sheriff_U3       Same, but I think that it gets thrown off mostly by Luanti's modified lua 5.1 and little quirks + the fact it keeps thinking roblox or minecraft modding instead lol.
22:30 Sheriff_U3       Another star trek fan? :)
22:30 Sheriff_U3       I remember that episode quite well :)
22:31 bgstack15        Oh yeah, I don't have those coding contexts, but I have read recently that since Lua is embedded into things and not really updated like a single app should be, apps tend to add their own quirks. They don't have need to update to Lua x+.1 because even Lua doesn't really deal with backwards compatibility.
22:31 bgstack15        Yes. I was hoping you'd get the reference. I suppose not everybody into free software is also into Star Trek, but nerdy interests tend to overlap somewhat.
22:32 [MatrxMT]        <Blockhead256> 5.2 was a big break in compatibility, plus then LuaJIT is faster and never went past 5.1, which meant it was basically impossible for many engine devs who embed Lua in their games to want to update. I think 5.3 and above weren't quite as bad
22:32 [MatrxMT]        <Blockhead256> *they never wanted to update because they didn't want to break their users' mods or give up performance
22:33 Sheriff_U3       I found it interesting when in TNG they mentioned the fact that their computer/programs are 32bit lol.
22:34 MTDiscord        <luatic> 5.3 brought 64 bit integers done wrong. big mistake
22:35 MTDiscord        <luatic> pall is also no big fan of <close> and he's not wrong either
22:35 MTDiscord        <luatic> unfortunately it doesn't loook like defer is happening in luajit...
22:39 Sheriff_U3       idk that Minetest had rats at one point: https://github.com/luanti-org/luanti/commit/4556c212dba726271352b05a9299564e05abb218
22:49 Sheriff_U3       Does anyone know about when .tr translation was added? Been looking through commits for about 30 mins without success. (Of course someone didn't add it to the changelog or mention it in lua_api.txt when it was added...)
22:49 [MatrxMT]        <Blockhead256> 5.0 for client-side translation I think
22:49 [MatrxMT]        <Blockhead256> everything before that was intllib
22:50 [MatrxMT]        <Blockhead256> there is the unassuming changelog section https://docs.luanti.org/about/changelog/#user-interface-1
22:50 [MatrxMT]        <Blockhead256> .po is more recent and should be findable
22:51 Sheriff_U3       I know that .po has been around since 5.10, someone was nice and added that info to lua_api :)
22:52 Sheriff_U3       Blockhead256: thanks I missed that!
22:54 [MatrxMT]        <Blockhead256> np, guess it comes with being around for a while. Huh, your forum account is only back to 2025, you've been playing longer though, right?
22:55 Sheriff_U3       nope
22:56 [MatrxMT]        <Blockhead256> oic
22:56 MTDiscord        <wsor4035> imagine having a forums account
22:56 Sheriff_U3       I discovered Luanti back in October 2025.
22:58 Sheriff_U3       I started learning Luanti modding around the 2025 game jam time frame, with toolranks being my first real project. After that it was Circuits.
22:59 Sheriff_U3       Though both of those are forks and not ordinal to me.
22:59 Sheriff_U3       *original
22:59 [MatrxMT]        <Blockhead256> huh, I guess I really thought you had some background before circuits. Anyway I'm conflating that you have a level of experience with tech in general with you actual background with Luanti
23:01 Sheriff_U3       As far as Luanti is concerned I'm still really new lol.
23:02 Sheriff_U3       Same with Linux as well, started using Linux Mint around September 2025.
23:03 [MatrxMT]        <Blockhead256> ah, the year of the linux desktop
23:03 Sheriff_U3       as is every year it seems
23:05 [MatrxMT]        <Blockhead256> the way I see it is everyone has (potentially) their own personal year they switch to the linux desktop, not some universal year. For me, it was 2021
23:19 MTDiscord        <the4spaceconstants2181> this year was mine
23:19 Sheriff_U3       Hows it gone for you?
23:23 MTDiscord        <the4spaceconstants2181> very well
23:25 Sheriff_U3       that's nice, I had trouble with my laptop freezing on Linux... fixed it by disabling cstates.
23:26 MinetestBot      02[git] 04appgurueu -> 03luanti-org/luanti: Fix remaining issues with multi-track animations (#17306) 13304c6d3 https://github.com/luanti-org/luanti/commit/304c6d3fa87539fa4e376ef926e2a274217bab1f (152026-06-30T23:24:30Z)