[MC-55101] Pistons without block attached now update blocks around arm instantly when extending

Pistons take around 3 gameticks to extend. Before the 14w19a update, pistons without a block attached or in front of them, wouldn't cause updates around their arm instantly, but after 3 gameticks. This still works the same way in 14w11b. It seems to occur since the slime block update.

Steps to reproduce:
1 - Build the setup as shown in the picture (with redstone on top of the wool blocks)
2 - Place a redstone torch on top of the redstone block to generate a 1-tick pulse (2 gameticks long).

What should happen or what used to happen:
The bottom piston doesn't extend because it receives an update after 3 gameticks - when its no longer powered.

What actually happens:
The bottom piston extends instantly, at the same time as the other one.

EDIT: The usual update after 1.5 ticks or 3 gameticks also occurs so theres an update at the start and end of the push.

EDIT 06 May 2016:
Fixing this bug would break a huge amount of contraptions at this point and there are no issues with the current behaviour. So resolving this as 'will not fix' would be preferred. Thanks.

Attachments

Comments 16

Dlawso the Really Lucky Rabbit 2014-05-13T00:37:33Z

Possible duplicate of MC-108

kazblox 2014-05-13T02:16:52Z

Is related to MC-108... if this didnt happen before 14w19a but shares the same behavior as MC-108, then it's related.

DicoTheRedstoner 2014-05-13T06:59:36Z

This bug does in no way relate to MC-108. I am saying that pistons now seem to update blocks around their head instantly when extending, unlike before.

Noid Emkay 2014-06-02T01:44:49Z

Dico :O

Noid Emkay 2014-06-02T01:54:20Z

http://imgur.com/RbVDB3m

that creates a 1 tick delay

Your example did not do anything for me.

6 more comments

DicoTheRedstoner 2014-06-02T06:28:02Z

Well, just maybe thats because the torches powers and updates the piston by itself? Your setup is different from mine, you should place the torch on top of the redstone block and you will see that both pistons power, while they wouldn't have before (which was useful)

Noid Emkay 2014-06-03T01:31:50Z

Yeah okay first I missed the redstone, I hope this works:

http://imgur.com/aV908Si

DicoTheRedstoner 2014-06-03T15:39:40Z

Sorry, but you don't seem to know what I'm talking about and/or what this bug is about. Its about updates given by piston arms when extending, not about powering a piston.

kazblox 2014-06-03T21:37:57Z

Just found out that JIIRA has another issue link field called "found while testing". Change the current string, "relates to MC-108", to "found while testing MC-108". That's much better.

DicoTheRedstoner 2014-06-04T07:56:26Z

I just found this while redstoning, so that doesn't actually make any sense whatsoever.

DicoTheRedstoner 2014-06-04T07:58:00Z

I just want to clarify that this is about UPDATES and it has NOTHING to do with diagonal cross connection. It's only used to test the update behavior. I also want to point out that the update of normal piston heads also occurs at the normal time, so theres 2 updates. when the push starts and when it ends.

kazblox 2014-07-09T01:35:57Z

remove the relation please.

galaxy_2alex 2014-11-01T12:25:58Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.

DicoTheRedstoner 2016-05-06T11:43:59Z

I added an edit to the description, at the bottom.

wobst.michael 2016-10-29T20:39:26Z

Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.

DicoTheRedstoner 2016-10-30T16:17:55Z

It is still an issue but it should not be fixed at this point anymore. It would break too many redstone creations. Thus, please close it with the resolution "Won't fix".