I have created this model on the community realm, so you can check it out. Co-ords 253, 113, 76
Basically an observer triggering a T-Flipflop circuit. The T-FlipFlop is build of 3 droppers and one hopper (classic design) .
The observer is set to watch sugarcane growing beneath it. Facing down and strongly powering the dropper above it.
The output of the dropper at the rear is taken via comparator to power a sticky piston to break the sugarcane.
On single player this works ok most of the time. On a realm the observer appears to be triggering the T-FlipFlop twice per observer pulse resulting in the creation of an oscillator/clock action. This should not happen.
On single player if you place a second observer on the side of the first observer (output facing away from contraption) the Oscillations run a what looks like 1 tick.
On single player if you place a second observer on the side of the contraption this time observing the Comparator, Oscillations will happen at a 3 tick rate.
Non of these behaviours should occur.
PS a dedicated realm for these demonstrations would help enormously and save you the time of trying to repo these issues yourselves.
Attachments
Comments 2
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Your contraption does not have a well-defined behavior, so those kinds of unreliability is basically impossible to avoid. Let me explain why:
The 3-dropper TFF, a variant of Grizdale's TFF, depends on the ticking order in droppers and therefore it is unreliable. The observer is strongly powering one of the 3 droppers, which also activates two other ones at exactly the same tick, so there are 3! = 6 possible ways to tick them. The Bedrock code base, unlike Java, randomly chooses the order in such cases which leads to an indeterminate result.
Also note that the observer is triggered 3 times for each growth of sugar cane, and you expect your contraption to ignore exactly 1 of them. This is also a source of timing issues and thus should be avoided, unless you have a perfectly clear view of event occurrence timings. The observer triggers:
when the sugar cane grows and touches the observer.
when the observed block turns into a piston head, i.e. the piston extends.
when the observed block turns into an air block, i.e. the piston retracts.