It is possible for entities to be at the bottom of a Soulsand bubble column and not rise within it. I suspect the entity is sitting in the gap at the top of the soulsand hitbox, just below where the water bubble column starts.
Linked issues
Attachments
Comments 4
Note: I haven't played Minecraft for about 5 years so cannot comment to the bug still being present. Since the bug was a product of the physics produced when hitboxes of partially filled voxels interface, it might very well still be evident, unless 'fixed' by "waterlogging" mechanics.
In 1.13.1 The soul sand hitbox does not fill the entire voxel.
This causes a gap between the top of the soul sand hitbox and the top of the voxel it occupies.
The bubble column starts at the bottom of the voxel above. It is possible for entities to sit in this gap above the soul sand and below the water of the bubble column.
Steps to reproduce:
Create a bubble column on top of soul sand.
Inject entities onto the top surface of the soul sand, below the water of the bubble column.
In my initial report I showed an automated dropper firing entities onto ice and sliding into the bottom of the bubble column system where some of the entities could get caught in the gap below the water.
In the recreation by Alexis they use a spawn egg in creative mode to directly inject skeletons onto the surface of the soul sand, where the bubble column fails to propel them upwards.
I hope this helps.
Thank you, that helps a lot 🙂
After some further searching around, I was able to find MC-207866, which is triaged and seems to describe the same general behavior of entities (items in this case) getting stuck in the bubble column. Considering this issue hasn't really been maintained in recent years, it might make sense to merge this into the listed report/resolve it as a duplicate.
(Also, as a side note the image attached by Alexis is bedrock rather than Java, so the behavior is different)
Can you still reproduce this issue in the latest version, or snapshot? Considering the lack of updates since version 1.15 Pre-Release 2, and no consistent steps to reproduce, it is difficult to tell how to get this issue to occur again. Any information you could provide would be appreciated. 🙂