hkniberg

We moved the snow level higher in C&C part II because of the higher terrain. In 1.17 mountain biome the rain becomes snow at around y100 and above. In 1.18 that is moved up to around y130. 

Turns out this actually isn't a duplicate.

Thanks. I managed to repro it myself also. I agree it is hard to repro in a consistent way right now. But now we at least know the bug still exists.

I believe this is fixed. If not please reopen and provide an updated repro case.

Is this still an issue? If so please provide an updated repro case.

Large ore veins are large on average. But only on average, so sometimes you will be unlucky and encounter an extra small one. Similarly, you could get lucky and encounter an extra large one.

This bug is fixed now I think. The random holes are a separate issue, can confirm that. I suggest making a separate ticket for that.

Since 21w40a surface biomes can no longer be on top of other surface biomes, so I suspect this isn't an issue any more.

sigh... fixing it again

This is an old issue that is a lot more common in 1.18 because of the terrain.

This is specific to savanna, since those farms follow the terrain, thus exposing the water. The water doesn't tick at first, so it just hangs there. But then once the crop ticks it causes the water flow, causing savanna villages in hilly terrain to be overrun with waterfalls. 

This is still a bug though. The portal shouldn't generate under the netherrack. The cause seems to be that the portal is right on the border of two biomes, and they are fighting over which type of portal it should be.

Panda trying hard to hide in the jungle.
  

Thanks for finding an example. This example is a floating aquifer. With the current aquifer implementation that will happen sometimes when a small aquifer coincides with a large cave. As long as it is fairly rare we will most likely not fix this.

If this is still an issue in 21w44a please provide updated seed & coords.

Wave to the panda

Note that Groves currently don't generate trees (MC-236698) which will be fixed for next snapshot. This may contribute to the feeling of less interesting terrain.

Cannot reproduce this, but could use some help testing.

This is probably just a matter of perception. The seeds have a changed a bit. The general terrain elevation is the same, so plateaus and rivers and such should be in the same general locations. But the detailed terrain shape is different (the 3d noise), so jaggedness and overhangs and peaks will be different. Some areas will be more jagged & extreme in experimental snapshot 7, other areas will be more jagged and extreme in 21w37a.

I think what happened here is that people are revisiting known locations from experimental snapshot 7 with dramatic & extreme terrain, and finding that they just look less dramatic on 21w37a, which is statistically likely. That should go both ways. If you find some dramatic terrain in 21w37a and visit those in experimental snapshot 7, the same location in experimental snapshot 7 is likely to be less dramatic.

To test this properly, you need to visit a number of new random locations on both versions and compare. On average the extremeness of the terrain should be similar - sometimes more dramatic on one version, sometimes more dramatic on the other. If not, let us know!

This is useful input. But the diagram was not intended to be exact (the title says "Approximate ore distribution"). We may tweak these ranges in the future, once we have mountains to test with. But for now this works as intended.

This bug has nothing to do with aquifers, so I renamed it.

This is closed because it represents an opinion more than a bug. We might still improve it (aquifers are still in early development) but we don't want keep open Jira tickets for things like this.

On a more important note: accusations of laziness are not helpful or constructive. Neither are opinions about what should be easy or what should be the "correct" solution.

Design is all about tradeoffs. If a design doesn't seem optimal it may be because we made a tradeoff to avoid some other problem, or because the problem is non-trivial and we have decided to focus on other more important things first.

We welcome feedback, but keep it constructive and respectful. And keep in mind that WAI doesn't necessarily mean we won't improve it. It just means we don't want to set that expectation.