Ways to Recreate It:
-Put an Observer and then a Piston (Normal or Sticky) on his side.
-Connect the Observer and the Piston.
-Activate the Observer (Just update the Observer with a block).
I don't think that is supposed to work that way.
Linked issues
relates to 1
Attachments
Comments 15
migrated
This is intended. The observer detects block updates and the piston activating causes an update, same with it retracting so it creates a second pulse causing the loop. Here is a way to prevent the loop.
[media]This is intended. The observer detects block updates and the piston activating causes an update, same with it retracting so it creates a second pulse causing the loop. Here is a way to prevent the loop.
[media]Oh, I thought that the Piston extended itself did not count as a block updade, I thinked that was an entity, my apologies.
This had been fixed in 1.2 with the instant observers. As of 1.2.5 Beta 3 (1.2.5.15) observers have been slowed down (from the changelog, it seems it was to fix MCPE-23947) and this issue is occurring again.
This had been fixed in 1.2 with the instant observers. As of 1.2.5 Beta 3 (1.2.5.15) observers have been slowed down (from the changelog, it seems it was to fix MCPE-23947) and this issue is occurring again.
This had been fixed in 1.2 with the instant observers. As of 1.2.5 Beta 3 (1.2.5.15) observers have been slowed down (from the changelog, it seems it was to fix MCPE-23947) and this issue is occurring again.
This had been fixed in 1.2 with the instant observers. As of 1.2.5 Beta 3 (1.2.5.15) observers have been slowed down (from the changelog, it seems it was to fix MCPE-23947) and this issue is occurring again.