How to use Format Number node in Oraphim

Type ID: motion.text.format_number
Category: Text

What this node does

The Format Number node is registered in Oraphim's Text category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 6 sockets and 12 properties for this node. Its main registered inputs are Value, Prefix, Suffix; its main outputs are Text, Rounded Value, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Value	in_value	Float
Prefix	in_prefix	String
Suffix	in_suffix	String

Outputs

Socket	Key	Type
Text	out_text	String
Rounded Value	out_value	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Value	value	Float	Input	0.0
Format	mode	String	Format	Decimal
Decimal Places	decimals	Int	Format	0.0
Rounding	rounding	String	Format	Nearest
Digit Grouping	grouping	Bool	Separators	0.0
Group Separator	groupSeparator	String	Separators	,
Decimal Separator	decimalSeparator	String	Separators	.
Trim Trailing Zeros	trimTrailingZeros	Bool	Format	0.0
Compact Threshold	compactThreshold	Float	Format	1000.0
Negative Style	negativeStyle	String	Affixes	Minus
Prefix	prefix	String	Affixes	0.0
Suffix	suffix	String	Affixes	0.0

How to use it

1. Add Format Number from node search. Use motion.text.format_number when you need the exact registry entry.
2. Connect a compatible Float source to Value. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Value, Format, Decimal Places first so you can see the node's effect in isolation.
4. Route Text (String) into a compatible downstream node, viewer, or output path.
5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Format Number. Feed a compatible source into Value. Change Value away from its registry default and compare the result. Connect Text to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

• If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
• If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
• If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
• If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Related nodes

• Transform Glyphs — motion.text.glyph_transform
• Analyze Text — motion.text.analyze
• Text Selector — motion.text.selector
• Text Template — motion.text.template
• Glyphs on Elements — geometry.glyphs_on_elements

Return to the complete Oraphim node reference.