When using the new move command (clone command with move mode) I keep getting crashes if my structure includes chests or trapped chests. The error seems to be a " awy cannot be cast to awn" error. Crash report included.
Just to be clear it's not tile entities in general. I'm able to include furnaces just fine. Ender Chests however turn invisible.
Time: 23/05/14 3:36 AM
Description: Ticking block entity
java.lang.ClassCastException: awy cannot be cast to awn
at awn.n(SourceFile:213)
at awn.m(SourceFile:250)
at alk.i(SourceFile:1363)
at bjs.p(SourceFile:1697)
at bjs.ah(SourceFile:843)
at bjs.f(SourceFile:797)
at net.minecraft.client.main.Main.main(SourceFile:121)
Details:
Name: Chest // awn
Block type: ID #164 (tile.stairsWoodDarkOak // aui)
Block data value: 1 / 0x1 / 0b0001
Block location: World: (-38,77,31), Chunk: (at 10,4,15 in -3,1; contains blocks -48,0,16 to -33,255,31), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Actual block type: ID #164 (tile.stairsWoodDarkOak // aui)
Actual block data value: 1 / 0x1 / 0b0001
Linked issues
is duplicated by
Attachments
Comments

After reporting this I stopped getting the error. I've gotten the problem once since, when putting down a chest that instantly texture-transformed into an ender chest. Same "awy cannot be cast to awn" message with the crash. But it didn't repeat the next time I loaded. Since then if chests texture transform to ender chests (yes it happened again later) I break them rather than looking in them. I think I should make a seperate ticket for the "chest transforming into ender chest" bug.
Ok when travelling south (a lot of these clone-move glitches are direction dependent) the Ender Chest turns invisible EVERY TIME. Attempting to look in the invisible ender chest crashes the game with "awy cannot be cast to aww" (yes "aww" this time instead of "awn"). Simply breaking the invisible ender chest makes it go away safely.
Also using /fill to place invalid chest locations causes the game to crash with a similar error

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.
Cannot confirm/reproduce
worked fine for me 😞
*A other bug happened but this is not important to mention here I guess (MC-55702)