RobinDinVienna

If you power that rail it will flip. That is intended. It will always connect in one way, and can be flipped one other way through powering it. Any other behavior, as great as it would be, is a feature request.

One random block with no rhyme or reason to be there is a bit different from the floating formations we had since ever, isn't it...

Did music discs ever give off a note? That I only know from note blocks (which actually play a note then)

It gave me this in the log in the launcher upon freezing up: 

Encountered an unexpected exception java.util.concurrent.CompletionException: z: Feature placement at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320) at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159) at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482) at acx.b(SourceFile:58) at auk.g(SourceFile:91) at auk.a(SourceFile:146) at auk.run(SourceFile:102) at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) Caused by: z: Feature placement at acv.a(SourceFile:639) at com.mojang.datafixers.util.Either$Left.map(Either.java:38) at acv.a(SourceFile:621) at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150) ... 11 more Caused by: java.lang.IllegalArgumentException: Cannot set property cou{name=extended, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in Block{minecraft:air} at coe.a(SourceFile:117) at cny.a(SourceFile:364) at cnu.c(SourceFile:115) at cob$a.b(SourceFile:839) at cob$a.k(SourceFile:835) at cjk.a(SourceFile:96) at cob$a.a(SourceFile:969) at caz.b(SourceFile:310) at cye.a(SourceFile:41) at cvv.a(SourceFile:80) at ddw.a(SourceFile:56) at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) at java.base/java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:411) at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762) at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276) at java.base/java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:411) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596) at ddw.a(SourceFile:55) at ddw.b(SourceFile:44) at cpz.a(SourceFile:315) at cqb.c(SourceFile:146) at cqb.a(SourceFile:289) at acv.a(SourceFile:627) ... 14 more

And upon killing the java process I get the attached crash report. ("
The game crashed whilst exception in server tick loop
Error: java.util.concurrent.CompletionException: z: Feature placement
Exit Code: 9
")

Indeed, that makes the gamewindow go black after a while... I see. 

I was able to open the world on MacOS Monterey 12.0.1. on the pre-relaese (5)

There are 2 blocks at former build height (close to where I spawned) and normal terrain below around y70. Is that how it is supposed to be?

Generally, Mojang tries to have no damage done to the world that the player is not causing or able to stop themselves. So a Creeper should only ever explode as aggro to players. No other mobs.

Thanks for the link

Can confirm for 21w41a see my below-comment on: MC-238903

Just to show it incase someone cares: Same village has a nice little "farm" 

Still looking for examples of this one, but one minor one is where the stairwell intersects with a grassy cave at /tp @s -10512 ~ -944 on seed 1088126630841226858

edit: Another slight example:

Same seed:

/tp @s -9616 ~ -1312 Intersecting the aquifier

Another, better aquifier example:

incl. waterlogged inside:

Well, ouch. I guess just in the lack of a "dunno how to fix" resolution option. But OK, then...

The order of the names is also not alphabetical: My correcting suggestions for that also include fixes to such inconsistancies: https://bugs.mojang.com/browse/MC-223552

As I found many more such inconsistencies, I extended the bug report to collect all wrong orders/typos that I could find in the new json. Now made the list a table.

Also here: NO modification. I don't know what Allen Reichert is on.

No, it is not. It is the normal minecraft launcher, the current snapshot and the credits roll/file contains the text like this. NOTHING modified here!

Sadly. But I don‘t get why. Don‘t even want consistancy? 

How is the resolution here a won't fix? What happened here? Then I guess the bug is that lava cauldrons do burn you or what? Inconsistencies/bugs just not getting fixed all over?

As this is not a "1.17" Bugtracker, but the general Minecraft Java Bug-Tracker, all affected versions from the time of finding the bug at least should be marked. 1.16.5 is the CURRENT RELEASE version. So of course, if the 'bug' exists in it, it MUST be listed.

 -- 

And such bugs could also be fixed in a 1.16.6. Who knows, so it would not make sense removing any release version.

As the commenter I was replying to noticed the nonsense they were writing and deleted theirs, I shall leave this here crossed out for reference...

Hope this just becomes a WAI at some point. Anything else would be a waste of resources and these pillars are a nice big source of obsidian... The deeper the better. Maybe we get them down to -64 in the next update?