Tala Esenlikler

Initial UE 5.7 release

Linked And Composite Variants

Use linked groups and composite points to share or combine interaction surfaces without duplicating command authoring.

Interaction Framework 1.0.0 UE5.7

Linked Group Points

A linked-group point uses EInteractionRuntimePointKind LinkedGroup and references an FInteractionRuntimeLinkedGroupDefinition by linked group id. The point supplies the world surface and point id, while the linked group owns the shared variants, selection mode, optional policy profile, and widget payload. Use this when several sockets, handles, or helper components should expose the same command set.

Shared Authoring

Linked groups prevent duplicated command rows. Instead of copying variants across several points, author the variants once in the linked group and point multiple linked surfaces at that group. Each surface can still be focused independently, but the command and variant logic remains centralized.

Composite Points

A composite point uses EInteractionRuntimePointKind Composite and an authored CompositeGroupId. Composite commands can use CompositeGroupOrder to control ordering inside the grouped surface. Use composite points when an actor should expose one combined command surface from several authored points or when command rows need to be assembled into a larger interaction menu.

Variant Compatibility

Keep variant ids consistent across grouped authoring when runtime state should map cleanly from one surface to another. If a linked group contains variants named Locked and Unlocked, every linked surface using that group receives those variants from the group. For composite setups, use clear command ids and ordering so the final surface remains predictable when several points contribute rows.

Payload And Policy Inheritance

Linked groups can provide a shared UInteractionRuntimeWidgetPayload and policy profile override. A point can still carry its own projection and proximity settings for the physical surface. Keep visual placement on the point and shared widget/data behavior on the group when the same command appears in several places.

Common Build Patterns

  • Two handles on one door share a linked group with the same Open command.
  • A machine with front, side, and rear helper points uses linked surfaces so every side opens the same command surface.
  • A console combines Inspect, Repair, and Use rows from several authored areas through composite point authoring.
  • A linked group carries a widget payload override so every shared surface opens the same custom prompt widget.