Bus Out

Bus Out is the receiving end of this pack's 25-channel bus. It takes one WCX_BUS input (the 总线束 bundle produced by Bus In), and unpacks it into twenty-five outputs, 输出_1 through 输出_25 - one for every slot the bus supports. Feed it the bundle and each output is the value that was connected to the matching slot at Bus In, or None for slots that were never connected.

It's the "one wire instead of forty" payoff. The KB's node-plumbing doc calls the context bundle the most important pattern in the plumbing layer: a dozen values that every downstream node needs get carried down a single line instead of as a dozen wires dragged across the whole canvas. Bus In packs, Bus Out unpacks, and in a big workflow that transformation is the difference between a graph you can read and a bowl of noodles. Same family as rgthree's Context, with this pack's stricter shape: no merging or updating on the line - Bus Out is a pure splitter.

Mechanics worth knowing:

• It always emits twenty-five outputs, even when the bundle is sparse. The source guarantees a full-length tuple, filling missing slots with None. That's defensive coding that prevents "tuple length changed" errors - and it means you can wire Bus Out's outputs into optional inputs downstream and let the Nones skip their work naturally.
• The labels are Chinese. Input 总线束 ("bus bundle"), outputs 输出_1…输出_25 ("output"). Cosmetic, expected, harmless.
• It validates defensively. If the input isn't a dict (or is None), it returns twenty-five Nones rather than crashing. You'll get that only if you bypass Bus In, since nothing else produces a WCX_BUS.

The caveat is the same one that applies to the whole bus: WCX_BUS only round-trips through this pack. Bus Out is the only reader of what Bus In writes, so any workflow using the bus depends on the pack being installed at both ends. That's the standard lock-in cost of pack-specific context types - worth paying when a big graph's legibility is the binding constraint, not worth it for a graph that fits on one screen.

Install is pack standard: ComfyUI Manager → search ComfyUI-Practical-Tools → install → restart, or git clone https://github.com/wenchengxiang/ComfyUI-Practical-Tools into ComfyUI/custom_nodes. No dependencies, no models. If every output is None, the bundle input wasn't connected or isn't a real WCX_BUS - re-check the Bus In on the other end.