For the double speed of the observer clock, the reason is the following. When you place an oberserver clock "naturally," one observer detects the new block and starts a loop of 2 ticks. That's because there is always one observer waiting for a change. When you move it by piston, both observers start active, and each tick, they see the other one is active and so fire again with no delay. I hope that makes sense
the "pulse shortener" is in fact called a monostable circuit, i'll now warn that the monostable circuit design with the sticky piston uses quasi connectivity, a property that isn't available in bedrock edition
That’s what I was thinking it was, but like I said in the video, I didn’t look anything up and this was all from memory as per the challenge from my fellow server mate. And yes, I should have mentioned that this is a java exclusive thing. Thank you for the input!
it does because when the sticky piston fires, the other observer pulses as soon as the other observer finishes moving, creating a very fast clock. my guess of why it doesn't happen is that when you place two observers manually, both observers change its states at the same time, however observer A is scheduled to pulse before observer B turns off
For the double speed of the observer clock, the reason is the following.
When you place an oberserver clock "naturally," one observer detects the new block and starts a loop of 2 ticks. That's because there is always one observer waiting for a change.
When you move it by piston, both observers start active, and each tick, they see the other one is active and so fire again with no delay.
I hope that makes sense
Yep that makes sense. Thank you!
the "pulse shortener" is in fact called a monostable circuit, i'll now warn that the monostable circuit design with the sticky piston uses quasi connectivity, a property that isn't available in bedrock edition
That’s what I was thinking it was, but like I said in the video, I didn’t look anything up and this was all from memory as per the challenge from my fellow server mate.
And yes, I should have mentioned that this is a java exclusive thing. Thank you for the input!
I know almost nothing about red stone. Feel like you explained things well enough that I can follow along.
Yay! Glad it was easy to follow
@ you did great! Keep it up! 👏
I was not aware that pistons pushing observers together made it go faster
Yep, idk why, but it does
it does because when the sticky piston fires, the other observer pulses as soon as the other observer finishes moving, creating a very fast clock.
my guess of why it doesn't happen is that when you place two observers manually, both observers change its states at the same time, however observer A is scheduled to pulse before observer B turns off
Interesting! I honestly never gave it much thought, I knew it happened and that was about it lol