Integer Sequence Modifier

A small, focused utility: build a run of consecutive integers, then output them as one comma-separated string you can feed into anything downstream that wants a list of numbers as text - a batch of seeds to try, frame indices for a video pipeline, or a set of values to drive a loop that a workflow re-triggers.

The three inputs. starting_int (default 0) is where the sequence begins. amount_of_ints (default 5) is how many consecutive integers get included. index shifts which integer in that run the sequence is effectively centered or offset around - with only these three fields exposed and no further documentation on the exact reordering behavior, the safe way to understand index is empirically: run it at a couple of different values with a GR85_ShowText node wired to the output and watch which numbers move where, rather than assuming a specific rotation scheme.

Output. comma_separated_list - a single STRING, e.g. something like "0,1,2,3,4" for the defaults, ready to feed into a text field, split elsewhere in your graph, or log with GR85_SaveTextFile.

Installing it. Search "comfyui_gr85" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/veighnsche/comfyui_gr85

Restart ComfyUI. No models, no extra dependencies - it's integer arithmetic.

Practical use. If you're building a batch where each iteration needs a distinct, predictable integer - driving a filename counter, stepping through frame numbers, or generating a spread of candidate seeds to compare - this gives you that sequence as text in one node rather than wiring together several primitive math nodes to get the same result. Pair it with GR85_IntToString if you need to peel a single value back out for something that wants one integer rather than the whole list, though note that node takes a raw INT, not a string, so you'd need to parse this node's comma-separated output elsewhere before that conversion makes sense - they're not a direct pipeline into each other without something in between to split the string.

Where to be careful. Because the exact effect of index isn't spelled out anywhere public, don't assume behavior you haven't actually verified for your use case - check the output with a text-display node before you wire this into something you're not watching, especially if getting the wrong integer in the sequence would produce a confusing downstream result (a mismatched frame number, a duplicated seed).

This node is also a reasonable case for keeping amount_of_ints small while you're first wiring up a graph - a short sequence is easy to eyeball against expectations in GR85_ShowText, while a long one just gives you more numbers to squint at without making the verification any more reliable.