Authoring model

This section documents the core V-SwiFT data model that authors patch against.

Data hierarchy

A V-SwiFT-authored part switch is built in layers:

  • Data_PartSwitch

    • owns the full switch definition for a part

  • VariantSet

    • groups one family of choices

  • Variant

    • represents one selectable option in that set

  • transformers

    • apply the actual changes or generate saved override data

Practical mental model

Think of Data_PartSwitch as the container, VariantSet as a category, and Variant as a choice inside that category. The transformer list on a variant is where the real behavior lives.

Special authored collections

Data_PartSwitch also carries PredefinedDynamicNodes, which gives you a way to define attach-node data that exists independently of any one variant transformer.

Related topics

Transformer reference

Patch Manager integration

Runtime behavior