XB-BOX - 📋 列表分发

Some nodes hand you a list - a batch of file paths, a set of storyboard frames, several prompts at once. But the node on the other end of the wire wants individual strings, one per input. That's the gap XB_ListDispatcher fills: it takes a list of strings, splits it by line, and pushes each line out on its own dedicated output port. You get a fan-out node that turns one messy list wire into clean, individually-addressable text lines.

The reason this exists is ComfyUI's list handling. When a node is list-aware (INPUT_IS_LIST), its input actually receives a list of values even if it looks like a single wire. This node joins everything it receives, splits on newlines, strips each line, drops empties, and then emits line 1 on 文本1, line 2 on 文本2, and so on. It's plumbing in the truest sense - no pixels touched, no data transformed beyond the split - which is exactly what the plumbing layer of ComfyUI is for (see the node-plumbing essay in the KB).

The two inputs

• 列表输入 (list input) - a STRING socket marked as an input (you must wire something in; it won't take typed text). Any list of strings works.
• 输出数量 (output count) - integer, 1 to 99, default 3. This controls how many of the 99 available output ports actually carry data.

That's the whole control surface. Set output count to 5 and you get 文本1 through 文本5 populated; the remaining ports exist but output empty strings.

Outputs

Up to 99 STRING outputs named 文本1…文本99 (Text1…Text99). Practical pattern: feed it a multi-line prompt list from a batch node, set the count, and wire each output into a separate CLIP Text Encode for per-line conditioning. Feed it the output of XB_llamaStoryboardInstruct's output_list and each frame prompt lands on its own wire for batch image generation.

A couple of honest notes

The node treats every newline as a split point and strips whitespace - so blank lines silently vanish, and a line containing only spaces disappears rather than erroring. That's usually what you want, but it means you can't round-trip intentionally-empty lines. Also, empty outputs beyond the source data's length are empty strings, not errors - a downstream node getting "" where it expected text is the thing to watch when you change the input list's length without changing the output count.

Installing it

Part of XB_ToolBox, so the standard install applies:

cd ComfyUI/custom_nodes
git clone https://github.com/WJLUOXIAO/XB_ToolBox.git

or search XB_ToolBox in ComfyUI Manager and restart. No dependencies beyond ComfyUI core.

Should you use it?

If you're already running XB_ToolBox (say, for the llama storyboard nodes), this is a handy no-cost utility for un-batching lists into individual wires. If you're not running the pack, it's a perfectly fine generic list-splitter but not a reason to install a 300-node suite on its own - ComfyUI's own batch/split utilities cover much of the same ground. Where it earns its keep is the 99-output headroom and the clean newline handling in workflows that already live in the XB ecosystem.