Phone : Huawei P9
The redstone delay from an a piece of restone activating till an observer outputs power varies to such a large degree that timing sensitive redstone cuircuits are currently not possible.
Test world attached with 2 rows of 6 double piston extenders - one using redstone ontop of observers to trigger the top piston (A) and one triggering it directly with redstone ontop of the piston (B)
B works every time
A works randomly
Video illustrating issue:
https://youtu.be/etqt07lbPGI
In the test world delete retracted bookshelves and place new ones infront of the haybales to reset ( reset cuircuit is not included to keep the restone to the bare bug )
Linked issues
duplicates 1
Attachments
Comments 16
migrated
@wakafu mafuyuu - even so it should either always fail to pull a block or always pull a block - as shown it does both on the same tick. This is inconsistent - hence the title of the bug report 😉 You can't have reliable circuits if you introduce a random factor
@wakafu mafuyuu - even so it should either always fail to pull a block or always pull a block - as shown it does both on the same tick. This is inconsistent - hence the title of the bug report 😉 You can't have reliable circuits if you introduce a random factor
@wakafu mafuyuu - even so it should either always fail to pull a block or always pull a block - as shown it does both on the same tick. This is inconsistent - hence the title of the bug report 😉 You can't have reliable circuits if you introduce a random factor
@wakafu mafuyuu - even so it should either always fail to pull a block or always pull a block - as shown it does both on the same tick. This is inconsistent - hence the title of the bug report 😉 You can't have reliable circuits if you introduce a random factor
Duplicate of the ever-annoying MCPE-15793.