Parameter Groups & UI

Public Labels should describe the visible or conceptual result. A user should be able to understand the interface without opening the source graph.

Use Graph Properties → Interface to define public parameter order.

Give related parameters the same Group name. For example a Pattern group might contain Scale, Rotation, and Distortion, while Surface might contain Damage, Roughness, and Fine Detail. Group membership comes directly from the stored Group text, so keep spelling and capitalization consistent.

Leaving Group empty keeps a parameter ungrouped. This is useful for important controls such as Scale or Seed that should stay visible at the top level. Avoid one-item groups unless the grouping genuinely improves the interface.

IMAGE Organize related exposed parameters into clear interface groups.

A fresh instance should already produce a valid, useful result. Defaults are part of asset design, not just technical values copied from the source graph.

Min and Max should describe the range that is useful for the asset rather than every value the underlying math can accept. If a meaningful Float range is 0–1, exposing -10,000 to 10,000 only makes the control harder to use.

Use the public type that matches how users think about the value:

When an Integer represents modes, expose it as an Enum rather than making users memorize values such as 0, 1, and 2. Keep existing Integer meanings stable once the asset is in use.