Observer Piston Head Loop
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it). This was fixed in 1.2, perhaps as a side product of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947
Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.
Observed Results:
The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
Screenshots/Videos attached:
Yes
Notes:
This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
Linked Issues
is duplicated by5
MCPE-28595Piston heads treated as solid blocks when passing in front of ObserverDuplicateMCPE-28683Observer Piston LoopDuplicateMCPE-29481Observer Blocks detecting pistons and constantly fire.DuplicateMCPE-29532powering a piston by an observer into it now makes an infinite cycle of powering (destroyes any farm using observers)DuplicateMCPE-40588Difference in observer behavior between PC and Bedrock versionDuplicate
Created Issue:
Observer Piston Head Loop
Verification builds:
1.2.5.15 BetaSummary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.Observed Results:
The piston retracts, but then extends and retracts ad infinitum.Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.Screenshots/Videos attached: Yes
Notes: This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10
- 1.2.5.15
Verification builds:
1.2.5.15 BetaSummary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1.Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.Observed Results:
The piston retracts, but then extends and retracts ad infinitum.Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.Screenshots/Videos attached: Yes
Notes:This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.
*
Observed Results:*The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
*
Screenshots/Videos attached:*Yes
*
Notes:*This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.
*
Observed Results:*The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
*Screenshots/Videos attached:*Yes
*Notes:*This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.
*
Observed Results:*The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
Screenshots/Videos attached:
Yes
Notes:
This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.
*Observed Results:*The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
Screenshots/Videos attached:
Yes
Notes:
This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it).This was fixed in 1.2, perhaps as a side produc of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.Observed Results:
The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
Screenshots/Videos attached:
Yes
Notes:
This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
Verification builds:
1.2.5.15 Beta
Summary:
Prior to 1.2 observers detecting a piston head that it was powering would form a "clock". This was incorrect behavior since observers, normally taking 1 tick to detect and output a signal, would have had it's signal ignored (as the piston head would have been retracting while receiving the pulse, therefore ignoring it). This was fixed in 1.2, perhaps as a side product of the faster observers and the instant chaining observers. It has returned in 1.2.5.15, possibly as a side effect of this bug being fixed:
bugs.mojang.com/browse/MCPE-23947Steps to Reproduce:
1. Build setup as posted in the attached videos.
2. Turn the lever on to "prime" the setup.
3. Turn the lever off.Observed Results:
The piston retracts, but then extends and retracts ad infinitum.
Expected Results:
The piston retracts, ignoring the observer's pulse since it (should) be occurring at the same tick that the piston head is retracting.
Screenshots/Videos attached:
Yes
Notes:
This is a borderline case of bug/game design issue. It seems that to fix this, the observer clock linked in the bug report above must be broken, unless some special exception is made.
is duplicated by
relates to
is duplicated by
is duplicated by
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-28520.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-28520.
Your additional information and observations are very useful, so if you can add them to the comments section of the parent issue it would be appreciated.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
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
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-28520.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-28520.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Thank you for your report!
However, this issue has been closed as Working as Intended..
This has been confirmed as working as intended. If you have a suggestion, please visit the Minecraft Feedback Site or choose a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Is the looping an internal confirmation or did a dev mention it somewhere?
Based on the definition of observer behavior in the wiki, the piston block triggering will update the observer. So if a piston block was in a block observed by the observer, then it would update when the piston expanded or contracted. This 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. Please re-open this case and fix.