FOSS gamedev and creative worlds

In mapgen v7 is there any way to prevent cave generation above a certain height, specifically to avoid large gaping holes in the terrain? I've struggled with this dilemma for quite some time, but have yet to find a solution. I've tweaked all of the relevant the noise parameters, yet certain caves seem to ignore both "mgv7_np_cave1" and "mgv7_np_cave2". I've searched Google the past two days, but there is very little technical documentation about customizing mapgen v7, just a lot of screenshots. What am I missing?

Any help or direction would be greatly appreciated.

Please paramat, help! The only way I found was to disable all cave generation, as well as rivers. It messes up the map. :(
Moreover, I forgot how to disable this.

Thanks maikerumine. Indeed the only workaround I've found is to set mg_flags to "nocaves". But that undermines my goal, since I do want caves in my world. If only there was a cave_depth_min and cave_depth_max parameter to restrict the cave generation range.

It seems I successfully devised an interim solution at least for Minetest 0.4.13, by reworking the following code in cavegen.cpp:





I also defined "surface_level" and "terrain_surface_level" within the appropriate structs and classes of cavegen.h and mapgen.h. And, of course, I added "terrain_surface_level" to mapgen.cpp, as a user-definable parameter.

I was hoping to implement a "terrain_bedrock_level" as a counterpart to "terrain_surface_level" thereby setting the minimum cave generation range, but that would have required far more substantial changes to cavegen.cpp (as it stands, the upper limit was already conditional on "mg->water_level", so that was an easy enough replacement.) Since I'm fairly unfamiliar with the mapgen logic, I didn't venture much further for fear of breaking something important.

This of course is just a quick and dirty fix. Ideally there would be a formalized specification for cavegen parameters, maybe in a future release I hope :)

There are 2 types of cave in mgv7: the web of narrow tunnels, and the large blob-shaped caverns which sometimes have water or lava. The surface holes are mostly the tunnels, you can't limit these according to y but you can remove the tunnels without removing the large caverns, if this sounds good to you i'll tell you how.

Your code above only affects the large caves, not the tunnels.

Hi paramat, I would be interested in learning more about any solutions you can suggest. I tested a number of different caves, including those with tunnels. Each time I reduced "terrain_surface_level", the depth of the caves would adjust accordingly and any non-conforming tunnels would disappear.

Trial #1: http://imgur.com/a/Z62Qt
Trial #2: http://imgur.com/a/mIsIC
Trial #3: http://imgur.com/a/Z0vLs

Perhaps I'm missing something, but each of the test cases above worked. On a sidenote, I overlooked these two snippets of code that I changed as well in cavegen.cpp.

0.4.13 has these 3D noise tunnels https://github.com/minetest/minetest/blob/0.4.13/src/mapgen_v7.cpp#L864
But you can easily limit those on a per-mapchunk basis in line 861.

Thanks for the tip paramat. I can see from mapgen_v7.cpp that the tunnels can only be limited on a per-mapchunk basis.

However, am I to understand correctly that while the function "generateCaves( )" creates the tunnels, the function "makeTunnel( )" is what actually creates the caverns? Isn't that backwards? O_o

In non-mgv6 mapgens generateCaves() creates the 3D noise tunnels and also the classic large caves from mgv6.

makeTunnel() was named for mgv6 where that code creates both the large caverns and the smaller tunnels by varying the width, both are essentially tunnels because they are a string of excavated volumes.