FL Float

As basic as this pack gets: a single float value, 0 to 1, rounded to two decimal places, with a widget you can drag or type into. It exists because sometimes you just need a properly-typed FLOAT constant to feed into a node that won't take a raw number typed directly into its own socket, or because you want one value driving several downstream nodes from a single place you tweak once.

Why bother with a node for this

Two reasons. First, if the same value needs to drive multiple places - say, the same blend strength for an image mix and a mask feather elsewhere in the graph - wiring one FL_Float into both means you adjust it once instead of hunting down two separate widgets that are supposed to stay in sync. Second, some custom nodes only expose a FLOAT input socket with no editable widget of their own, expecting the value to arrive from a connection rather than a typed field - piping a constant through FL_Float is the simplest way to hand them a static number when they insist on getting it that way.

It's one of a small cluster of "glue" utility nodes this pack ships for wiring numeric values around a graph without dropping into a Python node - FL_FloatToInt, FL_IntToFloat, and FL_Math are its siblings.

Inputs and outputs that matter

value (0-1, default 0.5, step 0.01) is the entire node. Output is value as a proper FLOAT - wire it wherever a workflow expects one: denoise strength, a blend or opacity slider, a LoRA weight, anything typed FLOAT rather than accepting its own widget. The 0.01 step is fine-grained enough for most of those uses without needing to scroll through a huge range to land on, say, 0.65 exactly.

Installing it

ComfyUI Manager: search Fill-Nodes, install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/filliptm/ComfyUI_Fill-Nodes, then restart. No dependencies for this one at all - it's pure ComfyUI.

Where people get burned

The range is fixed at 0-1. If you need a float outside that - a CFG scale up around 7-15, say, or a negative value - this node's range doesn't stretch to cover it; look at FL_FloatToInt/FL_IntToFloat for conversion needs or a different value node entirely if you need something wider. Otherwise there's not much to trip over here - it's a constant, not a computation, and there's no async call, no cache, no failure mode beyond forgetting you left it wired to the wrong socket after copy-pasting a chunk of graph.