MC-248858Falling blocks no longer creates block updates in entity phase
The bug
In 1.18.2, falling blocks no longer produces block updated in the entity phase. The expected behavior would be for falling blocks to produce a block update when the sand entity gets ticked in the entity phase due to the sand block being removed.
How to reproduce
- Build the attached build in a version prior to 1.18.2. Observe that the bottom block is pulled to the side before the second top piston pushes.
- Build the same build in 1.18.2. The second iron block is no longer pulled to the side due to the lack of a block update in the entity phase scheduling an early block event.
Linked Issues
Created Issue:
Falling blocks no longer creates block updates in entity phase
In 1.18.2, falling blocks no longer produces block updated in the entity phase.
The expected behavior would be for falling blocks to produce a block update when the sand entity gets ticked in the entity phase due to the sand block being removed.
To reproduce:
1. Build the attached build in a version prior to 1.18.2. Observe that the bottom block is pulled to the side before the second top piston pushes.2. Build the same build in 1.18.2. The second iron block is no longer pulled to the side due to the lack of a block update in the entity phase scheduling an early block event.
![[Mojang] MimmiB](../../../data/avatars/users/18949.svg){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
In 1.18.2, falling blocks no longer produces block updated in the entity phase.
The expected behavior would be for falling blocks to produce a block update when the sand entity gets ticked in the entity phase due to the sand block being removed.
To reproduce:
1. Build the attached build in a version prior to 1.18.2. Observe that the bottom block is pulled to the side before the second top piston pushes.2. Build the same build in 1.18.2. The second iron block is no longer pulled to the side due to the lack of a block update in the entity phase scheduling an early block event.
The bug
In 1.18.2, falling blocks no longer produces block updated in the entity phase. The expected behavior would be for falling blocks to produce a block update when the sand entity gets ticked in the entity phase due to the sand block being removed.
How to reproduce
- Build the attached build in a version prior to 1.18.2. Observe that the bottom block is pulled to the side before the second top piston pushes.
- Build the same build in 1.18.2. The second iron block is no longer pulled to the side due to the lack of a block update in the entity phase scheduling an early block event.
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
is duplicated by
Due to changes to falling block physics in 1.18.2, presumbably connected to MC-248858 they sometimes start behaving a bit erratically. For instance - it's possible for 2 falling block entities to fall on the single spot, which makes it possible only one of them to convert ot to the block, when the other drops as an item. That in general makes it rarely drop cubic gravel blocks when you use a shovel with Fortune 3, which has never been before (it has always been dropping flints only) and probably must not happen (similar to manner Slik Touch shovel used on gravel always drop cubic blocks and not a single flint).
How to reproduce:
Go to Nether 15 height, give yourself pickaxe eff 5, shovel eff 5 AND fortune 3. Find a gravel vein and dig it out from the bottom. Notice it will drop some of cubic gravel blocks, which has never been before.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
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.
This bug has also broken a falling edge that relied on sand to be pulled up to power a comparator. In the image attached, the comparator will not power when the button is pressed in versions 1.18.2, however it will before 1.18.2. Unsure whether the issue is the same or not
We decided to resolve this issue as works as intended.
The change was caused by the fix for
MC-243015.In short, block updates in chunks that are not entity ticking could cause several falling block entities to spawn, as the block was not removed right away.
But this was not the only issue caused by the delayed removal of the block, like for example
MC-238200and MC-151488.There also were issues it caused for the implementation of dripstone, that required less than ideal workarounds.
While it's not clear why the removal was delayed to begin with, I believe it was a workaround for an engine limitation that since has been resolved, as applying a similar fix to Beta 1.7.3 causes the flickering when sand falls: https://www.youtube.com/watch?v=lL3soEOygnA
(It also was the cause of a sand duplication glitch back then; though unrelated to the current ones with end portals)
While it is unfortunate to lose the emergent behavior described in this report, it is not considered important enough to back away from the fix, as there are also alternative ways to get similar timings.