Observer block outputs single game tick pulse, not single redstone tick pulse

May be intentional, PE and PC Edition are seperate and don't necessarily have the exact same features.

Interesting note: because of how short the observer pulse is in Java edition, you can't invert a redstone torch with its signal, whereas in MCPE you can. (You can try this by placing a repeater, then a block, and then a redstone torch on the block on the output side of an observer, and then activating the observer. The redstone torch will invert in MCPE, but not in the Java edition.)

Observers do give out 2gt pulses in most cases. The exceptions are observers that are updated by blocks events (block pushed in front of observers) or observers, that are activated by player inputs. This behaviour is similar to other redstone components (pistons). I don't see a reason to fix this, because it would require a rewrite of the order in which things are processed, which in turn would break countless things.

I also don't see a downside of observers giving 1gt signals in some cases. It's a useful tool, if used correctly and doesn't add confusion for people, that don't know about (see pistons, where exactly the same happens)

The title of this bug post is used in the description of the 16w41a snapshot. The problem is that in 16w41a the actual delay is 4 gticks and not just 2 (as the title says). Is that intended?

@unknown From my recent observations (pun sort-of intended), it seems that MCPE observers also output a 2 rtick or 4 gtick pulse. Maybe. There are a couple of weird timing bugs in MCPE that may be interfering with my tests, but if this is the case, then the Java edition observer behavior may be intentional. Or both could be bugged and are both supposed to have just a 1ritck pulse. From what the devs have said, the Java edition observers are intended to work like the MCPE observers, unless the MCPE observer behavior is marked as a bug. And as for this... well, I'm not sure. 😛

See MC-108697.