Input Text

If your published RiceRound workflow needs a prompt box, a caption field, or any other chunk of free text that an end user should be able to type into, RiceRoundInputTextNode is the node for it. It's a plain multiline text field that outputs a STRING - the RiceRound-flavored equivalent of a core text-input node, purpose-built to become a form field on the web page riceround.online generates from your published workflow.

Where it fits

ComfyUI_RiceRound doesn't generate images itself; it packages a workflow you've already built so RiceRound's platform can host it as a page and a callable node, with each Input-category node in your graph corresponding to one editable field on that page. This one's job is text. Whatever you type here while testing locally is the field's default; once published, whoever uses your page gets to overwrite it before the workflow runs on their behalf.

The inputs and output that matter

• text_info (STRING, multiline) - the only field. Its tooltip reads "The text to be encoded," which is worth flagging rather than trusting literally: that's the stock description ComfyUI ships on CLIPTextEncode, and this node has nothing to do with CLIP or text encoding - it's a plain text box that happens to carry the same boilerplate tooltip forward. Don't read anything into "encoded" here.
• Output: labeled STRING rather than the value naming most of this pack's other nodes use for their outputs - a small inconsistency worth knowing about if you're wiring things up and expecting the same output name across every RiceRound node. It behaves like any STRING output regardless of the label.

Installing it

Search "RiceRound" in ComfyUI Manager and install, or install by hand:

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

then restart ComfyUI. There's no requirements.txt or model weight called out in the README for this pack - it's a lightweight packaging and upload layer on top of a workflow you've already built, not a generation node with its own dependencies.

Common issues & troubleshooting

Is this safe to leave in a workflow you're about to publish? Yes - it's Input-category, which is exactly what the README says belongs in the graph you feed into RiceRound Publish. The nodes to pull out before publishing live in the separate Output category (things like Output Boolean and Output Float), which the README describes as debugging aids only.

You wired this into something expecting a specific STRING output name and it didn't connect the way you expected. Because this node's output socket is labeled STRING rather than the value label most other RiceRound nodes use, double-check the actual wire rather than assuming the naming pattern from RiceRoundIntNode or RiceRoundFloatNode carries over here - it doesn't.

The multiline box doesn't seem to save what you typed once published. Confirm you're testing against the same template_id you're publishing to - RiceRound Publish's default template_id is a demo placeholder, and if you never swapped it for your own project's ID, you may be looking at a stale or unrelated published version rather than the one you just edited locally.