DP Draggable Int 1step

The fine one. A draggable integer that moves in steps of 1, from 0 all the way to 2000. Where the 4-step and 8-step siblings snap to a grid, this one hits every whole number in between - so it's what you use when the exact value matters and "close enough" isn't.

Think step counts, sample counts, any integer where 37 and 38 are genuinely different and you want to land on precisely one of them. Its wide 0–2000 range also makes it a reasonable general-purpose int knob when you don't want the constraint of a stepped selector.

The one input

• value (0–2000, step 1, default 500) - drag or type; it moves one integer at a time.

Output is a single value (INT) that wires into any integer input downstream - a KSampler's steps, a batch size, a loop count, whatever.

Why promote an integer to its own knob

Same reasoning as the draggable floats: the number you actually iterate on shouldn't be buried inside another node's cramped fields. Pull it out to a draggable node where it's easy to grab, and - the part that pays off in a big graph - wire that one output into several places so a single drag updates all of them. One source of truth for a value beats setting the same number in four nodes and forgetting the fourth. That's the whole quality-of-life pitch.

How to install it

ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes

then restart. No models, no dependencies. Under the "DP" utils category.

Common issues & troubleshooting

It outputs an INT, and my target wants a FLOAT. Then use a draggable float node - ComfyUI won't auto-convert an integer into a float input. Match the type to the socket.

I keep overshooting the value I want. Step-1 dragging over a 0–2000 range covers a lot of ground per pixel. Type the number directly into the field for exact values, or if you only ever need multiples of 4 or 8 (dimensions, some frame counts), the 4-step and 8-step variants snap to that grid and are easier to land.

Do I need this for a value I never change? No - a constant can just be typed into the downstream node. This is for the integer you're actively tuning or that feeds several places at once. For a set-and-forget number it's extra nodes for no gain.