Troubleshooting
Review draft. This source page has not completed website editorial and release-specific verification.
# Troubleshooting
A Check reports ProviderUnavailable
Section titled “A Check reports ProviderUnavailable”Dialogue Director 2.1.0 has no local random fallback and does not require Probability Director. Confirm that the intended external provider is installed and registered for the same GameInstance. The optional canonical Probability integration is DirectorBridge Dialogue.Probability ContractVersion 3.
Without any provider, ordinary conversation flow remains available. Checks, random branches, and weighted Dialogue Sets stop with ProviderUnavailable. They do not take an authored failure route, choose a candidate, or consume a retry attempt.
A Skill-sourced Check cannot resolve
Section titled “A Skill-sourced Check cannot resolve”Confirm that ValueSourceKey is Skill, SkillId is an exact valid Skill identity, SkillParticipantRoleId exists in the active Definition, the role is bound to an Actor in the current frame, and the optional Skill query bridge is registered. Missing context produces a structured acquisition failure and does not dispatch a substitute value.
A profile ID validates but the provider rejects the Check
Section titled “A profile ID validates but the provider rejects the Check”Base Dialogue validation verifies identifier structure only. It does not query the provider registry or assert that a profile is configured. Verify the profile name and its mechanics in the installed provider integration. The provider returns an explicit rejection or invalid-request status when its own profile contract is not satisfied.
JSON import reports unsupported schema
Section titled “JSON import reports unsupported schema”The current DialogueDefinition interchange schema is version 3. Earlier unreleased shapes are not migrated. Export a current document from the asset and apply changes to that canonical representation.
Snapshot restore requests participant rebinding
Section titled “Snapshot restore requests participant rebinding”Dialogue snapshots do not serialize Actor or UObject references. Rebind all captured root participant role IDs before resuming traversal. Nested SubDialogue bindings are reconstructed from their saved caller/callee mappings.