🎯 VRGDG Trigger Counter

VRGDG_TriggerCounter is the pack's little index-advancer: you feed it a seed, and it hands you an index that moves forward each time the workflow runs. It's one of those unglamorous control nodes that makes the bigger VRGDG music-video pipeline work, because a long music video is really a loop of many short scenes, and each loop pass needs to know which scene it's on.

That's the whole mechanism. One INT in, one INT out. The seed just gives you a deterministic starting point - same seed, same sequence, which is exactly what you want when you're iterating on scene 12 and don't want to re-roll scenes 1 through 11. Wire the index output into something that selects a scene or a prompt (the pack's own VRGDG_PromptSpitterWithIndex is the natural partner, and it's what the "unlimited length" workflows use), queue the graph repeatedly, and each run advances.

Why you'd bother

If you've ever generated a multi-scene video in ComfyUI, you know the pain this removes: manually changing an index or a prompt between runs, or babysitting a queue. A counter that ticks on every execution means you can set a seed, queue up 40 passes, and walk through 40 scene prompts in order. It's a small node that quietly deletes a lot of tedious clicking, and it's a pattern worth stealing even if you never touch the rest of the pack.

The catch with any stateful node like this is the same one: "advances on each run" only works if the workflow actually runs the counter each pass. Bypass it, or run a sub-graph that doesn't include it, and your index stops advancing while you think it's still ticking. Keep it in the main execution path and it behaves.

Getting it

It ships in the VRGDG pack:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

or ComfyUI Manager → search "vrgamedev". Restart after install. The pack's dependencies are kornia, librosa, and imageio - mostly irrelevant to this node, but Manager should handle them anyway.

It's not a model node, so there's nothing to download and nothing to tune beyond the seed. If the node ever feels like magic, remember it's just an integer that goes up by one. The value isn't the math, it's that the surrounding workflow is built to listen to it.