FOSS gamedev and creative worlds

While thinking about how to better test my mapgen, I had the idea that it would be neat if I'd be able to reload parts of it on the fly, without the need to exit the subgame and restart it. There is no direct facility in Minetest that allows it, but we can work around it with a chatcommand and by encapsulating the important code in a function or object. Obviously you can't reload everything, as there are things that just need to be known when the mod starts, but other parts can be reloaded.

Let's have a look at the basics on how to accomplish this, assume this to be in the init.lua:



And that's the basic framework, now you can run the command "reload" from within Minetest and "dynamic.lua" will be reloaded, you can make changes to "dynamic.lua" and simply reload it without having to exit Minetest.

You could also do that with a mapgen system, for example (note that the code assumes my utils mod to shorten it):



Now you can make changes to the system, type "reload" in Minetest and the next piece of the world is generated the new, reloaded system will be used.

Right. Reloading the code isn't the problem. Dealing with the effects of the old code is what can screw things up. Any code module that gets reloaded needs to be carefully structured to take care of side effects. If it registers objects or callbacks, can they be replaced, or overridden somehow? Will old objects and functions still be referenced, essentially creating memory leaks and unexpected behavior? Those are the difficult sort of questions to answer, not whether or not dofile() can be called again. They make the "can" and "should" question very specific to the particular context in a mod.

It will work perfectly fine if the dynamic file only declared functions. The main init file could then register these in a callback through wrapping.



I came up with a practically identical idea last year, but I've never used it other than in dev tch demos.

Of course you'd have to restart minetest if you want to add new call backs, unless you make a mechanism for it.

Dynamicly changing the code while working on a mapgen sounds like a very good idea. I just wonder how practical it actually is. There'd still be the need to fly into new terrain in order to get it generated. Or is there a way to get the current chunk beeing regenerated anew, without restarting the game?

@Sokomine If it is probably encapsulated you'd only need to call it again for already existing blocks, either invoked by moving into it or when being invoked by a command. But no, I don't think that there is an automatic way.

You can use minetest.delete_block or whatever to delete mapblocks. They should then be remade in a few seconds. Also see /delete_block

@rubenwardy I guess you mean "delete_area"? If yes, I have to try that, that sounds intriguing.

And it works, obviously. Pretty neat.

More fun - prevent interrupt load script if error present on run.
Hmm but runtime errors still crash game.