Mask Bridge

The mask counterpart to RiceRoundImageBridgeNode, and it does exactly the same job: take a MASK in, hand the identical MASK back out, and in doing so, mark that specific wire as a RiceRound-recognized input point rather than an arbitrary connection in the middle of your graph. If your published workflow needs a mask that's already being produced somewhere else in your pipeline - a segmentation step, an earlier inpaint pass - this is how you flag it as something RiceRound's publish tooling should treat as an exposed input rather than baked-in internal plumbing.

Why a passthrough node needs to exist at all

RiceRound Publish (RiceRoundEncryptNode) builds its generated page and cloud-node interface by scanning your graph for RiceRound's own Input-category nodes. A raw MASK output from some arbitrary node in the middle of your workflow isn't part of that vocabulary - RiceRound has no way to know you meant it as user-facing input rather than internal detail. Routing it through Mask Bridge first gives the publish step a landmark it recognizes at that exact point in the graph. That's an inference from the node's naming and category, not something the README spells out explicitly (it doesn't document individual nodes at all), but it's the most coherent explanation for why an otherwise do-nothing passthrough exists in the pack.

The input and output that matter

• mask (required, MASK) - tooltip reads "only image," which is a copy-paste leftover from the pack's image-typed nodes rather than an accurate description of a mask field. Don't read too much into the exact tooltip wording across this pack; several of them carry over boilerplate that doesn't quite match the field it's attached to.
• Output: value (MASK) - the same mask, unmodified. Wire it downstream exactly as you would the source mask.

Installing it

Through ComfyUI Manager: search "RiceRound," install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/RiceRound/ComfyUI_RiceRound

then restart ComfyUI. The README documents no dependencies or model downloads for the pack - it's a packaging and publishing layer, not a generation one, so install is quick regardless of which node in it you're here for.

Common issues & troubleshooting

You added this and nothing visibly changed. Correct - it's an identity passthrough, so there's no visual or functional difference in your local test run. Its entire purpose is signaling to RiceRound's publish step, which you won't see the effect of until you actually run RiceRound Publish and check what fields show up on the generated page.

Deciding whether this belongs in your published workflow. It does - it's Input-category, and the README's rule is that Input-category nodes are what belong in the graph you feed into RiceRound Publish, while the separate Output-category nodes are debugging aids you strip out first.

You're not sure whether to use this or RiceRoundDownloadMaskNode. Use Download Mask when the mask should come from a URL fetched at runtime - the more realistic shape for something an end user's client supplies. Use Mask Bridge when the mask is already being computed inside your own graph and you just need to flag that computed value as an exposed input point.