When I try to set up these pistons pushing sand up, it works sometimes, and other times it pulls in the sand, pushes the sand up, it falls back down, gets pushed back out, then back in until it finally stays up, sometimes it gets stuck trying to push sand up over and over until it finally works and stays up. It's very unpredictable. I've tried different delays with repeaters and it doesn't seem to change the consistency of it. Happens with other redstone contraptions as well but this is the one that I'm dealing with right now.
I know there's several other reported issues that are kind of the same thing, but they all get marked as "resolved" but the bug is still there so I don't understand why they keep getting marked as resolved.
Also I know it's not "working as intended" because redstone logic should not be random, sometimes working and sometimes not.
Linked issues
Attachments
Comments 2
When a ticket is "resovled," you should look at the Resolution field. If it says "Duplicate" that means that the ticket is reporting a bug that has already been reported on another ticket. We do not keep multiple tickets open for the same bug. This is not like customer support where tickets receive an individual response.
Based on the description and pictures what you are experiencing is working as intended. There is no predetermined activation order for redstone components affected by the same redstone update. This ticket will be resolved as a duplicate of MCPE-16371. Since that ticket is already resolved Working As Intended, it is not considered a bug. Please do not leave a comment. You may leave feedback on on the Feedback Site.
Please note "Redstone-Logic" is not random ONLY on Java edition. This is working as intended for Bedrock. Only the Piston update-order on Bedrock is random due to technological limitations. If you want Mojang to change the update-order, make a feed-back post. Redstone-Components other than Hoppers, Pistons and Observers are intended to be consistent.