ConditioningBatch4

Nothing fancy here - this is a tidiness node. ComfyUI's stock ConditioningCombine merges two conditionings, so combining four means chaining three of them together and cluttering your graph. ConditioningBatch4 does the same job - batching multiple conditionings into one - in a single node with four input slots.

This kind of node earns its keep in RES4LYF specifically because the pack leans hard into regional and temporal conditioning - the README's own claim is "unlimited zones," with more than ten used in a single image in their examples. Once you're masking off four separate regions of a canvas and giving each its own prompt, you've already got four conditionings that need to end up as one input to the sampler. A three-node chain of combiners to do that is exactly the kind of graph clutter this node exists to avoid.

How it works

It combines (batches) the conditionings you wire in rather than blending or averaging them. The result is a batch, not an interpolation - if you wanted a weighted blend between conditionings, this isn't that node; look at ConditioningAdd or ConditioningAverageScheduler from the same pack instead.

The inputs and outputs that matter

• conditioning_0 (CONDITIONING) - the only required input.
• conditioning_1, conditioning_2, conditioning_3 (CONDITIONING, all optional) - wire in as many as you actually have; leave the rest unconnected.

Output: conditioning (CONDITIONING), the combined batch, wired into your sampler like any other conditioning.

How to install it

Via ComfyUI Manager, search "RES4LYF". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

then restart.

Common issues & troubleshooting

You don't need to fill every slot. Only conditioning_0 is required - if you only have two or three conditionings to combine, leave the rest of the inputs disconnected rather than hunting for something to plug into them.

This combines, it doesn't blend. If your goal was a weighted mix between conditionings rather than a batch of separate ones, this node will technically run without error but won't give you what you're after - reach for ConditioningAdd (layer one onto another at a strength) or the stock ConditioningAverage instead.

Got more than four conditionings to combine? Use ConditioningBatch8 instead of chaining two ConditioningBatch4 nodes together - same pack, same behavior, just more slots.

Order matters if your downstream regional-conditioning setup cares about it. Some regional conditioning approaches associate each conditioning in a batch with a specific mask or zone by position - if your zones end up scrambled after combining, check that you wired conditioning_0 through conditioning_3 in the same order your masks expect, rather than assuming the batch node reordered something.