DP Int 0 1000

There's no trick here, and that's the point. This node holds one integer, bounded to 0-1000, and outputs it. It exists because ComfyUI's core INT primitive lets you type any number at all - including ones that don't make sense for whatever you're feeding it - and sometimes you just want a value dial that physically can't go out of range.

How it works

You get a single widget, value, with a hard floor of 0 and ceiling of 1000, stepping by 1. Drag it, scroll it, or type a number and it clamps to the range. Wire the output wherever an INT is expected - a batch count, a frame count, a step count, an index into a list, anywhere a bounded whole number makes more sense than ComfyUI's unrestricted default integer widget.

The value in reaching for this over a generic INT primitive isn't functional - it's about self-documenting your graph. When someone else (or you, six months from now) looks at a node capped at 0-1000, the range itself communicates something about what's a sane value for that slot, without needing a note.

Inputs and outputs

One required input:

• value - INT, 0 to 1000, step 1, default 500.

One output:

• value - the same INT, passed through.

How to install it

Search ComfyUI-Desert-Pixel-Nodes in ComfyUI Manager, or:

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

Restart, find it under DP/Utils. No dependencies, no models - it's a primitive widget, functional the instant the pack loads.

Common issues & troubleshooting

You need a value above 1000 or below 0. This node is deliberately bounded - that's its entire feature. If your workflow genuinely needs a larger range, use ComfyUI's built-in INT primitive instead, which has no such ceiling. Don't fight this node's range; it was designed to stop at 1000, not sized wrong by accident.

Nothing seems to happen when you connect it. As with any primitive, the value only matters to whatever's downstream - if the connected input isn't actually reading it (say, it's plugged into a slot that's overridden elsewhere, or the downstream node ignores that input under current settings), the node itself is working fine; the issue is upstream/downstream context, not this node.

Wondering why 0-1000 specifically, and not some other range. No documented reasoning beyond "a common enough bound for the kinds of values people wire into DP's other utility nodes" - treat it as a convenience default rather than a hard rule about what your workflow should use. If 0-1000 happens to bracket whatever you're dialing (a step count, an index, a percentage-times-ten), it's a good fit; if it doesn't, that's the signal to fall back to the unrestricted core INT primitive instead of trying to make this one stretch.

There's genuinely not much more to say about a bounded integer slider - it does one small, honest thing, and the entire value proposition is that it can't be talked into doing anything else.