Output Text

The plainest node in RiceRound's Output family, and a good one to reason about the whole family from. RiceRoundOutputTextNode takes a labeled string and hands back the same kind of thing, a STRING, which puts it a step apart from siblings like Output Boolean or Output Float - those do a real type conversion (BOOLEAN or FLOAT in, STRING out); this one is text in, text out. It's less a converter than a labeled pass-through you can glance at while building, before you ever touch RiceRound Publish.

Why that's still useful

ComfyUI_RiceRound exists to package a working local workflow into a hosted page and callable node on riceround.online, and the pack's README is explicit that its Output-category nodes - this one included - are there to troubleshoot a deployment, not to appear in the graph you actually publish. Even without a type conversion happening, tagging a string with a name and routing it through a dedicated node gives you a clean spot to check "is this the text I think it is" mid-build - a caption that got mangled somewhere upstream, a prompt fragment that didn't assemble the way you expected.

The inputs and output that matter

• name (STRING, default "文本" - "text" in Chinese) - the label for what you're checking. Like the rest of this pack's defaults, it ships untranslated; swap it for something meaningful if you're leaving this node visible while you work.
• str (STRING) - the text you're inspecting.
• Output: value (STRING) - the same text back out. Note this node's output socket is labeled value, matching the convention most of RiceRound's other nodes use - a small but real difference from RiceRoundInputTextNode, whose output is oddly labeled STRING instead.

Installing it

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 called out in the README - this pack is a packaging and upload layer for a workflow you've already built, not a generation node with weights to fetch.

Common issues & troubleshooting

It's wired into the workflow you're about to publish. Take it out first. The README's rule is specific to category, not to whether a node "does" anything: Input-category nodes belong in a publishable graph, and Output-category nodes, including this one, are meant for local troubleshooting only.

You wanted an actual text field for your published page and grabbed this instead. That's RiceRoundInputTextNode - a genuine Input-category field that becomes an editable box on the generated page. This node doesn't expose anything to an end user; it just lets you look at a value while you're still building.

Nothing seems to "happen" when you run it. That's expected - since there's no type conversion here, the only output of running this node is being able to see the string's value in ComfyUI's own UI. It's a check, not a transformation.