MCPE-28683Observer Piston Loop
Based on the definition of observer behavior in the wiki, the actual piston block will trigger an update on the observer. So if a piston block was in a block space observed by the observer, then it would update when the piston expanded or contracted.
This behavior does not apply to the piston head movement as quoted from the Wiki "A piston (not the head) extending or contracting" triggers redstone signal from the observer.
This is not the current behavior as of 1.2.5.15 - i.e. it is broken, according to your own documentation in the wiki. Re-creating this issue because it was closed as "working as intended", which is not the case based on the Wiki.
Linked Issues
Created Issue:
Observer Piston Loop
Based on the definition of observer behavior in the wiki, the actual piston block will trigger an update on the observer. So if a piston block was in a block space observed by the observer, then it would update when the piston expanded or contracted.
This behavior does not apply to the piston head movement as quoted from the Wiki "A piston (not the head) extending or contracting" triggers redstone signal from the observer.
This is not the current behavior as of 1.2.5.15 - i.e. it is broken, according to your own documentation in the wiki. Re-creating this issue because it was closed as "working as intended", which is not the case based on the Wiki.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
duplicates
first off - The wiki is user editable, thus it's not gospel.
secondly the line "A piston (not the head) extending or contracting" means - "an observer looking at the piston body, as opposed to the piston head"
The piston head is covered by "All other block / block state changes"
as the block the observer was observer has been replaced by a piston head and then at the retraction replaced by either air ( normal piston ) or the old block ( sticky piston ) - that's 2 "all other block changes" both detected.
Hope this helps
Whenever I have challenged Minecraft "behaviors" or the like, I am pointed to the Wiki. Whether it is user-editable or not, if Minecraft representatives are going to use it as their rule book, then it works both ways.
The piston head is actually not a block, and I disagree that the "All other block / block state changes" Wiki entry actually applies. If a mob moves into a block, it does not trigger the observer. The piston head isn't any different. It's a temporary intrusion and should be treated as such. When sugarcane grows into the block it is there for a longer period of time to potentially always there. The piston is passing through, so to speak, and should not be treated the same way.
Besides, if the piston head is moving into a block that already has an object in it, then it should not re-trigger the observer as the state of the block is not changing from empty to full. It's going from full to full. It's not until the piston head has left the block that a change of state actually takes place, whether its changing the state of a block like sugarcane, or moving a block out of the current clock.
Ultimately, the behavior I am describing just makes the Observer a better feature of Minecraft. It makes for much simpler devices that are simply not possible with the changed behavior in the latest release. It is extremely frustrating having to rebuild every time someone at Minecraft decides its easier to fix other problems by changing behaviors in something else.
Thank you for your report!
However, this issue has been closed as a Duplicate of
MCPE-28520.If you wish to make a suggestion, please use the feedback site.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki