I am aware of the recent change to pistons (From the Minecraft Wiki: "Blocks now lose their waterlogged state when pushed by a piston.") but I want to find out if this change was intentional or not, because to me, it just wouldn't make sense for a retracted piston to act as a normal block in water.
Something else I noticed while testing it, when it pushes a waterlogged chest, it removes the water completely when the chest is moved (part of the bug that was fixed). I'm not sure how this worked before the 1.16 update, if the piston moved the water with the waterloggable block or if the piston only moved the block, not the water.
Attachments
Comments 2
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Before the 1.16 update, the water would not be moved, but the block could be moved in and out of the water without the water being destroyed. They did this to remove zerotick farms and called it “parity” even though on the Java edition waterlogged blocks do not lose their waterlogged state when moved.