ScatterParamsBatch

This node is the "combine several" step that sits right next to ScatterParams - if that node generates one scatter recipe (how many copies, how big, where, how rotated), ScatterParamsBatch takes multiple of those recipes and merges them into a single SCATTER_PARAMS output. Practically, this is what you'd reach for when you're scattering more than one kind of thing onto a canvas - say, one set of small rotated copies from one source and a second, larger, more upright set from another - and you want both recipes to feed one downstream scatter/composite step as a unit rather than running that step twice.

How it's wired

Two SCATTER_PARAMS inputs are required - scatter_params1 and scatter_params2 - and four more are optional - scatter_params3 through scatter_params6 - so you can combine anywhere from two to six separate scatter recipes in one node. Each of those inputs is exactly what ScatterParams (or another ScatterParamsBatch, if you're nesting) produces. The output is a single SCATTER_PARAMS, the same type going in, which is what lets this chain: you could combine two batches into a third ScatterParamsBatch if you genuinely needed more than six sources, though at that point it's worth asking whether your workflow has gotten more complicated than it needs to be.

The inputs that matter

• scatter_params1 / scatter_params2 - the two required recipes. You need at least this pair to use the node at all.
• scatter_params3–scatter_params6 - optional, wire in as many as you actually have. Leave the rest disconnected.

Output: SCATTER_PARAMS, combining whatever you fed in, headed for whatever scatter/composite node in SP-Nodes actually places images (not part of this batch of node briefs, so I can't walk you through its exact inputs).

Installing SP-Nodes

Through Manager: search "SP-Nodes," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

Restart once it's cloned. Nothing here needs a model or an extra dependency - it's combining a handful of parameter bundles, not doing any image processing itself.

What to watch for

Like ScatterParams itself, this node produces nothing visible on its own - it's plumbing, and the only way to know it's working correctly is to check the result once it reaches whatever actually consumes the combined SCATTER_PARAMS. If you're only using two source recipes, don't bother chasing down what to plug into scatter_params3–scatter_params6 - they're genuinely optional, and leaving them empty is the normal case, not a half-finished setup.

The one thing I can't tell you with confidence, because it isn't documented anywhere in the README: exactly how the combined batch's placements interact when the individual recipes overlap in their x/y ranges - whether copies from different source recipes are allowed to land on top of each other, or whether the consuming node handles collision avoidance across the whole combined set. If your combined scatter looks more crowded or more overlapping than you expected, that's the open question worth testing empirically rather than something these fields let you control directly.