VRGDG_PromptSplitter_General

Most of VRGameDevGirl's splitter nodes are fixed-output affairs with a dozen or sixteen ports wired to a specific workflow section. VRGDG_PromptSplitter_General is the exception that proves the rule: a JSON array in, an index in, and exactly one text output out. It's the version of the family that drops into whatever you're building, because it doesn't assume how many slots you need - it just hands you the scene you asked for.

If you're adapting these nodes to a workflow of your own, this is the one to reach for. The sixteen-port variants exist because the pack's sections consume that many parameters per scene; your graph probably doesn't, and one output means you wire it wherever a single STRING goes.

How it works

Two required inputs:

• json_string - a JSON array of scene entries as text (defaults to []). Element N is scene N.
• index - which scene to pull, 0 to 10000, zero-based.

Outputs: a single text_output STRING - the selected scene's entry. From there, wire it into a text encoder, a prompt node, or a format node that expands it into whatever your downstream needs.

Why you'd use it over the others

The fixed-count splitters are optimized for the pack's own graphs - readable wiring at the cost of flexibility. The General splitter trades that visual tidiness for composability: since it emits one clean string, you can chain it into almost anything. Need the scene as a comma-separated prompt? Wire the output into a text format node. Need it per-line? Do the same. It's the splitter that doesn't dictate your downstream shape.

Gotchas

Same index rules as the rest of the family: zero-based, and the node reads whatever is in json_string at run time, so refresh the input if you edited the map. And remember it expects an array - [] - not a keyed object; if you feed it a {}-style prompt map it won't find elements by key.

Installing it

Part of the pack:

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

restart, or ComfyUI Manager → search vrgamedev. No models, no heavy dependencies - pure JSON selection.

The honest take

Of all ten splitters in this pack, this is the one a power user would actually keep in their own graph. It's the reusable one. The rest are workflow plumbing; this is a tool.