♾️🌊✨ Six Float Output Widget

The ♾️🌊✨ Six Float Output Widget is a node whose entire job is to not do anything: six float values go in, the same six floats come out, each on its own named socket. No switching, no math, no reordering - a pure pass-through with widgets on the inputs.

So why would anyone add that to a graph? Same reason people add pass-through nodes everywhere: organization and wire hygiene. ComfyUI's canvas fills up fast, and a small box that turns six inline widget values into six labeled float outputs makes a workflow easier to read and easier to rewire. Set your values in one tidy spot, then route each output where it's needed instead of digging through a chain of nodes to find where a float lives. It's also handy when you want values that are typed by hand but still usable as connections - a widget alone can't be wired to two downstream nodes, but an output socket can.

How it works

Six inputs, six outputs, same names on both sides:

• FLOAT1 through FLOAT6 - FLOAT, all default 0, all required.

Outputs: FLOAT1 through FLOAT6, each returning exactly its input value. The implementation is a straight return (float1, float2, float3, float4, float5, float6). If you don't touch any widget, every output is 0.0 - harmless, but don't wire a socket you forgot to set and expect a number.

There's no switch here, no selection logic - the "Six Float Output" name comes from the original code's class name, and the "Widget" in the display name means the values are typed into the node rather than pulled from connectors. You can still override any widget by wiring over it; ComfyUI lets a connection take precedence.

Installing it

Standard pack install:

• ComfyUI Manager → Install Custom Nodes → search "Endless" / "Endless-Nodes".
• Or clone it in:

cd ComfyUI/custom_nodes
git clone https://github.com/tusharbhutt/Endless-Nodes

Restart ComfyUI. No pip dependencies.

The honest caveat

Legacy alert, as with every ESS class: this is from the pre-June-2025 version of the pack, dropped in the author's cleanup, and a fresh install won't ship it - old workflows referencing it may flag it missing. Given that, and given that it's a pure pass-through, the pragmatic take is: if you have it in a working old workflow, fine, leave it be. If you're building new, you don't need this specific node - you can get the same "widget values as wireable outputs" behavior from many maintained nodes, or just type values where you need them. It's a tidy little convenience, not a capability you can't get elsewhere.