NEEDS TO BE ADDED!!! Observer blocks are not detecting other observer blocks changing states. It makes sense that an observer block would detect that another observer block has detected something and changed to its "activated" state for a moment. In fact, this is a concept I have used heavily in Java Edition for many different machines. Especially a very useful and fast clock that is created in Java Edition by pushing an observer block into position with a piston so that it is face to face with another observer - two outputs that are very fast, created by the fact that the one observer sees the other observer get placed in front of it, and then the one that got pushed sees the other one change state, and it goes back and forth infinitely.