VRGDG_SaveText

VRGDG_SaveText is a small file-writing node that sorts text into named slots, and it's best understood as the storyboard's scratchpad. It takes a piece of text, files it under one of six fixed categories - subject1, subject2, scene1, scene2, other1, other2 - and writes it out, giving you back both the text and the file path it was saved to.

Why six fixed slots

That's the tell that this node was built for a specific pipeline, not as a generic "save text" utility. The VRGameDevGirl music-video workflow is structured around two subjects and two scene types: you have a main character (subject), maybe a second character (subject2), and then scene descriptions that get turned into prompts. other1/other2 are the catch-all bins. The point of the fixed slots is that other nodes in the pack can expect a file to exist at a known location - the storyboard creator can read scene1 without you telling it where the file is. The moment you use a generic filename, that contract breaks.

So the workflow pattern is: the LLM node (VRGDG_Qwen3.5) produces a character description, this node files it under subject1, and later stages read that file back. The pass-through text output means you can also keep using the text downstream on a wire - the file write is a side effect, not the end of the line.

Inputs and outputs

• text_type - the enum: subject1, subject2, scene1, scene2, other1, other2. Pick the slot.
• text - the multiline string to save.

Outputs are text (echoed back) and file_path (where it was written).

That's the whole node. There's no folder or filename control and no overwrite toggle - it writes to wherever the pack's internal convention dictates. For a beginner, the practical lesson is: don't fight the fixed slots. If you need arbitrary filenames and folders, the pack's VRGDG_SaveTextAdvanced is the one that gives you those knobs.

Install

Same drill as the rest of the pack:

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

or ComfyUI Manager → "vrgamedev" → restart. Requirements (kornia, librosa, imageio) install with it; Windows portable users run the requirements file from python_embeded.

The honest take: this node is only useful inside the workflow it was designed for. If you're not running the pack's story pipeline, you'd reach for SaveTextAdvanced or a generic text-writer instead. But if you are following the music-video tutorial and a node is reading scene1 from disk, this is the node that put it there - and knowing that saves you from hunting through your output folder wondering where a file came from.