When using a clone command with the move option to teleport a structure downward non-solid blocks (chests, hoppers, and signs) replace each other (only visually).
The pictures show a structure teleporting downward one block at a time. The chest at the bottom begins to render in front of the objects above it although it is not really there (as shown by me standing in the "chest").
However, as shown in the last picture, when I relog everything is fine until I try and clone the structure again.
I should also mention that each time it teleports downward i get the debug error "Unable to locate sign at x y z".
I've tried everything I know to fix it and have been unsuccessful leading me to the conclusion that it must be a bug.
Related issues
is duplicated by
Attachments
Comments
migrated
kumasasa
MC-3564 is about having the "Unable to locate sign" message at all, this ticket is about not rendering a sign.
migrated
Shouldn't you use wall_sign instead of sign in the testforblock command? Or am I wrong?
migrated
The testforblock command is not used in this structure. It is a clone command using the move option. If the testforblock command was being used you would be correct.
Skylinerw
Confirmed for 1.8.3. Issue is caused by more than 64 block updates occurring in a chunk. Trying to place the block in a location where blocks previously existed before the client is sent chunk data causes the rendering issue and sign message. The server knows the new block(s) exists of course.
Not really any work-around, though. Luckily it's a client-side issue so things aren't actually breaking.
migrated
@Skylinerw So it's related to the "only 63 block updates per chunk problem"?
Also what counts as a block update? Is it only related to blocks with extra data like chest, hoppers, and command blocks?
migrated
MC-3564 is fixed, that means this is fixed
migrated
Resolving to MC-82703.