I have a very simple spigot mechanism in place. To the right inlet an [==] object is connected. It sends out a 1 when it receives a 3, and otherwise a 0. To the left input of the spigot is connected a number box that receives input every time the [==] is triggered. The problem is that the spigot refuses to work correctly when the patch is running. It keeps letting numbers through when [==] is outputting a 0. The only thing I can think of that might be the problem is that [==] and the number box are receiving their inputs at different times, so that the spigot is sometimes open for a number when it should be closed. However, I went to fairly ridiculous lengths to ensure that the two inputs are arriving at the same moment, even though it shouldn't have been necessary. And yes, the number box was connected to the spigot after [==]. I checked multiple times. So what on earth is the problem?

@Polaris could you post the patch in question?
This should be enough to get it to work:

Thank you for posting in my topic.

The setup that you posted is unfortunately not one that I can use, because the [==] and the spigot's left inlet are supposed to receive two different numbers.

I would probably post the patch, but it looks like the work of a tornado, so I don't think anyone would want to try making sense of it. I guess I'll post it anyway. The problem appears to be located in [pd all match]. The patch is triggered by its user pressing the topmost bang on the main page.

@Polaris This should do it:

Alternative:

@ingox

I tried the second, simpler setup, and so far, all of its output is what I was I trying to get. So it looks like you found a solution. Thank you.