From MCPE-124552:
Block data in affected worlds has shifted +64 Y resulting in the following problems:
Double chests changed to single chests
Chest empty
Item frames empty
Banners changed to solid gray/black
Beds all turned red
Mob heads all changed to skeleton skulls
Potions in cauldrons changed to water
Armor stands and minecarts disappeared/buried underground
Pets and animals suffocated/stuck in caves underground
Blocks pushed by sticky pistons no longer retract (compare MCPE-111632)
Returning from the nether through a nether portal puts player inside solid blocks underground.
All of these effects are explained by the fact that entity and tile entity position data did not change with block data. The game therefore read default or <0> state/contents for blocks that should have tile entity data (e.g. empty chests and item frames, red beds, normal skeleton skulls)--compare MCPE-78279. Entities ended up relatively 64 blocks lower, mostly inside solid blocks.
Character inventory is ok. Chest inventories are empty. All double wide chests now display as 2 sperate chests. Random clouds appear on the ground as if parts of the world are not loading, but if I walk through the walls the environment is loaded, just not the inventory in chests.
Broken after the update on 8/25/2021. Worked fine 8/24/2021.
Linked issues
is duplicated by 51
Attachments
Comments 24
I also noticed, no clouds in the sky. My main village and storage area is at cloud height now, 131. My village used to be at around 64, so it seems the earth is .... bigger?
All captured villagers are gone. All captured animals show up as dead, beef, hides, feathers, wool, etc.
I was so frustrated....all of my chest entities are all gone , Ok for the player inventory but all my large chest become 2 small chest
I assume this is caused by the world height being shifted up 64 blocks, rather than starting at -64 it now starts at 0. And some data, block data in particular it seems (chest contents, signs, lecterns, etc.) wasn't accounted for, resulting in a new block being placed without carrying the old data over. Not too sure though.
@unknown
The screenshot clearly shows version 1.17.30.24.
And I think this is true information. And this happens due to an attempt to return the raised chunks to their place. Apparently there was an error and worlds that have not actually undergone changes associated with version 1.17.30.23 anyway "return" the chunks to their place (to -64 height). After the test [MCPE-139669] in version 1.17.30.24 I was unable to reproduce the error, and the old world returned whole chunks to their place.
https://bugs.mojang.com/browse/MCPE-139669?focusedCommentId=1065427&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1065427
I can provide the world if needed for testing.
the nether has some issues to and the end as well as they don't convert 100% the same between versions and i made a new bug report thats about /setblock not working on the first time you load a world from a prior version/ earlier version than 1.17.30.23 then load it in that version or later with caves n cliffs toggle enabled. Called MCPE-140623
Nathan: when you say this issue affects 1.17.40.20, do you mean that
a world loaded in 1.17.40.20 that was not previously affected by this issue, can be affected? In other words, that block data shifts upward in 1.17.40.20?
Or do you mean that
worlds where the shift happened in 1.17.30.23 still contain the shift?
If it's the latter only, then this bug does not really affect 1.17.40.20.
All experiments are turned on except "Experimental Molang Features".