Luanti Forums - Index page
forum.minetest.net.web.brid.gy
Luanti Forums - Index page
@forum.minetest.net.web.brid.gy
Problems • Re: A most puzzling ore spawn issue
I'm a bit confused... If it's too late to register new ores at that time, then logically none of my own ores should be registered since that occurs only within the callback. But during testing I found that most of my ores were being registered, just not all of them. It was puzzling because the ores which failed to register were all located inside the same files where the working ores are. For example, gemstones are working and are registered from within "mineral-non_metal-ore.lua", but all the other ores in that file are missing from the table. Most stones are registered, but a few are missing. All of the metal ores are missing, which is really odd since that file is loaded before the one that registers the gemstones.<br><br>Apparently I've spent too much time in a terminal and forgot that Firefox can read plaintext files, which solves my non-issue of posting code *facepalm* Here's the broken init.lua file, and in the meantime I'll be reading that forum you linked.<br><div class="codebox"><p>Code: </p><pre><code>local geopath = minetest.get_modpath("geo")---- API and Config--geo = {}dofile(geopath.."/config.lua")dofile(geopath.."/api/climate.lua")---- Nodes--dofile(geopath.."/nodes/stone-sedimentary-node.lua")dofile(geopath.."/nodes/stone-metamorphic-node.lua")dofile(geopath.."/nodes/stone-igneous-node.lua")dofile(geopath.."/nodes/sediment-node.lua")dofile(geopath.."/nodes/mineral-metal-node.lua")dofile(geopath.."/nodes/mineral-non_metal-node.lua")dofile(geopath.."/nodes/blocks.lua")---- Items and Tools--dofile(geopath.."/craftitems.lua")dofile(geopath.."/tools/flint.lua")dofile(geopath.."/tools/ruby.lua")dofile(geopath.."/tools/sapphire.lua")dofile(geopath.."/tools/hammer.lua")----[[ Mapgen--NOTICE: The exact order in which these files are loaded seems to matter morethan I once thought. For example, if lava.lua is loaded earlier in the chainthen the magma conduits will never form, but the code still runs and causes lagwhenever I break something.--]]---- Clear the ores table.--local ores_copy = {}for k, v in pairs(core.registered_ores) doores_copy[k] = vendcore.clear_registered_ores()---- Initialize new ores--if geo.config.gen_stone thendofile(geopath.."/mapgen/stone-upper_mantle.lua")dofile(geopath.."/mapgen/stone-crust.lua")dofile(geopath.."/mapgen/stone-chunks.lua")endif geo.config.gen_sed thendofile(geopath.."/mapgen/sediment-ore.lua")endif geo.config.gen_ore thendofile(geopath.."/mapgen/mineral-metal-ore.lua")dofile(geopath.."/mapgen/mineral-non_metal-ore.lua")endif geo.config.gen_lava thendofile(geopath.."/mapgen/conduit.lua")core.register_mapgen_script(geopath.."/mapgen/lava.lua")endlocal delete = {["default:stone_with_coal"] = 1,["default:stone_with_copper"] = 1,["default:stone_with_tin"] = 1,["default:stone_with_iron"] = 1,["default:stone_with_gold"] = 1,["default:stone_with_diamond"] = 1,["default:clay"] = 1,["default:sand"] = 1,["default:silver_sand"] = 1,["default:gravel"] = 1,["tnt:sulfur_block"] = 1,}---- Replace missing ores.---- NOTICE: The API doc says core.registered_ores is indexed by name, but when-- printing 'k' during debug it just gave a bunch of numbers, while 'ipairs'-- simply gives nil and is useless here. We use 'pairs' and 'def.ore' since-- that does return the node name as a string.--for key, def in pairs(ores_copy) doif geo.config.gen_ore thenif not delete[def.ore] thencore.register_ore(def)endelsecore.register_ore(def)endend---- Support for other mods--local mods = {"animalworld","advtrains","anvil","bweapons_bows_pack","composting","livingcaves","quartz","torches_redo","techage","tnt",}for i, v in ipairs(mods) doif core.get_modpath(v) thendofile(geopath.."/support/"..v..".lua")endendcore.register_on_mods_loaded(function()for _, def in pairs(core.registered_ores) doprint("GEO-LOGICAL: " .. def.ore)endend)</code></pre></div><p>Statistics: Posted by <a href="https://forum.luanti.org/memberlist.php?mode=viewprofile&amp;u=49614">rg19</a> — Wed Jan 28, 2026 10:21</p><hr />
forum.luanti.org
January 28, 2026 at 10:26 AM
Problems • Re: Graphical Errors in 5.15.0 (DO NOT UPDATE YET!)
> Well, unfortunately, there's practically nothing I can do, because I refuse to go to 5.15.0 until the graphical glitches are resolved. > I found it within 24 hours of the updates release. Yet, none of you care about it, I know Mojang would never let such graphical glitches fester, which is why every release of Minecraft lacks any significant graphical glitches. Consider me as "Staying behind" in this case. Look, I know this is frustrating. But in effect you're refusing to get yourself help, because you're the only one has both (1) experienced this glitch and (2) reported it. We do care, however you can't expect us to fix an issue that we can't reproduce or on which we simply don't have enough information. We are all on different computers and phones, on different operating systems (such as Android versions). Mojang is a multi-dollar company who can test their game on all the hardware they want it to run on. Luanti is a volunteer project where the community are invited to test things, but there is never any guarantee. It's absurd to compare the two. > Making matters worse: Android doesn't permit downgrading applications, so I was forced to uninstall the application, which resets it, and nothing was left. So it's more difficult to send screenshots from 2 different versions if I refuse to go forward. Maybe somebody else ran across it, and I hope they supply the screenshots to prove my point. I'm sorry you lost your data. It's quite bad that Android won't let you gracefully downgrade, and the files can't be touched by other apps usually. It is all up to you what to do. Consider though, that since you already are starting from scratch, maybe pushing harder to get the bug fixed by providing more data is not so bad an option. Have you got much to lose? Well, if it's going to make you lose your temper, then that's fine, leave it be. > I just showed the glitch to F-Droid, and they are legitimately shocked that such a glitch exists in Luanti. So F-Droid could revert back to 5.14.0, which would lead to a version dispute. That would be pretty drastic. I have 5.15 installed through F-Droid and no problems with it. Statistics: Posted by Blockhead — Sun Jan 25, 2026 01:50 * * *
forum.luanti.org
January 25, 2026 at 1:53 AM