goshdang it, despite reminding everyone else of this week in week out, I didn't enable the 1.20 pack first 😞 can someone please close?
I mean sculk_vein, sorry! Fixed the references above.
Relates to MC-104900 - can you verify if this is still an issue in the latest snapshot?
The bugtracker is not a place for suggestions, as you seem to be aware. Take this to the official feedback site as your request is just going to be ignored here.
Chains are now waterloggable as of 20w18a
Ulraf has confirmed in his Sunday stream that he believes this to be a bug, posting this message with his consent.
@nighter @[[Mojang] Adrian Östergård|https://bugs.mojang.com/secure/ViewProfile.jspa?name=nighter] could we get some clarification as to why this is a 'won't fix'? If I'm honest, without this being fixed it seems like y level biomes may as well not exist, for all the difference it makes to the game.
Duplicate:Â https://bugs.mojang.com/browse/MC-170849
I didn't state that this was a cave update. The issue aims to highlight that the vast majority of new nether terrain does not seem to have y level biomes, and the parts that do, don't seem to have correct boundings.
I'm inclined to disagree - these y level biomes examples are so rare it took a team of us over an hour to find an example, and even then certainly doesn't align with any observable edges for biomes like you'd typically see in any other biome in the game. Even if they intentionally fuzz, the examples listed above show no real pattern to their placement, and certainly should not be random blocks, or groups of blocks within other biomes. We've heard that vertical biomes are not finished, and I would strongly argue that until proven otherwise, this is a valid bug report to track issues with an incomplete feature.
Still in 1.14.2
Maybe it's already fixed as a side effect on your branch, but you said you couldn't find anything wrong with End Cities. Those were just reproduction steps for their issue in 1.14 if you wanted to test it further.
Â
EDIT: Well, not entirely sure what 1.14 version that world was generated on, made a fresh one now and also can't reproduce it for End Cities.
@unknown I can consistently reproduce the issue for End Cities by trying to get the advancement in a City that has already been generated and/or the advancement triggered by someone else. This also applies for 'The City at the End of the Game', not just custom advancements.
Confirmed for 1.14.1 and 1.14.2 Pre-Release 2
Confirmed for 1.14.2 Pre-Release 2
@[Mod] Neko Apologies for the ping, but as you can't view your profile from Alexander Egorov's ping, it looked like it might not have workedÂ
Can also confirm for 19w08a, seems to be worsening compared to previous snapshots.
Thanks, I've only just seen their spawning rules via docm's findings. While their flawed design is another problem completely, I've updated the ticket to reflect the core issue.
Yes.. As per the issue description: