Download Mask

The mask-only sibling of RiceRoundDownloadImageNode: give it a URL, get a MASK back. If your published workflow needs to accept a mask as input - say, for an inpaint region someone drew on the RiceRound-generated page - this is how it gets fetched into the graph, since a workflow running on riceround.online for someone else has no access to your local filesystem and needs the mask handed to it over the network instead.

Where it fits

This pack's whole job is turning a local ComfyUI workflow into a hosted page and callable node on riceround.online, with each Input-category node in your graph becoming part of the interface that page exposes. For anything image- or mask-shaped that needs to come from outside your machine once the workflow is live, a URL-based node like this one is the realistic option - the local file-picker equivalents (RiceRoundImageNode, and by extension a hypothetical local mask picker) only make sense for your own testing, not for what an actual visitor to your published page can provide.

The input and output that matter

• mask_url (STRING, no default) - the URL to fetch the mask from. As with RiceRoundDownloadImageNode, there's no format spec beyond "it's a string field" in the schema, so validate by testing against a real URL rather than assuming a particular format is required.
• Output: value (MASK) - wire it into whatever expects a mask, same as any other MASK source in ComfyUI.

If you need both an image and its mask from the same URL in one step, RiceRoundDownloadImageAndMaskNode covers that combined case instead of chaining two separate download nodes.

Installing it

Through ComfyUI Manager: search "RiceRound," install, restart. Manually:

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

then restart ComfyUI. No dependencies or model downloads are documented in the README for this pack - it's a lightweight packaging and network-fetch layer, not a generation pack with weights to download.

Common issues & troubleshooting

The fetch fails or the mask comes through wrong. Standard URL-fetch failure modes apply here same as with the image version: an unreachable URL, a link that requires auth the node can't provide, or a URL pointing at something that isn't actually a usable mask image. Also worth checking: whether the source image at that URL even has the alpha/luminance data you're expecting a mask to be derived from - a plain RGB image with no meaningful alpha channel will produce a mask that isn't useful even if the download itself succeeds.

Is it safe to leave wired into the workflow you're publishing? Yes - it's Input-category, and the README's rule is that Input-category nodes are exactly what belongs in the graph you run through RiceRound Publish. Leave the separate Output-category nodes out instead; those are the debugging-only family.

You want to sanity-check the mask visually before trusting it downstream. Nothing in this pack previews a MASK directly - route it into a core preview or mask-to-image node temporarily while you're debugging, then remove that detour before you publish, since it's not one of RiceRound's own recognized nodes.