Int List
An integer list that edits like a spreadsheet, not a JSON blob
- int list
- count
The sibling of the pack's Double List, but for integers - and honestly the more useful of the two, because integer lists show up everywhere in ComfyUI. Seeds, step counts, upscale factors, batch indices, denoise-pass numbers: HYBS_IntList gives you a clickable list editor for them, starts you at [1], and hands you a clean LIST of ints when you're done.
It exists for the same reason its float sibling does: in a node graph, lists are usually either hard-coded JSON or the output of some convoluted generator. This is the "just type the numbers, one per row" option, which sounds trivial until you've edited a [512, 640, 768] array by hand one too many times.
How it works
One socketless input, selection, holding the widget's internal JSON state - you interact with the rows, the widget serializes, the backend parses. Rows are coerced to integers; anything that doesn't parse is skipped, so the output can't carry a stray string. Outputs:
- int list (
LIST) - the integer values - count (
INT) - how many rows you have
The backend validates that the list isn't empty - a zero-length list would silently do nothing downstream, so the node refuses to run one. The search_aliases in the schema include "seed list," a hint that one of the intended uses is a fixed seed list for reproducible batch runs (contrast with the pack's Seed List Generator, which is random-per-run).
Installation
Standard pack install:
cd path/to/ComfyUI/custom_nodes
git clone https://github.com/hybskgks28275/ComfyUI-hybs-nodes.git
pip install -r ComfyUI-hybs-nodes/requirements.txt
Or "ComfyUI-hybs-nodes" in ComfyUI Manager, then restart. No models, no deps beyond the pack's (unrelated) toml requirement.
This is a utility node through and through - it adds no generation capability, it just makes list-editing tolerable. You'll reach for it in batch/iteration workflows where the list of integers is a parameter you change between runs, paired with whatever iterates over the LIST output. If your workflows don't iterate yet, it'll sit unused; if they do, it'll quietly become one of the nodes you don't think about, which is the highest compliment a utility node can earn.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| selection | STRING | [1] | Internal integer list state managed by the frontend widget. |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| int list | LIST | Editable integer values. |
| count | INT | Number of list entries. |