MCPE-24680inconsistent observer
Hello, an interesting change was done in beta-1-2-build-1, as it's written in the change-log : "Observer blocks no longer pulse twice when observing a retracting piston".
But, the result can be random and inconsistent, for example with the redstone build pic, the result is a kind of "random clock" stopping after 1 pulse or 3 or 5, etc... it's very unpredictable.
If you want more details about this inconsistent observer, I've done 2 minutes of video (and sorry for my french accent) here .
Linked Issues
Attachments1
Created Issue:
inconsistent observer
Hello, an interesting change was done in beta-1-2-build-1, as it's written in the change-log : "Observer blocks no longer pulse twice when observing a retracting piston".
But, the result can be random and inconsistent, for example with the redstone build pic, the result is a kind of "random clock" stopping after 1 pulse or 3 or 5, etc... it's very unpredictable.
If you want more details about more inconsistent redstone builds, I've done 2 minutes of video (and sorry for my french accent) here .
Attachments1
Hello, an interesting change was done in beta-1-2-build-1, as it's written in the change-log : "Observer blocks no longer pulse twice when observing a retracting piston".
But, the result can be random and inconsistent, for example with the redstone build pic, the result is a kind of "random clock" stopping after 1 pulse or 3 or 5, etc... it's very unpredictable.
If you want more details about
moreinconsistentredstone builds, I've done 2 minutes of video (and sorry for my french accent) here .Hello, an interesting change was done in beta-1-2-build-1, as it's written in the change-log : "Observer blocks no longer pulse twice when observing a retracting piston".
But, the result can be random and inconsistent, for example with the redstone build pic, the result is a kind of "random clock" stopping after 1 pulse or 3 or 5, etc... it's very unpredictable.
If you want more details about this inconsistent observer, I've done 2 minutes of video (and sorry for my french accent) here .
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
The issue with your example is that redstone devices are ticked randomly, not in order of propagation like Java. As of now it is a feature and unrelated to the observer itself.
The randomness of which piston extends is intentional. The redstone update order for simultaneously-activated blocks is intentionally random in Bedrock, unlike the sort-of-deterministic update order in Java Edition.
Interestingly enough the randomness itself does not seem to be intended, at least not permanently. The devs themselves have mentioned that the random order is only to prevent players growing accustomed to a broken system until they can establish a proper order method.