PairConditioningSetDefaultCombine_motorway_edition

PairConditioningSetDefaultCombine_motorway_edition is a "motorway edition" clone that handles the trickiest conditioning scenario in advanced workflows: combining your real conditioning with a default fallback, both positive and negative, without any of the conditioning ever leaving the pipe. It reads by key, combines with defaults applied, and writes the pair back by key.

The schema is a wall of key names, so let's untangle it. Required inputs: INPUT_positive_key (default positive), INPUT_negative_key (negative), INPUT_positive_DEFAULT_key (positive_DEFAULT), INPUT_negative_DEFAULT_key (negative_DEFAULT), INPUT_hooks_key (hooks), plus the two outputs OUTPUT_positive_key and OUTPUT_negative_key (both defaulting to positive / negative). And the MOTORWAY in, MOTORWAY out. No widgets - the behavior is entirely driven by which keys hold what.

What does it actually do? It's this pack's version of core ComfyUI's "set default combine" conditioning node, which exists for the "use this unless you have something better" pattern. You keep a known-good default pair (say, a stock positive and a safety-ish negative) in the *_DEFAULT keys, and your working pair in the positive/negative keys. The node combines the working conds with the defaults - the mechanics match the core ConditioningSetDefaultCombine operation - and stores the result back under the output keys. The hooks key is there because core's version applies a model/patch hook bundle to the resulting conditioning; if you're not using hooks, just leave that key pointing at nothing and it's a no-op.

Everything the "edition" suffix implies applies here: the node is part of the pack's experiment that cloned core nodes and rewired complex inputs/outputs to read and write the Motorway by key. That's a neat idea and a fragile one, because the current release of the pack doesn't register these nodes - the activation is commented out in __init__.py, and the release notes call it a hotfix that removed the node-cloning. With a current install you won't see it in the menu; you'd only hit it loading an old workflow or an old pack version. Don't go searching your node list for it and think you installed the pack wrong.

If you do run it, the mechanics are the pack's usual: pull values by key from the hash-addressed Motorway bag, run the underlying combine, write results back by key, clone the bag before handing it on so branches stay isolated. Keys are exact and case-sensitive - a positive_DEFAULT vs positive_default mismatch will throw the family error 'MotorwayClass' object has no attribute 'hash_'.

Install is standard:

cd ComfyUI/custom_nodes
git clone https://github.com/agilly1989/ComfyUI_agilly1989_motorway

restart ComfyUI, or use ComfyUI Manager (search "agilly1989"). No models, no pip deps. And the honest bottom line: this node only exists if you're on a pre-hotfix version, so if the fallback-conditioning pattern matters to you, plan to either pin an old release or replicate it with stock nodes. The idea is sound; the delivery is the part that got parked.