IO Sampler Settings v2.3 (Legacy)

Pipe IO Sampler Settings v2.3 [Eclipse] is the last of the legacy sampler IO nodes, and the one change it carries is a single boolean. v2.2 gave you prompt_seed; v2.3 gives you allow_overwrite as an input you can actually wire, rather than a flag you hope arrived inside the pipe.

Deprecated, still loadable, superseded by the pack's current IO Sampler Settings node.

What the switch does

Every channel in this node comes from one of two places: the incoming pipe, or the individual input socket. Something has to break the tie, and allow_overwrite decides which side wins.

• true - your direct inputs take priority. Values already in the pipe are overridden by whatever you wired in. This is how you keep one shared settings pipe and bend two or three values for a variation pass without rebuilding the pipe.
• false - the pipe wins. Direct inputs only fill channels the pipe left empty.
• Unconnected - the node falls back to the _allow_overwrite value already inside the pipe, and to false if there isn't one.

The flag is also written back into the outgoing pipe, so the decision propagates: a node downstream sees the same policy you set here, and you don't have to repeat yourself on every hop. It's an input-only boolean (a socket, not a checkbox), so wire it to a Boolean node or a primitive rather than expecting a widget.

The channels

Identical to v2.2: pipe, then steps, cfg, sampler_name, scheduler, guidance, denoise, sigmas_denoise, noise_strength, upscale_steps, upscale_denoise, upscale_value, seed and prompt_seed. All optional. The numeric ones are forced inputs so they appear as sockets; sampler_name and scheduler are untyped (*) and pass whatever you connect straight through.

The full output set mirrors the inputs, plus the pipe. The separate upscale_steps/upscale_denoise pair is the legacy signature: the current node kept only the single upscale_value, which is precisely why graphs with a distinct second-pass upscale still reach for v2.3.

Between them, seed and prompt_seed give you the render seed and the pick/expand seed as separate channels - same split v2.2 introduced.

Install

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

Or ComfyUI Manager → ComfyUI_Eclipse → restart. Category: 🌒 Eclipse/ Legacy.

Nothing in the dependency list is specific to these nodes - the pack's requirements.txt (torch, numpy, Pillow, opencv-python, safetensors, pilgram, PyYAML, aiohttp, plus some heavier audio pins) is aimed at the image and audio nodes. If Eclipse loads, this loads.

Watch out for

The node always writes the full channel set into the outgoing pipe, including channels where neither input nor pipe supplied anything. So a pipe that goes in with denoise missing comes out with denoise present-but-empty rather than absent, and a consumer that doesn't check can take that as a real value. Feed it a populated pipe or fill the channels you care about - that's the whole habit the pipe ecosystem asks of you, and it's the same one the modern node wants.

And the standing advice for all three legacy variants: they exist because saved workflows store socket order, and each version keeps its original indices so old links don't land on the wrong channel. For anything new, use the current IO Sampler Settings node; for old graphs, use the Workflow Migration Tool (as a node or via python tools/migrate_workflow.py, backups included) and stop maintaining three versions of the same settings by hand.