Unpack Text 10

This is the Unpack node most people will actually use. Unpack Text 10 takes one WGC_TEXT_BUNDLE in and hands you ten STRING outputs, and here's the part that earns the install: those outputs are auto-renamed to match the labels on your Pack Text 10. Your ten-box prompt library arrives on the far side as ten named wires - studio, golden_hour, film_grain, neg quality - ready to plug into whatever consumes a STRING.

The strings are plain text, so the outputs feed the usual suspects: CLIP Text Encode for positive and negative prompts, prompt-builder nodes, LoRA trigger stacks, anything with a string input. The pack just makes the plumbing legible.

How it works

Under the hood it's trivial: the bundle is a tuple of strings, and this node emits positions 0 through 9. All the cleverness is in the frontend, which walks the wire back to the connected Pack node - following ordinary Reroute nodes - to read the display labels and apply them to the outputs. Crucially, none of that label information enters the executed prompt. Only the ten string values do. That's what makes the whole setup cache-safe: you can rename a box on the Pack side, hit Run, and ComfyUI skips re-executing everything downstream because the submitted prompt didn't change. On a big workflow that's the difference between reorganizing your library and re-generating your image.

Label modes

• Live (default) - follow Pack labels automatically.
• Frozen - keep the current labels until you press Refresh Labels.
• Manual - turn auto-renaming off and edit names by hand.

Inputs and output

• bundle (input) - one WGC_TEXT_BUNDLE from any Pack Text size.
• text_01 … text_10 (outputs) - ten STRINGs.

Sizes stay forgiving: a Pack Text 20 feeding this reads out only the first ten; a Pack Text 3 leaves seven outputs empty.

Install

The pack is heyheywoah/WGC-Nodes. ComfyUI Manager → search "WGC Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/heyheywoah/WGC-Nodes.git

Restart ComfyUI. No dependencies, no models, no API key.

Where people get tripped up

• Empty outputs almost always mean the upstream bundle is smaller than this node - by design, not an error.
• Labels didn't follow the rename. Hit Refresh Labels, and check the label mode isn't Frozen/Manual.
• Subgraph boundaries. If your bundle crosses a collapsed Subgraph region, auto-label discovery isn't guaranteed in the 0.1.0 release; the values still arrive, only the names may lag.

Ten outputs is a wall of wires, sure - but it's a wall with names on it. That's the whole upgrade over a tangle of text_01s.