Output Boolean

Don't confuse this with RiceRoundBooleanNode - they look similar (same name and value fields, same Chinese default label "开关," meaning "switch") but they belong to opposite halves of this pack. RiceRoundBooleanNode is Input-category: it's how you expose a toggle as a field on your published RiceRound page. RiceRoundOutputBooleanNode is Output-category and marked as an output node - a debugging tool for confirming what a boolean value actually is at a given point in your graph while you're still building, not something you leave wired into the workflow you publish.

What it's for

RiceRound's README is explicit that the Output-category nodes exist to troubleshoot a deployment before it goes live, as distinct from the Input-category nodes that make up the graph you actually publish. This node fits that role: take a boolean value, give it a label, and get back a STRING - a human-readable check of what that value is, useful the same way a print statement is useful while debugging code. It's not something end users of your published page ever see.

The inputs and output that matter

• name (STRING, default "开关") - a label for whatever you're inspecting.
• value (BOOLEAN, default false) - the boolean you're checking.
• Output: value (STRING) - note the type change from the input: you feed it a BOOLEAN, it hands back a STRING, presumably a readable rendering of that value alongside its name. That's the pattern across every node in RiceRound's Output category - whatever comes in, a STRING comes out, which is consistent with all of them feeding some kind of shared debug/log display rather than doing meaningful data transformation.

Installing it

Through ComfyUI Manager: search "RiceRound," install, restart. By hand:

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

then restart ComfyUI. No dependencies or model downloads are listed in the README for this pack - it's a lightweight packaging and debugging layer, not a generation pack.

Common issues & troubleshooting

You left this wired into the workflow you're about to publish. Take it out first. The README's rule is specific: Input-category nodes belong in the graph you feed to RiceRound Publish; Output-category nodes, this one included, are for local troubleshooting only.

You're mixing this up with RiceRoundBooleanNode. Easy mistake given the shared naming and default label - check the category in the node search (Input vs. Output) if you're not sure which one you just dragged in. If your goal is exposing a toggle on the published page, you want the Input version; if your goal is checking a value while debugging, you want this one.

You expected a BOOLEAN back out and got a STRING instead. That's correct behavior for this node, not a bug - every Output-category node in this pack normalizes its result to a STRING regardless of what type it took in, which fits its role as a debug/preview tool rather than a data-processing step in your actual pipeline.