Bool Value Switch (VantageV2)

Simplest member of the value-switch family, and the one I'd actually use most. It's an if/else that emits a value you chose instead of a wire.

How it works

A BOOLEAN goes in on value. Conditions compare it to True or False using = or != - that's the whole operator set, which for a boolean is honestly enough. Each condition has a name, and once you save the configuration a result field per condition appears on the node body. The first matching condition returns its field's value.

The outcome type is set explicitly in the title-bar dialog: BOOLEAN, INT, FLOAT or STRING. Everything you enter gets converted to that type, so the same two rules can emit 25 and 50 today, or two prompts tomorrow, or true/false if you want to chain it into another logic node.

If nothing matches - which for =/!= over booleans basically means you wrote rules that don't cover one of the two states - the output is None.

The README's own example is the pattern to copy: a condition named Enabled prompt for True, another named Disabled prompt for False, each returning a different STRING. One checkbox at the top of the graph flips which prompt feeds your CLIP encoder.

Why a boolean and not two bypassed nodes

Because bypassing is invisible. Two prompt nodes, one muted, looks identical to two prompt nodes where you meant to mute one but didn't, right up until you read the render. A boolean → value switch makes the decision a wire, which means it shows up in a saved workflow, in a shared graph, and in a screenshot where somebody else is trying to work out what you did.

It's also the natural partner of the pack's Easy Controls node, which emits real BOOLEAN state outputs for its groups. Flip a group off, and a state output can drive the switch, which emits a different prompt or a different CFG. That's how you get a hierarchy toggle that changes content, not just execution.

Prefer this over String Value Switch when the deciding thing is genuinely binary and over Float/Int Value Switch when the input is a checkbox rather than a measurement. There's no cleverness here - it's the smallest useful mapping node in the pack.

Output is one socket, value, typed to your chosen output type. Wire it into anything with a matching input; you'll usually be converting that widget to an input first (right-click → convert), since a bare literal is never an input socket.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/vantagewithai/Vantage-NodesV2.git

Restart ComfyUI, hard-refresh the browser, then search "Bool Value Switch" or browse Vantage/Utils. ComfyUI Manager should also carry it under the pack name Vantage-NodesV2; the clone is the documented route.

Nothing to pip install - no requirements file, no declared dependencies, every import already part of ComfyUI. It does want a recent ComfyUI, because the conditions editor is a title-bar dialog that needs the newer frontend widget APIs. On a stale install you get the node and not the gear, which is a confusing way to fail.

Troubleshooting

None out means neither rule matched - with =/!= on a boolean that usually means someone defined a condition on True only and the value is False. Define both, or use != so one rule covers the other state.

Results arriving in the wrong type is the output_type selector again. int(False) is 0, float(True) is 1.0, and bool("False") is True - that last one is a genuinely nasty conversion, so don't put the word "False" in a STRING field and then wonder why it's truthy.

Changing the output type wipes the result fields and drops incompatible links, so do it before you type your values, not after.

And if a pack update adds fields you can't see, create a new instance - old nodes keep their original schema.