DialogueCheckAuthoring
Review draft. This source page has not completed website editorial and release-specific verification.
# Generic Check Authoring
Dialogue Director 2.1.0 authors semantic check intent only. The selected external provider profile owns resolution mechanics.
Definition fields
Section titled “Definition fields”FDialogueCheckDefinition contains:
- ResolutionProfileId: a stable FName-based identifier, not an asset reference.
- ValueSourceKey and BaseValue: semantic source key and authored value.
- SkillId and SkillParticipantRoleId: used when ValueSourceKey is Skill and Dialogue must acquire a Skill value from the participant in the current frame.
- Comparison, Target, and RangeEnd: neutral comparison semantics.
- ScalarInputs: ordered named finite scalar values forwarded to the provider.
- SuccessOutcome and FailureOutcome: Dialogue-owned semantic outcome identifiers.
FDialogueCheckNodePayload adds the stable CheckId, retry policy, optional retry reset condition, and node identity. Dialogue owns routing and retry state. No separate mechanics-specific Check or Skill Check definition exists.
The authored model contains no dice type/count/sides, advantage, probability percentage, random range, rules object, stream mode, decision policy, bias, or provider status field.
Authoring and validation
Section titled “Authoring and validation”ResolutionProfileId is always editable as a stable identifier. Dialogue structural validation checks its form and the neutral Check fields; it does not query a Bridge or provider registry. A project can author a profile ID before installing an integration. If an optional Editor provider is present, its profile picker, profile validation, descriptions, summary and search additions are shown as separate provider-owned metadata. The canonical authored value remains the profile ID. Unknown authored IDs remain intact and editable.
When ValueSourceKey is Skill, the author supplies the exact Skill identity and participant role. Dialogue obtains the current Skill value through its optional Skill query seam and passes the value to the provider. Dialogue does not store or modify Skill state.
A Check node has success and failure routes. Only a resolved provider outcome selects one. ProviderUnavailable, invalid request, rejected, failed, missing participant, or unavailable Skill produces a structured execution failure and does not take the authored failure route.
Retry identity
Section titled “Retry identity”Check retry policy is attached to the graph node. Dialogue preserves DialogueId, ContextKey, OperationId, ActivationScope, and AttemptIndex in the neutral request identity. Retry attempts preserve activation scope; AttemptIndex advances only as allowed by Dialogue retry semantics. Retry state is Dialogue-owned and persists in Dialogue snapshots.
Editor and preview
Section titled “Editor and preview”The base Dialogue Editor exposes generic profile, semantic source, comparison, target, scalar-input, outcome, and retry fields. Search and graph summaries include the profile identifier. An optional IDialogueResolutionEditorProvider may supply display data, additive validation, summary text, and search terms. Provider errors are clearly labeled as provider validation and do not change the owner structural-validity result. Copy/paste preserves structural references and authoring semantics.
Preview can inspect structure, comparison/target, Skill source, routing, and profile ID. It does not calculate chance, sample random values, evaluate rules, or simulate provider mechanics. Rich Probability authoring and preview belong to the optional DirectorBridgeDialogueProbabilityEditor.