Steps to reproduce the bug:
1- Place a repeating command block near you with this command in it:
kill @e[type=minecraft:falling_block]2- Set the command block to "Always active"
3- Place any gravity affected blocks (GAB) (sand, gravel, etc ...) in a case where the block is supposed to fall
4- The block won't fall until the command block is deactivated AND the GAB is updated
Demonstration video: https://youtu.be/k8AQ_MDccMY
The only command blocks used on this map are those shown in the video, and there are no custom datapacks loaded
Linked issues
duplicates
Attachments
Comments
migrated
migrated
Re: Dhranios
Sadly, it's a bit annoying when I'm using this behavior to, for example, fill a space with a specific block only when there is a support block.
For that particular case, I finally used carpets as they work as intended.
Arisa Bot
Thank you for your report!
We're tracking this issue in MC-56037, 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.
The cause for this is because the block actually doesn't delete itself, the falling block entity is supposed to do that on its first ticking (if they are the same block, or else it would delete itself, in order to prevent a duplication bug).