How To Use This Page
The target definition editor validates authoring data before runtime. Treat errors as blockers and warnings as design checks. The table below groups the common validation messages by the field you should inspect first.
| Message Or Symptom | Fix |
|---|---|
| No points authored. | Use Add Point. The action creates a normal point with one default variant and one default command row. |
Invalid or duplicate PointId. |
Assign a unique FInteractionRuntimePointId to every normal or composite point. |
| VariantId is required when point has multiple variants. | Leave the single default variant unnamed. Once the point has multiple variants, assign unique VariantId values. |
| All variants have no command rows. | Add at least one command row to a variant, or remove the inactive point. |
Invalid CommandId. |
Assign a stable FInteractionRuntimeCommandId to every command row with row kind Command. |
| InputAction is required. | Assign an input action to interactive commands. Auto-trigger commands do not need command input. |
| InputAction should use Boolean value type. | Open the input action asset and set Value Type to Boolean so it behaves like a pressed/released button. |
| Input action is not present in Runtime InteractionInputMappingContext. | Add the action to the mapping context assigned in UInteractionFrameworkRuntimeDeveloperSettings. |
| Hold pattern requires duration greater than 0. | Set the hold duration field to a positive value. |
| Multi-Tap requires tap count and tap window. | Set required taps to at least 1 and tap window to a positive value. |
| More marker next/back input is required. | Assign both Next and Back input actions on the More marker. |
| Input action collides on the same page. | Use different input actions for commands, More, Back, and cancel controls that can show on the same prompt page. |
| Linked-group point cannot author local variants or commands. | Move command authoring to the linked group definition or change the point kind. |
| Linked group must have at least 2 member points. | Add another point referencing the same linked group id or remove the linked group. |
| Widget payload class must derive from InteractionUIWidgetBase. | Change the payload widget class override to a widget class based on UInteractionUIWidgetBase. |
| POI or Interact view dot must be in [-1, 1]. | Clamp authored view-dot values to the valid dot-product range. |
| POI range is smaller than interact range. | Increase the point-of-interest range or reduce interact range so prompts can show before activation range. |
| Multi-participant commands require MultipleInteractors. | Set the resolved participation policy to allow multiple interactors. |
| RequiredParticipants must be at least 2. | Use single-player interaction for one participant, or set required participants to 2 or more. |
| SharedThreshold with Instant pattern is unsupported. | Use Hold or Multi-Tap pattern for shared threshold routes. |
Related Guides
Validation Workflow
- Open the target definition and fix structural warnings first: missing point ids, duplicate ids, empty command ids, invalid variant ids, and invalid composite shape.
- Fix input warnings next: missing command input, wrong input value type, missing More/Back input, or missing cancellation input.
- Fix prompt and payload warnings after the command surface exists.
- Fix runtime warnings last: missing point binding, stale save id, authority-only call on client, route mismatch, or replicated layout mismatch.
When Validation And Runtime Disagree
Validation can confirm authored structure, but runtime state can still block a command through requirements, cooldowns, busy state, disabled state, focus scoring, route state, or authority validation. When authored data validates but play still fails, switch to the runtime pages: Interactor Flow, Focus And Spatial Queries, and Networking And Authority.