Pistons can be waterlogged.
Pistons, much like Glass, should not be possible to waterlogg. They should behave like a solid block even if it’s trasparent, similar to Glass.
This could be a serious issue because Redstone still breaks underwater. Their for someone could easily destroy a redstone build because of this bug.
Linked issues
duplicates 1
Attachments
Comments 6
Still exists in 1.5. The update I would think it would be fixed in. Really hope this can be addressed. Ive destroyed 2 redstone builds now because of this. Postons should be treated like a solid unpassable block and water should not be able to interact with anything other then the piston head itself.
Copy of MCPE-32437 (or the other way around because here are some more information 🙂 )
Still exists in beta 1.6.0.8 tested on win 10 and Android 5.0 and 4.4.2
I like this "feature" to build some funny farms but on the other hand it can be annoying if you are not careful enough.
Thanks for the report, however this has been reported before as MCPE-32437, please search before reporting. Comment any extra info you may have on that ticket. Thanks.
Really... I have been watching this report for so long. Only to be told nearly 80 days later that it was a dupe. Like a week or two makes sense. But 80 days!?! Thats nearly 3 whole months. I even updated this post twice in that time making it reappear at the top each time. It’s not like it was buried. Wow... if it takes 80 days to tag it as a dupe. That would explain why it takes so unbelievably long to fix other basic critical bugs like this one.
If it was tagged like a week. Even 2 after. That would be understandable. But 80 days... no. I need to call that out. Sorry but thats bad, really bad. Dosen’t help my trust or respect with the bug tracker at all.
Joshua De Ruiter
Please refrain from making such comments as they do not help in fixing the bug.
Please understand that we mods and helpers do not wait for some time before marking a ticket as a dupe, we check a ticket if there is an earlier report. We find dozes of other dupes in some tickets and sometimes it takes longer to see if there was an older and updated report. This ticket was considered a dupe because a mod found an earlier report with the exact same bug.
Still exists in 1.4.2