basicIn_float

This is one of the plainest nodes in the whole pack, and worth knowing about mostly because of one small quirk: unlike ComfyUI's native float primitive, which is a slider/spinner widget with a min, a max, and a step, this node's field is a bare text box. You type a number in as a string and it comes out the other side as a FLOAT. That's a deliberate design choice in this pack's IO_Port family - no clamping, no step size fighting you when you want an oddly specific value like 0.037.

What it does

One input, input, typed as a single-line STRING and defaulting to empty. One output, float, typed FLOAT. Whatever you type gets parsed into a float when the graph runs. That's the entire node - a raw entry point for a numeric value you want to reuse somewhere else in an Apt_Preset workflow, without a slider's range restricting what you can type.

Where it fits

This pack leans hard on a "set it once, wire it everywhere" pattern for its IO_Port nodes - basicIn_Sampler, basicIn_Seed, and this one all exist so a value lives in exactly one place in your graph instead of being retyped into every node that needs it. If you've got a strength, a weight, or a threshold that three different downstream nodes all need to agree on, put it here once and fan the output out to all three, rather than typing 0.75 into three separate widgets and hoping you don't fat-finger one of them differently.

Installing it

Search "ComfyUI-Apt_Preset" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

Run install.bat on Windows (pip install -r requirements.txt on Linux/Mac), restart ComfyUI. Nothing to download - it's a bare value primitive.

Common issues

The one thing to actually watch for: because the field is a text box rather than a numeric widget, ComfyUI won't stop you from typing something that isn't a valid float - a stray letter, a trailing comma pasted in from somewhere else, an empty string left at the default. Any of those will fail to parse at execution time rather than being caught while you're editing, so if a run errors out on this node specifically, that's the first thing to check. It's a trade-off: you get the freedom to type any precise value with no slider clamping it, and in exchange you lose the "this literally cannot be an invalid number" guarantee a proper numeric widget gives you for free. If you want that safety back and don't need sub-slider precision, this pack's basicIn_int uses a real numeric widget instead - worth reaching for when you don't specifically need fractional freedom.