Common Issues

Even well-structured stories can sometimes fail checks or behave differently than expected. This article lists the most common problems encountered during testing and publishing, along with their likely causes and solutions.

1. Missing Backgrounds or Media

Symptom: A scene loads with a blank or black background.
Cause: The background image was deleted or not assigned.

Fix:

• Open the Scene Settings and assign a valid background.
• Verify the file exists in the Media Library and passes upload limits.

2. Orphaned Scenes

Symptom: A scene is never reached when playing the story.
Cause: No triggers or transitions lead to this scene.

Fix:

• Use the Scene Checks to identify unused scenes.
• Create a transition or dialogue action that links to it, or remove it if obsolete.

3. Unreachable Dialogues

Symptom: Some dialogue options never appear.
Cause: The dialogue option is hidden behind conditions that are never met.

Fix:

• Recheck related variables or flags.
• Use the Debug Menu to toggle variable values and confirm visibility.

4. Missing Descriptions or Screenshots

Symptom: The release fails Marketplace checks.
Cause: The story lacks required metadata (e.g., description length, tags, screenshots).

Fix:

• Open Story Settings → Marketplace.
• Add a description (at least 300 characters), three screenshots, and three tags.

5. Incorrect Age Rating or Content Warnings

Symptom: The story is flagged or rejected during review.
Cause: The selected age group doesn’t match the story’s content.

Fix:

• Review the Content Guidelines.
• Adjust the age group and check all applicable content warnings.

6. Story Fails to End Properly

Symptom: The story continues indefinitely or loops unexpectedly.
Cause: The final chapter doesn’t have a completion trigger.

Fix:

• Add a Chapter Success action at the end of the last chapter.
• Test with the Story Preview to confirm credits appear correctly.

7. Unused or Broken Items

Symptom: Items exist but have no visible use or effect.
Cause: Missing crafting recipes, item triggers, or inventory checks.

Fix:

• Verify that each item is referenced in an event, crafting recipe, or condition.
• Remove unused items to keep the project clean.

8. Variable Mismatch

Symptom: Logic doesn’t behave as expected (wrong branches trigger).
Cause: Wrong variable type or incorrect value set.

Fix:

• Recheck actions that modify the variable.
• Use the Debug Menu → Variables to confirm live values.

9. Scene Transitions Not Working

Symptom: Player gets stuck after a choice or click.
Cause: The trigger or condition linked to the scene transition is invalid.

Fix:

• Verify that the Actions contain a valid “Go to Scene” step.
• Use the Logs tab in the Debug Menu to confirm trigger activation.

10. Checks Not Passing After Fix

Symptom: An issue still shows as “Failed” after fixing it.
Cause: The check results are cached.

Fix:

• Click Run Checks again to refresh validation results.
• Ensure all related content has been saved before rerunning.

11. Release Not Progressing to Manual Review

Symptom: The release remains in “Automated Review.”
Cause: Unresolved Failure-level issues in Checks.

Fix:

• Open Checks and resolve all listed failures.
• Resubmit the release once the story passes validation.

12. Missing or Incorrect Content Flags (AI)

Symptom: The story passes checks but fails moderation.
Cause: AI-generated assets were not disclosed.

Fix:

• Reopen Story Settings → Content and enable the relevant AI flags (e.g., “AI Images” or “AI Voices”).
• Resubmit the release.

13. Collaborator Changes Not Reflected

Symptom: A collaborator cannot edit or access certain parts.
Cause: Permissions were not updated after adding the collaborator.

Fix:

• Open Story Settings → Collaborators.
• Ensure all relevant permissions are enabled, then click Save Changes.

14. General Best Practices

• Always run Editor Checks before creating a release.
• Use the Debug Menu to confirm logic and inventory behavior.
• Keep metadata (description, age rating, tags) complete and up to date.
• Re-run checks after any major edit to ensure compliance.

These are the most frequent problems reported by Bards and reviewers. Fixing them early ensures your story passes validation smoothly and reaches Dreamers without delay.