Modpack Version

0.5.11

Describe your issue

Looks like half of a mountain generated.

Seed:-909185449
Coords: 866, 112

Crash Report

No response

Latest Log

No response

Have you modified the modpack?

No

User Modifications

No response

Did the issue happen in singleplayer or on a server?

Singleplayer

I do wonder, if this change in latest update could be the reason:
Adjusted biome weights to make the most common biomes a bit less common.

It shouldn't be, we've tested this before, and the conclusion was that switching biome weights in TerraForged does not alter existing worlds.

Thanks for the report.
Are you sure you didn't modify the modpack in any way? That HUD in the top left is not default.

No - I think the HUD was one of the fps options.

No - I think the HUD was one of the fps options.

That is Optifine, that has been added, you can see it in second picture too as listed.
Although it shouldnt affect terrain generation, but nobody knows what it actually does, being Closed source and not recomended.

Has this world been generated in earlier versions of the pack? Im not sure, if there has been any changes to generation, that could have made that.

Was this with default terrain generation, TerraForged?

I loaded 0.5.11 and created a world (default settings) with that seed and teleported to the coordinates, everything is fine, so something has changed world gen in your savegame at some point.

I do wonder, if this change in latest update could be the reason:
Adjusted biome weights to make the most common biomes a bit less common.

Here is screenshot and you can clearly see in minimap that bottom is identical to yours:

Some kind of terrain generation change happened in the transition between 0.5.6 and 0.5.7 (tested with my own world seed, spawn is quite different). I tested it when i noticed the change in my 0.5.6 world after updating to 0.5.9 and chalked it up to the usual "mods updated, generation changed".

This is the provided seed/coords in a fresh 0.5.6 instance.

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.