VRGDG_PromptSplitter2

VRGDG_PromptSplitter2 is exactly what its name implies: a version of VRGameDevGirl's prompt splitter with exactly two text outputs instead of fifty. You feed it a JSON string and get back two scene prompts.

It's part of the pack's family of fixed-output splitters. Where the main VRGDG_PromptSplitter takes raw text and a scene count, this one takes JSON directly - the node family moved to JSON-string inputs as the pack's prompt-map format matured. Two outputs means it's built for the specific spots in the music video workflow where exactly two chunks come out, like splitting a scene's prompt into a positive and a continuation, or handing off a two-part lyric segment.

How it works

One required input:

• json_string - the prompt-map JSON as text. Paste it or wire it from an upstream node. Defaults to {}, so an empty node isn't an error, just an empty output.

Outputs: text_output_1 and text_output_2, both STRING, wired into whatever consumes scene one and scene two downstream.

There's no index and no scene count here - the node reads the JSON and hands you the first two entries. If your JSON has more than two prompts, that's fine; you just only get the first two on this node. That's the deal with fixed-output splitters: you pick the one whose output count matches the job, not the one that adapts.

When to reach for it

Honestly, rarely on its own. It's a workflow-internal node - the kind you encounter when you open a shipped workflow and wonder why this tiny thing is wired between the JSON fixer and the video nodes. The answer is that some sections of the pipeline only ever have two chunks, and a two-port node keeps the graph honest about that. If you're building your own graph, VRGDG_PromptSplitter_General (one output, index-picked) or the main splitter is usually a better fit. This one is for matching the pack's structure, not for reinventing it.

Installing it

It ships with the pack:

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

then restart, or ComfyUI Manager → search vrgamedev. No models, no heavy dependencies - pure JSON-to-text splitting.

The honest take

The two-output variant is the most skippable of the splitter family if you're building from scratch, but don't delete it from a shipped workflow - the graphs here depend on exact port counts, and swapping in a "better" splitter means rewiring everything around it. When in doubt, leave the pack's plumbing alone.