[MC-11220] Extending piston causes block update

In previous versions of minecraft extending piston didn't cause block update but now it causes. This breaks compact piston machinery
How to replicate: Place a pistons in a row and give a redstone signal to middle one
What used to happen: only piston given signal would extend
What happens now: adjacend pistons exted too

Related issues

is duplicated by

MC-13349 Turn on one of two vertical Pistons which are back to back = both activate

relates to

MC-108 Droppers, Dispensers and Pistons activate when blocks are providing power diagonally or two blocks above

Attachments

Comments

migrated 2013-03-07T14:41:27Z

[media][media][media]

kumasasa 2013-03-07T19:30:54Z

This is strongly related to MC-108, since powered blocks diagonally over the pistons will extend them.

lemonblock 2013-03-07T19:34:51Z

But before this wasn't happening so something must have changed (previously only one piston extendet) now that piston causes block update and that extends adjancent pistons too

migrated 2013-03-12T18:00:38Z

Confirmed in 1.5pre

migrated 2013-03-12T18:12:00Z

Confirmed.

migrated 2013-03-21T19:48:06Z

I wrote up MC-11957, which was quickly deemed a dupe of MC-108, but in fact it is exactly the bug described here.

In my example, I used buttons to fire the pistons. Rows of pistons above and below a row of buttons. Select a middle button, and one piston above fires. Unfortunately, three pistons BELOW will also fire. This is a big change of behavior.

migrated 2013-07-08T22:32:29Z

Please fix this bug. It is a REAL pain in the neck. We have a world implemented with an extensive rail system and ALL of our rail stations use push-button panels to set the rail switches. The push-buttons are supposed to activate the piston below them, in order to drive the circuitry that sets the rail switches. This has worked flawlessly ever since the official release, but now it is all broken because pushing one button now causes multiple pistons below to fire.

Ezekiel 2014-07-26T18:55:57Z

Is this still a concern in the latest Minecraft version 14w30c? 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 2014-08-08T13:22:37Z

I can confirm that this issue is still a concern with the distributed 1.7.10 client and the 1.7.9 server versions of MineCraft. Beyond that, I am unable to provide any more information at this time because I am currently traveling.

migrated 2015-03-09T23:47:30Z

Confirmed in 1.8.3. Intended. A block was changed, so it creates an update. People are confusing this bug with MC-108. They are actually completely separate bugs, they are just often observed together.