SDXL-SUPERMERGER_BLOCKS Components Params
The SuperMerger blocks param node that keeps the old muscle memory
- recipe
SuperMerger - the A1111 extension that kept the merging scene alive for years - organized SDXL block weights in its own layout, and a lot of people still think in that layout today. The SDXL-SUPERMERGER_BLOCKS Components Params node from comfy-mecha is a small gesture of respect to that muscle memory: a param node whose config uses the SuperMerger blocks layout directly.
It's the most pared-down of the family in one sense: it has exactly one input.
blocks- a single float weight for the blocks component.
And it returns a MECHA_RECIPE of per-block weights. Now, one float for "all the blocks" sounds useless at first. The point isn't the single value - it's that this node emits weights in the sdxl-supermerger_blocks config's merge space, which is the native input space for other recipe operations that speak that layout. Think of it as the anchor node when you're mixing SuperMerger-layout recipes into a mecha graph.
How it works
Mechanically it's a standard Components Params node: the float becomes a literal per-key weight restricted to the blocks component of the sdxl-supermerger_blocks config, returned as a MECHA_RECIPE. From there it can flow into a merge method's (delta|param|weight) input. For real per-block control on SDXL you'll usually want the sibling SDXL-SGM Blocks node with its 26 sliders - but if you're bridging in something that already speaks SuperMerger blocks, this is the matching endpoint.
Install
Pack-level: ComfyUI Manager → search "mecha" → Mecha Merge Node Pack, or:
cd ComfyUI/custom_nodes
git clone https://github.com/ljleb/comfy-mecha.git
pip install -r comfy-mecha/requirements.txt
Restart ComfyUI. Only dependency is sd-mecha; nothing to download.
Gotchas
Don't expect a slider grid here - this node's one blocks input is not the place to set 26 block weights. If that's the task, you picked the wrong variant; the SDXL-SGM Blocks node is the one with the full IN/MID/OUT grid. This node earns its keep as a compatibility shim between the SuperMerger layout and mecha's recipe space, and it's fine to skip entirely if you never touch SuperMerger-style recipes.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| blocks | FLOAT | 0.00-18446744073709550000–18446744073709550000 | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| recipe | MECHA_RECIPE | — |