Range Float (Mikey)

The README's own description of this one is a single line - "generate numbers from a given range using the seed offset" - and that's genuinely the whole idea. Define a range with a start, an end, and a step size, then let ComfyUI's own seed-increment mechanism walk you through it, one queued run at a time.

How it works

You set start, end, and step as the boundaries and granularity of your range, and seed picks which value inside that range comes out. This pack reuses "seed" as a general index selector in several of its utility nodes, not just here - it's the same pattern behind Range Integer and Load Image Based on Number. The practical upshot: set ComfyUI's seed control widget on this node to "increment" instead of "fixed," and every time you hit queue, you get the next value further along your range - a cheap, no-code way to sweep a parameter across a batch of runs without wiring up anything more elaborate.

The inputs and outputs that matter

• start and end (FLOAT, step 0.0001) - the boundaries of your range.
• step (FLOAT, step 0.0001) - the granularity between values inside that range.
• seed (INT) - which value in the range comes out this run. Fixed gives you the same value every time; incrementing walks the range.
• FLOAT (output) - the selected value, ready to plug into anything expecting a float - a CFG value, a denoise strength, an upscale_by, whatever you're sweeping.
• STRING (output) - the same value as text, so you can drop it straight into a filename or caption without a separate conversion node.

How to install it

Bundled with the rest of Mikey Nodes. ComfyUI Manager: search "Mikey Nodes," install, restart. Manually:

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

then restart. No models, no extra dependencies.

Common issues & troubleshooting

Seed set to "fixed" and you're not seeing the range move. This is the single most likely reason the node feels like it's "not working" - it's not sweeping anything on its own; ComfyUI's seed widget has to actually be set to increment (or randomize, if you want a different kind of variety) for successive queued runs to land on different values. Check the widget mode, not the node.

Values running past end. With no documented wraparound behavior, don't assume the node clamps or loops once the seed pushes it past the range boundary - treat end as informational for how far you intend to sweep, and keep an eye on the actual output value if you're running a long batch, rather than assuming it stops itself.

Step too coarse or too fine for what you expected. Since step has four decimal places of precision available, it's easy to fat-finger an extra zero. If your sweep is landing on far fewer or far more distinct values than you meant, that's the field to double-check first.

Wanted whole numbers instead. This node is float-only. For integer sweeps - batch sizes, step counts, seeds for a different node entirely - reach for Range Integer instead; same design, integer values.