Unpack Text 30

Thirty outputs. Let's be honest about what that looks like: this node turns one WGC_TEXT_BUNDLE into thirty STRING wires, and if you feed it a full Pack Text 30, that's thirty labeled connections radiating into your graph. It's the maximum-capacity Unpack in WGC-Nodes, and it exists for the person with a genuinely enormous prompt library - thirty styles, thirty scene descriptions, a per-character set that would overflow the 20.

The auto-rename trick is the same as every other size: outputs follow the labels on the upstream Pack node, so instead of text_01 through text_30 you get thirty meaningful names. The label modes are the same too - Live, Frozen, and Manual - but at this scale the Manual mode earns its keep. Auto-renaming thirty outputs while you're mid-edit is a lot of churn; freezing the names and refreshing deliberately is often the calmer workflow.

How it works

Mechanically it's the simplest node in the pack: the bundle is a tuple of strings, and this node emits positions 0 through 29. All the label magic lives in the frontend, which walks the wire back to the Pack node (following ordinary Reroutes) to discover display names. None of that enters the executed prompt - only the string values do - which is what keeps renaming and reorganizing cache-safe. At thirty boxes, that cache-safety is the difference between a workflow that re-runs when you reshuffle your library and one that just keeps going.

Inputs and output

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

Mismatched sizes stay graceful: a Pack Text 10 feeding this leaves twenty outputs empty; a Pack Text 30 mirrors all thirty. There's no reason you must pair matching sizes - unpack only as many as your graph consumes and let a smaller Unpack keep the canvas tidy.

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

• Thirty empty outputs if you fed it a small bundle. By design, not an error - but if a wall of empty strings is annoying you, size the Unpack to what you actually use.
• Subgraph caveat, at maximum impact. A bundle this big is the most likely to cross a collapsed Subgraph region, and automatic label discovery over subgraph boundaries isn't guaranteed in the 0.1.0 release. The strings always arrive; the names may need Refresh Labels or Manual mode.
• Don't buy the biggest size for the aesthetic. If your library is ten styles, Unpack Text 10 is the right tool. Thirty is for thirty.

For the prompt hoarder, this is the endpoint of the ladder: one wire in, thirty labeled strings out. Just be sure you actually need thirty.