While building a flying machine I noticed that under certain conditions my piston does not pull back the slime/honey block in front of it. I broke it down to the constellation that you can see in the first screenshot (2020-10-04_19.45.22.png). The second screenshot (2020-10-04_19.45.39.png) happened after flicking both levers. The third and last shows what happened after turning the levers back of. As you can see, the slime blocks in the middle of the bottom contraption are not pulled back, and I can't really think of a reason to why that is, so I decided to file a bug, as this doesn't seem right to me.
If there's an actual reason behind this, then I'd be happy to know! Thank you.
Note: I'm playing a modded version of Minecraft, but this behavior is also reproducible in the vanilla version and the newest Snapshot of the game.
Related issues
Attachments
Comments


Please provide a screenshot of your game with the F3 debug screen enabled.

Should be added to the attachments.

Thank you for your report!
However, this report is Invalid.
Your game is modified.
If you can reproduce the issue in a vanilla game environment, please create a new ticket - this is a bug tracker for the game, and not a support website.
Any issues occurring from game modifications need to be taken up with the appropriate team, not Mojang Studios or the Bugtracker.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord

I have also tried this with the newest Snapshot (status 2020/10/04), same results.

Would you be so kind and reopen this issue? I'm not going to open a new one with the very same content.

The provided screenshots still show a heavily modified game.

I've added one made in the newest vanilla 1.16.3 snapshot.

One theory I have about the bottom contraption transitioning from screenshot 2 to 3 is the following: The middle piston is directly powered by the observer behind it. The piston below it on the other hand is powered by quasi-connectivity. Under normal circumstances (when there's no block update above that piston), it wouldn't extend, but since there is a piston above it - the middle piston that is - it receives a block update and is thus powered and can extend. The same is true for the retraction: the bottom piston only retracts because the piston above it causes a block update.
Knowing that, and assuming that the order of operations is (1) middle piston retracts and (2) bottom piston retracts, then it would make sense that the slime block cannot be moved back, since it sticks to the block below it which itself is blocked by the immovable extended piston.
I think this might actually explain it. Let me know what you think.

I've reduced the example to this - flick the lever and the same behavior can be observed:
[media]
Assuming my theory is true, the question would be if this is intended behavior or not, since you'd (or I would) normally think that the order of operations shouldn't matter when the pistons retract during the same tick.

You are correct about why the piston isn't pulling. I doubt this behavior would be changed though, since so many redstone contraptions use update order, and that type of change to it would break most of them.
Thank you for your report!
We're tracking this issue in MC-108, 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 would like to learn more about this particular feature, see this article on the Minecraft Wiki.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki