How to use Join Strings node in Oraphim

Type ID: geometry.string_join
Category: Text

What this node does

The Join Strings 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 5 sockets and 3 properties for this node. Its main registered inputs are Delimiter, String, String 2; its main outputs are Geometry, String. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Delimiter	delimiter	String
String	string	String
String 2	string2	String

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
String	out_string	String

Controls

Control	Key	Type	Group	Registry default
Delimiter	delimiter	String	Inputs	0.0
String	string	String	Inputs	0.0
String 2	string2	String	Inputs	0.0

How to use it

1. Add Join Strings from node search. Use geometry.string_join when you need the exact registry entry.
2. Connect a compatible String source to Delimiter. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Delimiter, String, String 2 first so you can see the node's effect in isolation.
4. Route Geometry (Geometry3D) 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 Join Strings. Feed a compatible source into Delimiter. Change Delimiter away from its registry default and compare the result. Connect Geometry 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

• Glyphs on Elements — geometry.glyphs_on_elements
• String to Curves — geometry.string_to_curves
• Text Motion — geometry.text_motion
• Text to Glyph Geometry — geometry.text_to_glyph_geometry
• 3D Cursor — geometry.tool_3d_cursor

Return to the complete Oraphim node reference.