PairConditioningSetProperties_motorway_edition

PairConditioningSetProperties_motorway_edition is the lighter half of this pack's conditioning-property pair: it applies properties to a conditioning pair - mask, hooks, timestep range, strength, area - and writes the modified pair back to the Motorway, without the "combine with existing" step. New conditioning in, restyled conditioning out, both by key.

The schema is mostly key names plus two widgets. Keys: INPUT_positive_NEW_key (positive_NEW), INPUT_negative_NEW_key (negative_NEW) for the conds being modified; INPUT_mask_key (mask), INPUT_hooks_key (hooks), INPUT_timesteps_key (timesteps) for the properties; and OUTPUT_positive_key / OUTPUT_negative_key (defaults positive / negative) for where the results land. Widgets: strength (float, default 1, range 0–10, step 0.01) and set_cond_area (enum, default or mask bounds). This mirrors core ComfyUI's ConditioningSetProperties node, which is the "give conditioning a mask + timestep window + strength" utility that underpins a lot of regional prompting and inpainting-adjacent workflows.

Mechanically, the node pulls the two *_NEW conds out of the Motorway bag by key, applies the mask (masking the conditioning to that region), the timestep range (only active during that part of the sampling), the hooks bundle, and the strength/area widgets, then stores the results under the output keys and hands the cloned Motorway on. In a plain Motorway graph this is how you'd say "take the subject prompt, confine it to the face mask, at full strength, over these timesteps" without dragging mask and conditioning wires across the canvas.

The honest caveat, same as every "edition" node here: the currently released version of the pack doesn't register these nodes. The module that creates them - a clone of core nodes with complex inputs/outputs rewritten as key fields - is commented out in __init__.py, and the release notes call it a hotfix that removed the node-cloning. Current installs won't show this node in the menu; you'd only encounter it in an old workflow or an old pack release. If you're looking for it after installing the latest version, you didn't do anything wrong - it's just not shipped live anymore.

When it does run, the usual pack rules apply: keys are exact and case-sensitive (a timesteps vs Timesteps mismatch throws 'MotorwayClass' object has no attribute 'hash_'), and the bag is cloned at each hop so branches stay isolated.

Install is the pack standard:

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

restart ComfyUI, or ComfyUI Manager → "agilly1989". No models, no pip deps. And the takeaway: this is a genuinely handy idea - property-editing conditioning entirely inside the pipe - that's currently parked in beta limbo. If the pattern appeals, replicate it with core nodes for now and keep an eye on the pack for the day the clone module comes back.