mojira.dev
MC-65372

Large biome worlds use normal-size river generation.

See screenshot "1.7.10" which was taken in Minecraft 1.7.10, and screenshot "14w31a" which was taken in Minecraft 14w31a. Both using "Large Biomes" world type with seed -4253180711807921163, floating at position (107,155,35) looking at the same small lake.

Notice that version 14w31a has significantly more river. I believe this is because the snapshot is using the river placement from "Default" world type, meaning that rivers are not being spread out the same way other biomes are. Note that previous versions of Minecraft used the correct skewed placement (to match the Large Biome theme).

This is an error in world generation because (1) rivers are not being skewed and positioned as they should and (2) because previous versions of Minecraft skewed and positioned them as expected.

For what it's worth: I've used AMDIST to map the seed in both Default and Large Biome versions, and it turns out that the rivers in Minecraft 1431a are indeed being placed in the exact same locations they would if the world were Default type.

Linked issues

Attachments

Comments 6

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.

I've found this issue to still exist in the current 1.8.1 Minecraft version, I've already posted a minecraftforum.net topic on this issue a while ago: http://www.minecraftforum.net/forums/minecraft-discussion/recent-updates-and-snapshots/2307527-1-8-1-8-1-default-scale-river-generation-in-large

I can confirm this is still an issue in 1.8.2 pre-releases, seeing terrain borders at half-generated lakes where 1.7 chunks meets 1.8 ones. Perhaps affected versions should be extended to 1.8.2-pre1 to 1.8.2-pre4 and the environment updated to Java 8u25.

I just tested this on release 1.8.7 and it is still an issue.

This is still an issue in 1.8.8...

Same problem still in 1.8.9

Solus Lumidas

Erik Broes

Community Consensus

Minecraft 14w31a, Minecraft 1.8, Minecraft 1.8.1, Minecraft 1.8.7, Minecraft 1.8.8, Minecraft 1.8.9

Retrieved