Reforestation after a Widlfire?

[Nüchterwolf]

Heyo

On my 4 Player Server, a massive fire we didn't notice for way too long just cleared out a substantial area of jungle, leaving our Island desolated and barren looking.

Is there a easy way to restore the woodlands that grew there? Maybe a Mod, or a server command to restore the chunks to the way they were generated?

 

We could also roll back the server several hours, but we'd all loose a lot of progress, so I'm unwilling to do that.

 

Thanks in advance,

Nüchterwolf

[Professor Dragon]

I'm guessing that the world regeneration command will be your friend here:

https://wiki.vintagestory.at/List_of_server_commands/wgen

Something like "/wgen regen 2" if you wish to regenerate the two chunks around where the command issuer is standing.

WARNING: This command is destructive.
Do not operate near ANYTHING you wish to keep. This includes Ruins and Mounts, as well as player built structures.

I'm not sure how this works on a multi-player server. I guess it will run just as it does in single player.

The alternative is to replant a lot of seeds.

Professor Dragon.

[Nüchterwolf]

Thanks, this is exactly the kind of thing I was looking for.

I'll make sure to back up the server before using it. Thanks a lot, you saved me a lot of headache.

Have a nice Weekend,

Nüchterwolf

[MKMoose]

59 minutes ago, Nüchterwolf said:

Is there a easy way to restore the woodlands that grew there? Maybe a Mod, or a server command to restore the chunks to the way they were generated?

To add on to what @Professor Dragon has suggested.

You can use the command /wgen regen <chunk_range> (e.g. /wgen regen 2) to regenerate chunks in the given chunk radius. Using /wgen regen 0 will only regenerate the chunk you're currently in. This will remove any of the changes you've made to these chunks, and has the potential to be very destructive - make a backup before messing with it.

You can also try using /db prune <threshold> <keep/drop> as a faster and more robust but less precise alternative - it will remove all chunks which have had a number of changes made by players lower than the given threshold. It is also risky, and it might not work quite as well on older worlds, so again, make a backup. After running it, double-check that it didn't remove things you wanted to keep.

• The threshold is the minimum number of player-made changes for a chunk to be preserved.
  • Use e.g. /db prune 1 keep for very careful regeneration, where only chunks with no player-made changes are removed.
  • Increase the threshold to maybe ~3-5 to also discard almost-unchanged chunks.
  • Use e.g. /db prune 10 keep for more aggressive deletion, which might remove a couple things you've placed or left in chunks.
  • Increasing the threshold above ~10 is generally not recommended unless you're absolutely sure you really want to clean up the world more aggressively.
• The keep/drop option refers to whether land claims should be preserved, which preserves any structures (e.g. traders) as well as player-made claims. You could use it to deliberately protect your structures after making a claim on them, but it should be usually unnecessary.
  • Change keep to drop in any of the commands listed above to also regenerate structures.
• Initially, it will tell you how many chunks would be removed and kept. Once you decide on the specific command, add confirm to it to actually run it (i.e. /db prune <threshold> <keep/drop> confirm, e.g. /db prune 3 keep confirm). If you're unsure, you can run the prune with a lower threshold first and increase progressively if it doesn't have the expected effect.
• After running /db prune, you can also take the chance to run /db vacuum to reduce the save file size.
• Finish by reloading the world.

Recreating the forest more or less manunally is also a possiblility, but for an area this large it would take a prohibitively long time - still, you can consider it in chunks which you can't regenerate without losing something. If you need to see chunk boundaries near your structures, use .debug wireframe chunk.

And also, in case you have fire from lightning enabled, you can consider turning it off with /worldconfig lightningFires 0 to avoid this kind of situation in the future.

Edited October 17 by MKMoose