![]() ![]() If that results in a fire somewhere, grab some marshmallows, not a delete key. So some peoples' world configs temporarily break - what else can be done? G*d forbid people have to re-configure their worlds if some mods get temporarily disabled. load_mod_foo should always and forever refer to a single mod at the top-most level of the mods directory, and never from a modpack, no matter how badly the engine wants to look in a modpack for it.You're seriously going to argue about the validity of this bug and legitimacy of the years-old modpack feature, and then leave the feature just plain broken for two months? WTF? Ok, fine, I get it. This is NOT a modpack bug, this is an engine bug, it's frankly being stupid and naive about loading mods. If I delete DB from ~/.minetest/mods, purge world.mt of load_* entries, and enable those mods again, everything works as expected. If I uncheck "Hide mp content" and look at the listing of DB's contents, some of the mods I asked for got pulled from there instead of the top level, and at least one not loaded at all (luacontroller), regardless of its viability. Close Minetest and go back into the world configuration, and only digistuff looks like it's enabled, I guess since that's the only one of those five that doesn't have a DB counterpart. The engine throws the previously-mentioned override warnings and then proceeds to load some of the mods I asked for from places I explicitly avoided asking for, and breaks the dependency resolver, as it fails to load some mods (inconsistently warning me of dependency failures in the process). If I clear all load_* entries from world.mt, fire up Minetest and ask it to enable only the individual mods digilines, digistuff, mesecons, mesecons_luacontroller, roads from the top level of the mod listing, and I click Save, and then go look at the world.mt file, it's spammed with tons of entries (all set to either nil or false) for stuff I never asked for. That's deliberate, as they supply new functionality that I wanted to test in an otherwise stock minetest_game environment, and a copy of DB just happens to also be stored in ~/.minetest/mods, for use with a different world than the one I am using for the test. ![]() All items not marked as "modpack" above are singular mods, some of which are newer than their Dreambuilder (DB) counterparts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |