No, but fooling around with the delay line is one way to implement single-step or really slow step. So either your next clock pulse is when a humanoid hits a b

No, but fooling around with the delay line is one way to implement single-step or really slow step. So either your next clock pulse is when a humanoid hits a button or when a delay line times out. Can't just gate in a clock using a "AND" because of jitter and syncing is more trouble than its worth. I never worked on this model so this is just semi-educated guess.