VRGDG_MuteUnmute4PromptCreatorWF_0

VRGDG_MuteUnmute4PromptCreatorWF_0 is a workflow-choreography node: it mutes, unmutes, or bypasses whole groups of nodes at runtime, and can auto-queue the next run when it's done. Think of it as a remote control for your own graph, used to swap which parts of a workflow are live between passes.

ComfyUI lets you mute nodes by hand - but that's a manual canvas action, and it doesn't scale to "run pass A, then pass B, then pass C" without you babysitting the UI. This node makes the muting itself part of the graph: you tell it which node groups to act on, what action to take (active / mute / bypass), and it executes that on execution. The name says "4PromptCreator" - it's built to drive the prompt-creator workflow through a batch run, muting the nodes that belong to a stage you're not currently generating.

Inputs worth knowing

• signal - a wildcard trigger that fires the node. Wire in whatever marks the run boundary; the node acts when this fires.
• group_count - how many of the group slots (1–12) you're using.
• group_action - the global action for the listed groups: active, mute, or bypass. Bypass and mute differ subtly - bypass routes around the node while mute disables it entirely; for prompt nodes they're close cousins, and mute is the default for a reason.
• group_1 … group_12 - the target node groups (each with its own group_N_action override). Groups are the named selection boxes you can draw around nodes in ComfyUI, so "group_1 = Camera Pass" is a readable, self-documenting way to target a cluster.
• node_ids_csv - an alternative targeting method: a raw comma-separated list of node IDs, for when you'd rather be precise than use named groups.
• group_targets_json - the power-user route: a JSON blob of targets, letting another node construct the target list dynamically.
• auto_queue_next + queue_delay_seconds - after acting, auto-queue the next workflow run, optionally after a delay. This is what makes multi-pass batch runs hands-off: one run mutes the "lyrics" group, queues the next run which mutes the "scenes" group, and so on down the line.

Output is a single signal_opt wildcard, passed through so the node can sit inline in a chain without breaking the flow. It's also marked as an output node, meaning it works fine as a terminal "do this and end the run" step.

Why there are three of them

The _0, _1, _2 suffix is the giveaway: this is the same class instantiated three times so a single workflow can have three independent muting stages without node-name collisions. Stage 0 mutes the setup group and queues stage 1, stage 1 swaps in the second set and queues stage 2, and so on. If you've ever wanted a workflow to run three passes unattended with different nodes live in each, this trio is the mechanism.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

Restart ComfyUI; find it under VRGDG/General. ComfyUI Manager: search vrgamedev. No extra downloads.

Honest note

This is workflow plumbing, and it shows its author-specific origins - the "4PromptCreator" naming and the CSV/JSON targeting are clearly shaped around one particular graph. The concept is sound and useful, but expect to read the tooltips carefully and experiment: muting happens at runtime, and a wrong group_targets_json can quietly mute the wrong half of your graph. Test with group_count = 1 and one obvious group before scripting a whole batch.