Summoning a "falling block" within a block of same type causes the block to disappear.
Also, doing the same but with the "time attribute" causes the block to simply stop rendering itself.
In any case, blocks shouldn't disappear, the intended behavior is simply to summon an entity, not to destroy a block.
How to reproduce:
Easy way to reproduce it, for block disappear:
Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {NoGravity:1b,BlockState:{Name:"minecraft:stone"}}
Easy way to reproduce it, for block stop rendering:
Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {Time:1,NoGravity:1b,BlockState:{Name:"minecraft:stone"}}
Expected behavior:
Summoning a sandstone (or any other block except stone) on a stone block does not cause it to disappear or be destroyed. (Because it's not the same type the "block entity" vs "block")
Open any world, with commands active
/setblock ~ ~ ~2 stone
/summon minecraft:falling_block ~ ~.8 ~2 {Time:1,NoGravity:1b,BlockState:{Name:"minecraft:sandstone"}}
Comments 3
MC-72248, yeah.
Thank you for your report!
We're tracking this issue in MC-72248, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This ticket actually appears to be a duplicate of either MC-72248 or MC-114286. I'm not too sure, my apologies. 🙂