Description
When a minecraft:falling_block entity is summoned via the /summon command and its Time value is set to 0, it does not replace the corresponding block, although the BlockState is exactly the same.
What I expected to happen
Time:0 used to replace the block it was summoned inside, if the BlockState tag of the entity was the same as the block it was inside of. This would only leave the falling block behind, giving the effect, as if the block had started to fall down.
What actually happened
The block did not disappear and did not change in any way.
How to reproduce
See attachments for details. Stand on top of a floating block of minecraft:polished_granite{}. Execute the following command:
/summon minecraft:falling_block ~ ~-1.0 ~ {Time:0,BlockState:{Name:"minecraft:polished_granite"}}
Attachments
Comments 2
Thank you for your report!
We're tracking this issue in MC-248858, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
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.
Duplicate of MC-248858