MC-411Terrain Generation Issues
I created 2 DEFAULT worlds with the seed "LightChase", one in Version 1.3.2 and the other 1.4.2 Pre-release. Both versions give me the same world with a partly generated cave (See Picture 1 and 3), a river that didn't float down (See Picture 2) at where it should be, ork trees and a lake south-eastwards (See Picture 4). I tried to recreate it several times and I was given the same result.
Then, I created a Large BIOMES world with the same seed in 1.4.2 Pre-release. This time, I was given a world with a similar cave yet fully generated (See Picture 6, notice the trees are gone), a Swamp biome which didn't show up in the Default world (See Picture 6, on the right), the same lake at the same position of the Default-world lake (See Picture 5).
I think, and I believe, that it's a generation bug occured because of a code error.
Environment
System:Windows 7
Java:Jre 7 update 7
Linked Issues
Created Issue:
A Generation Bug from 1.3.2 to 1.4.2 Pre-release
I created 2 DEFAULT worlds with the seed "LightChase", one in Version 1.3.2 and the other 1.4.2 Pre-release. Both versions give me the same world with a partly generated cave (See Picture 1 and 3), a river that didn't float down (See Picture 2) at where it should be, ork trees and a lake south-eastwards (See Picture 4). I tried to recreate it several times and I was given the same result.
Then, I created a Large BIOMES world with the same seed in 1.4.2 Pre-release. This time, I was given a world with a similar cave yet fully generated (See Picture 6, notice the trees are gone), a Swamp biome which didn't show up in the Default world (See Picture 6, on the right), the same lake at the same position of the Default-world lake (See Picture 5).
I think, and I believe, that it's a generation bug occured because of a code error.
Environment
System:Windows 7
Java:Jre 7 update 7
Attachments6
duplicates
duplicates
relates to
duplicates
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
AGenerationBug from 1.3.2 to 1.4.2 Pre-releaseTerrain Generation Issues
is duplicated by
For previous discussion about this issue see MC-411
I got the new seed-and-pos in 13w36a so the bug exists still.
Seed: -689819745 (feiwudeyinghuaa)
Pos: -325 351
@[MOD] Anon Ymus You may not understand it. In MC-411
@[Mod] Tails said:
Resolving this since the upcoming update changes terrain generation quite a bit. If there are any new issues with the new terrain generation, please create a new ticket.
However in Snapshot 13w36a I see this bug again so it's not resolved at all. And as Trails said: "If there are any new issues with the new terrain generation, please create a new ticket.", I created a new ticket.
Since this bug exists, you can reopen MC-411, add 13w36a as Affected version and leave this issue as duplication.
See MC-411. Duplicate or at least related to. EDIT: note: its state of "invalid" is basically a forgotten state, it should have been reopened for proper evaluation.
Im pretty sure this is not a bug. At lease a very minor bug.
Sorry, this has always happened to some extent over most updates.
Looks normal. Not a bug. Caused by a minor change in how the seed is used. As the 1.4.2 generation will consistently produce the same terrain with the same seed, it's definatly not a bug.
This generation bug has happened on all of four worlds I've generated in 1.4.6 with random (inputless) seeds. Doesn't seem normal to me at all. I have screenshots of one of the worlds.
Resolved as duplicate of
MC-6820, there are the reasons for this behaviour.The screenshot numbers seem to be mixed up (due to way how JIRA switches order when uploading more or something).
Actually, most screenshots depict a different issue than the
MC-6820. I think this issue could be the same or at least related to issueMC-7200(also reported by me and has a fix).Would be nice to get seeds and locations if anyone spots similar straight cut surface caves/tunnels. I could easily check the bug then.
@Markku Yes it's mixed up. And I agree mine is more related to
MC-7200thanMC-6820.Ok, relinked to
MC-7200but leftMC-6820as a potential relation.I managed to create that same world and gave a bit of surgical knife to the cave generator code...
I first applied the two fixes, but that didn't help, so this issue is NOT related to either
MC-7200orMC-6820.I then suspected another piece of code and made a specific change to prevent that code working in the relevant coordinates (allowing that tunnel to continue no matter what that suspected code was deciding). And this time the tunnel did continue, like shown in the other screenshot. Thus that suspected piece of code is the reason...
... But the disabled piece of code is an intended feature, though implemented in a bit crude way. Namely, there is specific check in the cave generator code for NOT tunneling into water; it stops the tunnel just before it. It is not perfect, as it makes a sharp cut instead of trying to do some fancy natural shaping (difficult!).
So, this particular case is "intended feature". Changes to it should probably be a feature request along the lines of "more natural caves/tunnels near waters".
Added a screenshot for the case when the stop at water -feature is disabled for tunnel generation.
Ok, reopened this ticket.
Leaving the links as "related to"
Cannot reproduce in the latest version of minecraft
Can you provide a seed?
@Ezekiel As I just bought a new computer, you might have to wait for some days so that I could see whether I can reproduce it. Thank you for remembering this issue.
Can reproduce in 1.6.2. (Note, the seed, "LightChase", is in the description...)
Note, this issue is more about a somewhat extreme and visually bad effect of an intended coding feature. See my comment earlier and the 'disabled_water_stop_feature' screenshot what happens when the feature is disabled. However, the current operation obviously creates quite disturbing shapes. Mojang needs to decide whether they consider this small enough a problem to leave as "won't fix", or if they want to try to make a better tunnel "shaping" algorithm. Note also that most likely, this same "feature" is the reason why e.g. large ravines can be cut vertically sharply when a river passes through it, etc.
Resolving this since the upcoming update changes terrain generation quite a bit. If there are any new issues with the new terrain generation, please create a new ticket.
No longer valid, complete rework of terrain generation code in 1.7.x
@Talven81 The same bug still can be seen in 1.7.x (e.g
MC-29466)