Output Float

The Output-category counterpart to RiceRoundFloatNode, and, like the rest of RiceRound's Output family, it's a debugging tool rather than something meant to end up in the workflow you publish. Feed it a float, get back a STRING you can inspect - a readable check of a number's value at a given point in your graph while you're still building, not a field an end user of your published page will ever interact with.

Where it fits

RiceRound's README draws a hard line between its two node families: Input-category nodes are what you build a publishable workflow out of, and Output-category nodes exist purely to help you troubleshoot before you go live. RiceRoundOutputFloatNode follows that Output pattern exactly - same shape as RiceRoundOutputBooleanNode and the other Output-category nodes, taking a typed value and normalizing it down to a STRING result rather than passing the original type through.

The inputs and output that matter

• name (STRING, default "数值" - "value/number" in Chinese) - a label for what you're checking.
• number (FLOAT, no default in the schema - you set it explicitly) - the value being inspected.
• min / max (FLOAT, defaults 0 and 1,000,000) - worth noting this range is dramatically looser than RiceRoundFloatNode's default range of 0–100. Since this is a debugging node rather than something validating end-user input, that makes sense - it's less about constraining a real field and more about not accidentally clipping whatever value you're actually trying to inspect.
• Output: value (STRING) - the readable result, not the raw FLOAT. Every node in this pack's Output category shares that pattern.

Installing it

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

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

then restart ComfyUI. The README lists no dependencies or model downloads for this pack - install stays quick regardless of which specific node you're after.

Common issues & troubleshooting

It's still in the graph you're about to publish. Remove it first - per the README, this is an Output-category node meant for local debugging, not part of the workflow you feed into RiceRound Publish. If your actual goal is a user-adjustable float field on the published page, that's RiceRoundFloatNode instead.

You're confused by the min/max range being so much wider here than on the Input version. That's expected, not a mismatch to fix - this node isn't validating a field an end user submits, so there's no reason for its range to match the tighter default on the Input node. Set it to whatever bracket makes sense for what you're actually inspecting during a given debug session.

You expected the raw number back and got text instead. Same pattern as every other Output-category node here: it normalizes whatever type it receives into a STRING for display, which is consistent with all of them feeding some shared debug view rather than doing real data processing.