Conditioning Switch (JPS)

Conditioning is the encoded form of your prompt - what actually reaches the sampler after CLIP Text Encode has done its work - and once you're maintaining a few different prompt variants (different style presets, a txt2img version versus an inpainting version, an A/B test between two phrasings) you end up needing a clean way to pick which one is live without rewiring the graph each time. That's what this node does: it's a five-way selector for CONDITIONING connections.

Wire up to five conditioning sources into the optional con_1 through con_5 inputs - you can leave any of them unconnected if you're not using all five slots - set the select integer to the slot you want live, and whichever conditioning sits there comes out con_out. It's pure routing: nothing about the conditioning data itself is touched, merged, or blended, it's just a switch deciding which wire actually carries signal downstream.

This is the same "5 to 1" pattern the whole JPS switch family shares - there's a matching one for images, latents, models, VAEs, and ControlNets, all built the same way. The design choice worth knowing about, straight from the pack's own README: these switches were deliberately built to output whichever slot number you selected (not a plain boolean), specifically so they chain cleanly into other JPS switches without needing an extra conversion node in between - some competing switch implementations use a 0/1 boolean instead and need extra math nodes to bridge into anything downstream that expects a different scheme.

Where it fits. The clean use case is prompt-variant testing: build two or three CLIP Text Encode chains for different phrasings or styles, feed them all into this switch, and flip select to compare outputs on the same seed without disconnecting and reconnecting wires each time. It also pairs naturally with Enable Disable Switch (JPS) if you're driving several switches off one central selector value, keeping conditioning, model, and other choices in sync from a single number.

Installing it. ComfyUI Manager, search "JPS Custom Nodes for ComfyUI," or:

cd ComfyUI/custom_nodes
git clone https://github.com/JPS-GER/ComfyUI_JPS-Nodes.git

Restart, and it's under JPS Nodes/Switches. Delete any previous copy of the pack first if you're reinstalling - the author flags this specifically to avoid class-name conflicts between two installs. No models, no heavy dependencies.

Troubleshooting. The gotcha that catches people most often: select has to point at a slot you've actually connected something to. If you wired con_1 and con_4 but left con_2 and con_3 empty, setting select to 3 gets you nothing, not a fallback to the nearest connected input. Match the number to a slot you've populated. If the node disappears from the menu after a ComfyUI update, that's usually a stale install rather than anything wrong with the node itself - reinstalling through Manager typically clears it up.