Updated descripton by @unknown
Steps to reproduce
Set a repeating command block with the command /setblock X Y Z <block> destroy
Set up a sticky piston attached to a clock circuit so that it repeatedly pulls away then pushes back the the blocks that are set.
Expected results
Each time the block is destroyed by commands, it drops that block and you see particles for that block.
Actual results
Sometimes the block does not drop, and you see update block particles.
Demo using above steps
[media]Original description
Moving blocks do not drop items when broken by withers or commands. The easiest way to reproduce this bug is to set a repeating command block with the command /fill (x y z)(x y z) air 0 destroy, and then you push blocks with pistons within the region of the fill command.
Linked issues
is duplicated by 4
Attachments
Comments 13
Sorry about that, I will provide a video as soon as I can, I also understand that I should do a better job explaining the bug and reproduction steps of the bug. Also, while I was writing the bug report I actually meant that when you push blocks into the region of the fill command, the block doesn't drop any item, I am truly sorry for the confusion.
When you add the "destroy" part of the command it is supposed to drop the item of the replaced block, normally it does this, but with moving blocks it doesn't.
i had MCPE-180388 i added my world to this bug fix where i was testing to see if block 36 was added to bedrock.
Hi, could get ownership of this ticket because will can update if happens aswell in the nintendo swich.
Much the same as MCPE-84280 can you please clarify what you mean and how you are coming to the conclusion.
A video of the issue may help us identify the bug you are reporting. Based off the description I'm a little lost.
Your repro descriptions would seem to demonstrate that breaking a block immediately on placing doesn't drop the block rather than the block being moving.