SR Float Prompt Input (Mikey)

Don't overthink this one - it does exactly what the schema says and nothing more. One input_float widget in, one FLOAT output out. No math, no clamping, no range limits defined. It exists purely to give a floating-point value its own named wire in your graph.

Why that's useful at all

The "SR" prefix (shared with SRIntPromptInput and SRStringPromptInput) points at the pack's Search-And-Replace / placeholder system. The pattern these three nodes fit is a common one in bigger ComfyUI graphs: instead of hardcoding a number into a dozen different nodes across your workflow, you park it once in an SRFloatPromptInput, give the node a clear title so you can find it later, and route its output wherever that value needs to go. If you're driving a placeholder-based prompt template through this pack's text-processing nodes and one of the placeholders needs to resolve to a float - a strength, a denoise value, a ratio - this is the node that gets it into the graph as a typed value rather than as text you'd have to parse back out.

It also plays nicely as a "single source of truth" input: rename the node, put it up top of your workflow near your other exposed controls, and anyone opening the graph later (including future you) can see at a glance which numbers are meant to be tweaked.

The one input, the one output

• input_float - the value itself. No default is defined in the schema, so ComfyUI will hand you its own numeric widget default; set it explicitly rather than relying on that.

Output is a single FLOAT, named the same as the type. Wire it into anything that takes a float - a KSampler's denoise, a LoRA strength, a custom node's numeric input.

Installing it

Through ComfyUI Manager (search "Mikey Nodes"), or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bash-j/mikey_nodes

Restart ComfyUI after either. This node has no dependencies of its own - it's a thin wrapper, so there's nothing to download or configure beyond having the pack installed.

Troubleshooting

There's genuinely not much that goes wrong here - it's a passthrough. If you're not seeing the value you expect downstream, the almost-always cause is that you edited the widget on a different instance of the node than the one actually wired into your graph (easy to do after a copy-paste), or you're looking at a saved workflow where the value got reset to whatever the schema's blank default resolves to. Check the node you're actually looking at is the one with a live connection, and you'll usually find it.

If what you actually wanted was a node that computes something from two floats rather than just holding one, this pack also ships EvalFloats - that's the one for expressions, not this one.