FloatNumber

FloatNumber is the most honest node in this pack: one slider, one output, no logic. You set a number between 0 and 1, and it hands that number to whatever you wire it into as a FLOAT. It exists because the pack's later workflow JSONs needed a handy way to dial in values like style fidelity, strength, or adapter weights - and on those graphs, a named slider sitting in the node list reads better than digging a value out of a primitive.

The one input

• Number - a FLOAT from 0 to 1, step 0.01, default 0.6. The name is the behavior.

One FLOAT output, equal to whatever you set. The source is literally return (Number,).

When you'd use it

It's a convenience, not a necessity. Any ComfyUI primitive can produce a float; this node is the pack's flavor of that. In practice you'll see it in workflows that need a small set of 0–1 parameters - which is most of the tuning knobs in this pack (style_fidelity, strength, adapter_weight, control_weight, scale, tomesd...). If a loaded workflow references FloatNumber nodes, they're almost certainly carrying those per-run settings so you can tweak one slider without opening widget menus. Wire the output into any FLOAT input on a LCMGenerate* node and it just works.

Setup

It's part of taabata/LCM_Inpaint-Outpaint_Comfy:

cd ComfyUI/custom_nodes
git clone https://github.com/taabata/LCM_Inpaint-Outpaint_Comfy
cd LCM_Inpaint-Outpaint_Comfy
pip install -r requirements.txt

Or ComfyUI Manager, search LCM_Inpaint-Outpaint_Comfy. No models, no dependencies beyond the pack.

Honest take

There's genuinely nothing to say about this node's mechanism, and that's fine - it's a utility widget. Two small caveats: the range is hard-capped at 0–1, so it can't carry a value like cfg = 8 (you'd use a primitive for that), and like everything else in this pack it's 2023-era glue. If you're building a fresh graph, ComfyUI's built-in primitives do the same job; keep FloatNumber in mind mainly for when you're reading or editing an existing pack workflow.