What I expected to happen. When you place a Redstone torch so it connects to the side of a block, it will stay connected even if I leave the chunk the blocks is in but keep the chunk the torch is in.
What happens is the redstone torch drops itself as an item as If i broke the block it was connected to.
To reproduce: Find a chunk boundry and place a block that a redstone torch can be placed on the side of on 1 side ofthe boundry, place the torch on the other side of the boundary so it connect to the other block but is in a different chunk. Fly away some distance so that both chunks become unloaded. Walk back to the place where you had the torch. You will see that the torch has dropped itself as an Item.
Update by @unknown:
Also affects:
Lever
Sign
Torches
Update by @unknown:
There are steps to reproduce this in MCPE-17271.
Moderator note by @unknown:
Please limit comments to only new information regarding the issue.
Linked issues
is duplicated by 44
relates to 3
Attachments
Comments 39
Relates to MCPE-14113
This bug occurs with cocoa pods and beds in 1.14.30. However, I cannot reproduce this bug with any of the blocks listed in the title, so I think the fix in 1.2.0.11 was successful. I have created a new ticket for cocoa pods, MCPE-67479.
Just had this happen today. I've loaded this world a dozen times and today when I loaded in, all the paintings in the room where I had logged out in were floating on the ground. It was just the one room and it DID occur along chunk borders. I'm guessing the chunk with the paintings loaded in first without the wall in the next chunk attached to it?
Just had it happen again. Interestingly enough it didn't happen when I loaded in. I checked to make sure everything was intact, then told my friend to go ahead and join. When SHE logged in I saw everything pop off. Everything was fine for me when I loaded in but a friend joining caused the issue. This was probably the case the first time as well but I wasn't paying attention for it. She noticed it that time as well. She also loads into the same room as me. Incase I didn't mention, this is a local world.
Can we please have this ticket reopened? It's clearly not fixed.
Chris: the issue you are describing is tracked at MCPE-142303.
@unknown confirmed this still a problem in build 5.