Nodes/WGC Nodes/Pack Text 30
ComfyUI Node

Pack Text 30

The prompt hoarder's node

By heyheywoah·Created about a month ago·Updated about a month ago· 1
Pack Text 30
    • bundle
    text_01
    text_02
    text_03
    text_04
    text_05
    text_06
    text_07
    text_08
    text_09
    text_10
    text_11
    text_12
    text_13
    text_14
    text_15
    text_16
    text_17
    text_18
    text_19
    text_20
    text_21
    text_22
    text_23
    text_24
    text_25
    text_26
    text_27
    text_28
    text_29
    text_30

    Thirty text boxes is a lot of text boxes. Pack Text 30 is the top of the WGC-Nodes size ladder, and it exists for the honest case where you have a genuinely huge prompt library - thirty styles, thirty shot descriptions for a video project, a per-character prompt set that would fill a small wall. When you're there, this is the clean way to hold it: all thirty strings collapse into one bundle wire, and the panels fold down to slim labeled strips that remember their heights.

    Let me be blunt: most people will never need this. The pack's own design philosophy - fixed capacities, no dynamic slots - means you pick a size and live with it, and 30 is a lot to live with. If ten or twenty covers you, stop reading at the install section and grab the smaller node. But if you're the person with the 30-row spreadsheet of prompts, this is yours.

    How it works

    Same mechanism as every Pack Text node, just bigger: text_01 through text_30 get packed into a WGC_TEXT_BUNDLE tuple and travel down one wire. Only the string values enter the executed prompt - labels, collapsed state, and editor heights are frontend-only, so reorganizing thirty boxes doesn't invalidate ComfyUI's cache downstream. That property matters more here than anywhere: it's the difference between a workflow that re-runs when you shuffle your library and one that doesn't.

    Mixed sizes still connect. An Unpack Text 10 downstream reads only the first ten slots; an Unpack Text 30 mirrors all thirty back out.

    Inputs and output

    • text_01text_30 - thirty multiline STRING inputs, required, defaulting to empty. Nothing else to configure; this node is all text boxes, which is both its point and its ceiling.
    • bundle (output) - one connection carrying all thirty strings.

    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 model files, no API key.

    Where people get tripped up

    • Thirty outputs downstream is a lot of wire. An Unpack Text 30 next to your sampler becomes a wall of connections; that's normal, it's the price of the capacity. If it bothers you, an Unpack Text 5 or 10 on the far end keeps the graph calm and just drops the extras.
    • Dynamic prompts are off, as everywhere in this pack - no {a|b} expansion in these boxes.
    • Subgraph caveat bites hardest here. A bundle this big is more likely to cross a collapsed region, and label discovery over subgraph boundaries isn't guaranteed in 0.1.0. Reach for Manual label mode or Refresh Labels on the Unpack side when it does.

    The 30 is a niche size for a niche need. When you're in that niche, it's the only node that does the job in one wire.

    CategoryWGC/Text

    Inputs (30)

    NameTypeDefaultDescription
    text_01STRING
    text_02STRING
    text_03STRING
    text_04STRING
    text_05STRING
    text_06STRING
    text_07STRING
    text_08STRING
    text_09STRING
    text_10STRING
    text_11STRING
    text_12STRING
    text_13STRING
    text_14STRING
    text_15STRING
    text_16STRING
    text_17STRING
    text_18STRING
    text_19STRING
    text_20STRING
    text_21STRING
    text_22STRING
    text_23STRING
    text_24STRING
    text_25STRING
    text_26STRING
    text_27STRING
    text_28STRING
    text_29STRING
    text_30STRING

    Outputs (1)

    NameTypeDescription
    bundleWGC_TEXT_BUNDLE