DD NOR Gate

NOR is the gate for the word "neither." It outputs true only when both of its inputs are false, and false in every other case. If you've ever wanted to say "only do this when none of the blocking conditions are true," this is the gate that says it without you having to string together Not gates and an Or gate.

Two boolean inputs, expression1 and expression2 - and unlike most gates in this pack, both default to false, which is a deliberate hint about how it's meant to be used. One boolean output. The math: not (expression1 or expression2), i.e. "true only if both are false."

Why you'd reach for it

NOR shines for absence conditions - the checks that are about what didn't happen. A genuinely common shape: "no face detected AND no text detected, so this is a plain background - skip the detailer." Each detector feeds you a boolean, NOR outputs true exactly when both say "nothing found," and you route accordingly. Or, guard-style: "only run the watermark pass if neither the source is already watermarked nor the output is going to be cropped." Two negatives that both being absent is the only good case.

It's also the gate that makes your intent legible. You can build the same thing with a Not Gate feeding an Or Gate, but a single NOR gate at a glance tells the next person reading your workflow "this branch runs when neither condition holds." Graphs get read more than written; that's worth something.

Watch the defaults

Both inputs default to false, so a freshly dropped NOR gate outputs true immediately. That's correct for the gate, but it's the exact opposite of, say, the And Gate (which defaults both to true and outputs true). If you leave an input unwired you're silently voting "not true," and NOR treats that as "condition met." Connect both expressions and this stops being a surprise.

Installing

Standard DD-LogicNodes install: ComfyUI Manager → search DD-LogicNodes → Install → restart, or git clone https://github.com/dumbdemon/DD_LogicNodes into ComfyUI/custom_nodes. No dependencies, no model downloads. The one real requirement is a current-enough ComfyUI - the pack targets the newer extension API, so on an old build you just won't find the node in the menu.