Float Variable

Same idea as this pack's Integer Variable, just typed for decimals. The problem it solves is specific and real: ComfyUI's built-in Primitive node can't link certain paired widgets together - the README's example is start_at_step on one KSampler and steps on another, which you'd naturally want kept in sync but can't connect directly. Float Variable is the fix: one node holding a single float value, with an output you wire to every place that needs to agree on that number.

How it works

It's deliberately unfussy. There's no math, no range mapping, nothing computed - you set a decimal value on the widget, and the node exposes it as a FLOAT output. Anywhere that output goes, you're guaranteed the exact same value, because there's only one place it's actually set. This matters most for things like denoise strengths, CFG values, or LoRA weights you want two different parts of a graph to share without maintaining two copies by hand.

The input and output

value is the sole input, a float defaulting to 0. FLOAT is the sole output. If you've used rgthree-comfy's more general graph-plumbing tools before, think of this as the narrow, single-purpose sibling of something like its Power Puter - it doesn't evaluate expressions or handle arbitrary types, it just holds one number and lets you fan it out.

Installing the pack

• ComfyUI Manager - search "ComfyUI-N-Nodes," install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/Nuked88/ComfyUI-N-Nodes.git, then restart ComfyUI.

Nothing to configure beyond that - no models, no GPU dependency, no setup step specific to this node.

Common issues & troubleshooting

Not sure you actually need this over a regular widget. Test the direct link first. If ComfyUI's stock Primitive node lets you connect the two widgets you care about, skip this entirely - it only pays off in the specific cases core ComfyUI can't handle, like matching settings across two separate sampler nodes.

Value seems to only be honored in one of the two places you wired it. Check both downstream connections carefully - it's an easy mistake to leave one consumer still pointed at its own local widget instead of this node's output, in which case only the other one actually reflects your change. The whole point only works if every place that needs the shared value is pulling from this single node.

Need an integer or a string instead. This pack also ships Integer Variable and String Variable for exactly that - same pattern, different type, no generic "any type" version.