Un-explore the world ?

[Ivà]

@solars:
I tried your script and works like a charm. But I had to install libdbd-sqlite3-perl on a debain system to avoid the db modules failures.

@lag01:
I tried your script too and it does what you say :-), but I think it would be better if it saves a configurable area around all the blocks defined in useful_block_evidence. People tends to modify the surroundings of the things they build, with this script as is, these modifications are'nt preserved. If we could define an area around it would be fantastic.

[eli_3]

Hello,
I minetest version 0.4.10 and I would like to install the 0.4.12.
If I install the 0.4.12 I duplicate the worlds of 0.4.10?

[Don]

Hello,
I minetest version 0.4.10 and I would like to install the 0.4.12.
If I install the 0.4.12 I duplicate the worlds of 0.4.10?

When you install a new version of minetest it does not change existing worlds. They will still be there.

[eli_3]

thanks

[prestidigitator]

There's a somewhat easier way to do this. Export the areas you DO want to keep using a mod. Create a new world with the same seed, mapgen parameters, mapgen-influencing mods, etc. In the new world, import the whitelisted blocks with a mod when their locations are generated, and let the normal map generation take care of the rest. It's obviously still some work, but doesn't require mucking with the database directly.

[rubenwardy]

There is a command for this, /deleteblocks, I believe it's called.

[prestidigitator]

There is a command for this, /deleteblocks, I believe it's called.

Oh. Huh. And that just calls minetest.delete_area(). That must be new in the API. Cool.

Now added to wiki: minetest.delete_area()