Node Collector

Some nodes are the opposite of what they look like. Node Collector looks like a data node - multiple inputs, one output - but it carries no data at all. It's a way to gather references to a bunch of nodes and hand them to a mode-control node so that one switch can mute or bypass all of them. If you've ever wanted a "kill switch" for a dozen scattered nodes - every loader in the graph, say - this is the node that lets you bundle them.

The mechanism is in the wiring. You connect the nodes you want to control into the Collector's inputs (it grows inputs dynamically), and connect the Collector's single Output socket to a Fast Muter, Fast Bypasser, or Mode Repeater. Then flipping that downstream node's mode flips all the collected nodes together. It's the aggregation half of the mute/bypass toolkit: the Collector rounds them up, the repeater/muter applies the mode. The author's source comment says it plainly: it's based on the same idea as rgthree-comfy's collector, rewritten for ComfyUI's V3 API and Nodes 2.0 compatibility - the frontend rewrite that broke the original rgthree implementations.

How it works

Like every node in this pack's mode family (Mode Bridge, Mode Relay, Mute/Bypass Repeater), it's a virtual node - the Python execution returns None, and the real behavior is frontend JavaScript that tracks which nodes feed the Collector and forwards them to the connected mode node. There are no widgets, no data transformations, no output values. Its entire existence is to reduce a fan-in of many node references to one socket, so downstream mode control has a single handle to grip.

The Output socket is typed * and the tooltip spells out the intended consumers: "Aggregated output to Fast Muter, Bypasser, or Repeater." Those Fast Muter/Bypasser nodes aren't in your brief - they're part of the same pack's toolset that this Collector feeds.

The inputs that matter

There are no widgets to configure. The input sockets are the interface - connect the nodes you want grouped, and that's the setup done. If you connect nothing, the Collector has nothing to collect, and the downstream muter has nothing to toggle.

Install

Part of ComfyUI_Eclipse (r-vage). ComfyUI Manager, search ComfyUI_Eclipse, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart ComfyUI - these frontend-driven nodes need the restart before the JS loads; a workflow reload alone won't register them. No models, no heavy dependencies. If you grabbed a shared [Eclipse] workflow that won't load, the pack's v4.0 removed legacy node IDs after the RvTools_v2 rename - run the Workflow Migration Tool rather than reinstalling.

Common issues

"Nothing gets muted" is almost always one of two things: the collected nodes are connected into the Collector, but the Collector's output isn't wired to a Fast Muter/Bypasser/Repeater (it does nothing on its own - it's the middleman, not the switch); or the workflow was loaded before the frontend JS registered, so the mode tracking never initialized - restart ComfyUI. And the same boundary as the rest of the family: this controls mute/bypass state, not data. If you expected values to flow through the Output, you've found the wrong node - which is exactly the confusion this one generates on first sight.