Ard Float

Ard Float is a constant. You type a float into Fx, it outputs that float on float, and nothing else happens. There is no calculation, no conversion, no state - the node's own description says "float variable node," and that's the entire job description. In a graph, this is a labelled source of a number: wire its output anywhere a FLOAT is expected, and you've got a named, visible place to tweak that value instead of digging through widgets on other nodes.

The one input, Fx, spans 0.01 to 999,999 with a step of 0.0001. Note the floor: you can't represent 0 through the widget (min 0.01), though the node itself will happily pass along whatever float it receives - so if you connect a value rather than typing one, the min doesn't clamp you. The output is a plain FLOAT.

Why does this node exist when ComfyUI ships a Primitive node and even a "Float" input? Honest answer: it doesn't strictly need to. It's part of this pack's convention - the author's math nodes (Ard Math) and counters expect floats, the whole workflow style is "named boxes wired everywhere," and a visible constant with a clear label is easier to read than a Primitive's collapsed widget. If you like that style, it's tidy. If you're not invested in the pack's workflow, ComfyUI's Primitive or just the widget on the consuming node does the identical job.

Where you'd actually use it: feeding a denoise value, a scale factor, a CFG number, or any float input that you want to change from one place. Because it has a fixed label on the canvas, it's a decent habit for values you reuse across several wires - one box, many connections, single point of truth.

Honest verdict: this is a genuinely thin utility node, the kind every pack ships because the author needs it internally and it's trivial to expose. No dependency, no bug surface, nothing to troubleshoot - and nothing to get excited about either. Use it if you're following Ardenius' workflow style; otherwise, the built-in nodes cover you. It's one of those "fine, it exists" nodes.

Install is the standard pack route - ComfyUI Manager → search ComfyUI-Ardenius, or:

cd ComfyUI/custom_nodes
git clone https://github.com/ArdeniusAI/ComfyUI-Ardenius

then restart ComfyUI. The pack's requirements.txt installs civitai and moviepy for the pack as a whole - neither is touched by a constant node. If a single import error appears in the console at startup, that's the Save Image node wanting comfyui_controlnet_aux, and it doesn't affect this node.