Time Nick Message 05:12 * cheapie stares blankly at a line of code in someone else's mod 05:13 cheapie target:set_physics_override(tonumber(1), tonumber(1), nil) 05:14 cheapie ...massively outdated (and no longer even working, I think) way of calling set_physics_override() aside, I'd like to know what, exactly, compelled them to write "tonumber(1)" 06:32 MTDiscord in case 1 stops being a number obviously, foward compatibility xD 08:36 MTDiscord I'm having a texture issue with a mod that has appeared in newer versions of Luanti (I'm not sure exactly which). I'm currently using 5.10.0. Instead of loading the appropriate texture the entity's appearance is as shown in the following screenshot: 08:36 MTDiscord https://cdn.discordapp.com/attachments/749727888659447960/1327556783304343562/screenshot_20250111_001945.png?ex=67837f19&is=67822d99&hm=2401f389e52ad0395a86afdd0d6cbaa8042776eb1d6d13f7a8cab0d3aa74bc79& 08:37 MTDiscord It is supposed to be either a black, brown, or white horse. 08:38 MTDiscord There aren't any warnings or errors reported in the server log. And I don't know what the texture image being used is. 08:39 MTDiscord It looks like some kind of failsafe. But if I remember correctly, images aren't used for failsafe drawing of entities, rather a single color. 09:00 MTDiscord It appears to be an issue with old .x format models. 09:02 ll0lll0 I've seen it before 09:03 ll0lll0 I think it had to do with a table vs a string 10:17 MTDiscord Well, now I can't reproduce it. I changed the entity textures property from a table to a string. It appeared to fix the problem. So I changed it back to a table to make sure & created a new world. But the textures are working now. facepalm 10:45 MTDiscord Okay, I have determined the cause of the error. The textures property was being set to nil. Thanks ll0lll0, your hint actually let me to focus on the textures instead of the model. I was curious as to why no error or warning was emitted. But I suppose that is because the textures property isn't required since textures embedded in the models are supported? 10:45 MTDiscord *led me to focus 10:46 ll0lll0 :) 10:46 ll0lll0 I have no idea why it happens. Took me ages to figure out 10:48 MTDiscord I suppose it's just an artifact of the model not having an embedded texture. 10:50 MTDiscord But, that's just an assumption as I am very much a novice when it comes to 3d modeling. 10:50 ll0lll0 same 14:48 MTDiscord Do you have chat_log_level = warning, or are you looking at a terminal for warnings? 14:49 MTDiscord I'm asking because of #15209 14:49 ShadowBot https://github.com/minetest/minetest/issues/15209 -- Stuff printed at 'warning' log level is essentially invisible to normal users 14:50 MTDiscord AntumDeluge: Note that we don't support embedded textures at all 15:43 MinetestBot 02[git] 04cosin15 -> 03minetest/minetest: Fix CFileSystem::FileSystemType related UB (#15669) 1337899f7 https://github.com/minetest/minetest/commit/37899f7a14826ec78df3cad8d2b0dca44490d757 (152025-01-11T15:42:36Z) 15:43 MinetestBot 02[git] 04Desour -> 03minetest/minetest: VoxelArea: Fix missing cacheExtent calls in helpers (#15657) 13436b391 https://github.com/minetest/minetest/commit/436b391a800c267f6caabfe4adaee055120225e2 (152025-01-11T15:43:20Z) 15:43 MinetestBot 02[git] 04Desour -> 03minetest/minetest: Remove the unnecessary MeshCollector::append overload 13cbc074f https://github.com/minetest/minetest/commit/cbc074feb5e3e1bbb7e53011622ea7b09e16fe3b (152025-01-11T15:43:37Z) 15:43 MinetestBot 02[git] 04Desour -> 03minetest/minetest: transformNodeBox(): Replace BOXESPUSHBACK macro with a lambda 131e81c45 https://github.com/minetest/minetest/commit/1e81c454c8ed459c76c3bbae25e74f62a372e4a4 (152025-01-11T15:43:37Z) 15:43 MinetestBot 02[git] (9 newer commits not shown) 19:41 MTDiscord Should I enter the nodetimer question to the bugtracker, if I have a minimal repro? 19:41 MTDiscord Yes please