Pistons aren't retracting as they should. Changing redstone BEFORE pistons change their behavior.
What I expected to happen was...:
Piston retracting independently from the route taken by redstone
What actually happened was...:
Changing the position of the redstone wire some blocks BEFORE the piston, changes piston behavior
Steps to Reproduce:
1. Put pistons, redstone and lever as shown in pictures
2. Try to switch on and off the lever
3. Remove the piece of redstone shown in pictures and place it in the other corner
4. Try again to switch on and off the lever
Related issues
Attachments
Comments
migrated
migrated
migrated
I don't see how that issue is related (MC-108)
migrated
Not resolved
migrated
It is. You're powering a piston from 2 blocks above, hence as to why its resolved.
migrated
migrated
@Sonic did you watch the attached images?
migrated
These pistons were working in previus versions
migrated
new screenshots
migrated
[Mod] Mustek why you assigned "Status: Resolved" "Resolution: Duplicate" ?
migrated
not solved
CubeTheThird
MC-108 describes 2 behaviours: powering pistons from a diagonal, and from 2 blocks above, creating a quasi-connectivity behaviour, which is Working as Intended. Your report is describing the second of these, hence being resolved as a duplicate.
migrated
Why you say "from 2 blocks above" ? It's only one block above...
If you see the set of piston on the right and the set of piston on the left have different behavior even if the construction is exactly specular.
migrated
No, its 2 blocks. The block above the piston and the redstone dust count as "2 blocks".
migrated
The block is powered by redstone, so the piston is powered from one block above.
Anyway why the pistons on left are working differently from pistons on right?
The structure is simmetrical and those pistons were working properly in previus versions.
Torabi
While part of the behavior being demonstrated here is MC-108, the actual cause of the problem is MC-11193 - the quasi-connectivity behavior is only causing a problem because of the order in which the redstone and pistons are being updated. Changing the path alters the order in which the redstone is updated, and if a piston is updated, but still being powered due to quasi-connectivity, it won't retract. Try updating the pistons, such as by placing or removing a block next to them. They'll retract as expected.
I couldn't reproduce the isolated case from the first few pictures, but that's probably because the problem is location-dependent. The whole contraption will probably work just fine in certain orientations and at certain coordinates, but will malfunction in others.