Fix cascading world gen in the Nether (MC-117810)

[bs2609]

Fix for MC-117810, just adds a +8 offset to the x and z coordinates, same as all the other non-WorldGenMineable populators.

[LexManos]

Problem with Forge doing this is that it changes the locations of vanilla worldgen. And thats something we have to keep with vanilla.

[bs2609]

Had a slight bad feeling there was going to be a catch...

If it doesn't look like Mojang are going to fix this anytime soon, would this be acceptable if it was made a config option?

[LexManos]

That might be a option. Opt-in to breaking vanilla worldgen compat.

[KingLemming]

Honestly I think an opt-in is the ideal way to handle this, and it should be handled. :)

[raoulvdberge]

If this is opt-in (almost) noone will toggle this flag, making this change useless.

[KingLemming]

Can config options not be distributed with modpacks or something? This is far from useless, and keeps with a stated Forge goal of not actively jacking with vanilla.

[LexManos]

Honestly, anyone who cares about runaway chunk generation enough to know what it is will know how to switch a flag.
Most people don't care that the game loads more chunks than it needs to. It uses a little more RAM, oh well.
I'm working on this, along with trying to find the other worldgen issues. It'll take me a little time.

[LexManos]

0ad4218