So, I was messing around with double-extenders and testing the shortest delay I can have between powering pistons for both pistons to extend. Suddenly, I stumbled upon this design which, for no reason, not only extended both pistons, but retracted them simultaneously. I assumed this was a mechanic of the game, but when I attempted to replicate it for my other designs, due to it's simplicity, I found that this design can result in three different possibilities: (1) Both pistons extend and both retract back to their original positions, (2) both pistons will extend, but when both retract, the upper piston stays in place above the bottom piston instead of reverting back to the starting position, (3) or only the upper piston will extend and then retract. So, I wanted to test if this was based on chunk errors, x to y to z differences, etc. so I went into MCEdit and cloned up a total of 3,200 copies of identical designs in a mesh design. Now, I have only test about 460 of these, but as the pictures show, there is no apparent pattern. I am at a loss and I assume that most anyone else who witnesses this would be, as well. I browsed the issues and bugs open and resolved and found similar bugs, but nothing such as this. And this is not direction-based either, which is the reason I tested the last 60 before reporting. I assume this has to do with how each individual chunk updates, but it must be location-based as well for the reason that each individual contraption always has the same response. I color coated option (1) in green, option (2) in black, and option (3) in blue.
Related issues
relates to
Attachments
Comments
migrated
migrated
the issue your seeing is with a bug in the timing of red stone ticks across a seed. I don't remember the bug number but basically the algorithm that determines a tick is based on location as well as time so at certain points a tick will be .00001 quicker or slower than another spot (number is exagerated).
I set up your example in my 1st screen shot and set up the fix for it in my 2nd screen shot. Its just as simplistic al be it needing one more block than yours and a repeater. Basically giving it the delay it needs. (yes there is a button on the bottom iron block, and ignore my redston work in the back ground)
Torabi
Is MC-11193 the issue you're thinking of?
migrated
Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
migrated
@ Talven81 - Yes this is still an issue. I've kept the same setup shown above and it still reacts based on location of the piston.
Ezekiel
Is this still a concern in the latest Minecraft version 14w08a? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
migrated
Updated for both 14w08a and 1.7.5
migrated
Although, interestingly enough it seems that since I last checked, the results of my tests have changed, like which behavior was associated with which color wool I used. I predict this may be due to the terrain update? I haven't checked any of the 1.7 snapshots or updates until now.
migrated
Is this still a concern in the current Minecraft version 14w18a / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
marcono1234
Confirmed for 14w21b
Seems to be caused be the game mechanic to update/load redstone maybe
Perhaps caused by: MC-11193
galaxy_2alex
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
galaxy_2alex
Reopened, thanks
migrated
This is simply the hashset at work and I believe it is intended (no idea why but whatever...)
migrated
I really hope this isn't intended, but I agree.
wobst.michael
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
SunCat
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-11193.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki