-
Bug
-
Resolution: Awaiting Response
-
None
-
20w15a
-
None
-
Unconfirmed
-
(Unassigned)
When an observer gets pulled back from an observer pulse, it creates a really short pulse. The pulse is too short/fast for a piston to detect, as well as for a fence gate to change animation. In the attached video I show how it should react with the use of a button (that is nothing happens). Then what happens when the observer pulse is used (a pulse is created). My assumption is that the observer being moved detects the piston head and as it is trying to send a pulse is moved. But then why does it not apply to the button pulse? Whatever the case may be, there is definitely an inconsistency that needs to be addressed.
Note: I could have this backwards and maybe the button should create a pulse.
Note 2: The pulse is also not created from a standard on/off of the piston (i.e. regular button press, lever flip, etc.) ONLY from the observer pulse.