psldbtj33ll

This issue was resolved but has now returned in a recent version.

This bug seems to have returned for me in 1.21.51. (Windows 10)

I've been able to verify that all languages have US-style date format, not just English (UK). Maybe the title of the post should be changed? It also seems likely this affects more people than discussed here as many will not speak English to see the reports.

I think this might be related to Minecraft now only saving "visited chunks" - I've found similar strange chunk errors in my pre-1.18 world - trial chambers appearing in existing chunks that hadn't yet had below y=0 generated. If you convert the world to java and look at it on a program like Chunky you see very scattered random patterns of chunks with terrain below y=0 following roughly where the player has travelled, but with many random un-generated gaps. I'm guessing these gaps then generate trial chambers within them, and the chambers can't overwrite the existing explored chunks for good reason. Hence, random chunks of the trial chambers are missing.

I'd add that similar scattered patterns of chunks appear when exploring new terrain as well. This is very noticeable on chunk maps of the world, but would be impossible to see in-game since the distant un-generated chunks appear normally. I think newer exploration always generates down to y=-64. The player travels to new areas, generating random scattered chunks (in 1.20), then returns later to find a trial chamber, to find that it only generates in new 1.21+ chunks. The random chunks that the game decided to save when the player first explored the area have no trial chamber within them, but the new chunks do.

I doubt there's any way to fix this in existing worlds, but improving the system that Minecraft uses to decide which chunks to save might solve problems like this in the future. If you have an existing world and want to find an intact trial chamber, the only option is to travel to unexplored parts of the world. The irony here is that doing so will create more scattered chunks, meaning any new structure added in the future will have the same problem in these newly explored areas.

I'd add finally that the older pre-1.18 system of saving chunks wouldn't have necessarily made this situation much better. The system saved way more chunks, meaning that rather than having a partial trial chamber, you would just have nothing. That might be less confusing but there would also still be structures crossing the boundary between old and new chunks. This kind of problem is probably just inevitable with large structures meeting existing chunks. 

Likely related to MCPE-181249

Unfortunately I don't have any at the moment - I'll post one here if I find one in the future

There is a world file here - My 0.9.0 World.zip

Unfortunately I can't send any worlds, since I can't verify if there's private information on the signs since they're blank. One of the worlds I noticed the bug in was created on Android in December 2015 or January 2016, so most likely 0.13.1

Intentional behaviour, this was added in the recent Armoured Paws update.

Potentially linked to MCPE-181249, which causes worlds from pre-0.9.0 versions to crash the game.

I have added one of the worlds that causes the crash (My World–.zip)

This bug has only been there for me since around 1.20.30. It could be related to the fix for MCPE-171797.

Until the aforementioned bug was introduced, the elytra worked as intended (Windows)