Creating & Publishing
Map and Playtest
Map helps you inspect story structure, while Playtest lets you follow the authored routes before readers encounter them.
On this page
Summary
Map helps you inspect story structure, while Playtest lets you follow the authored routes before readers encounter them.
Steps
- Open Map after adding chapters, scenes, and choices to see how the destinations connect.
- Look for passages with no intended incoming path, choices with missing destinations, and loops that do not lead to a planned continuation or ending.
- Start Playtest from the beginning and select every choice at least once; revisit branches that set or check conditions.
- After edits, rerun validation and a short Playtest from the affected decision point.
What to expect
- A branching map can contain intentionally optional passages; judge reachability against the story you intended to write.
- Playtest helps find route problems but does not replace careful reading, accurate content labels, or Admin review.
- Review submission is not publication: only the version approved by Admin becomes the public story.
Troubleshooting
- If the map is difficult to scan, inspect one chapter group or branch at a time and use clear passage names.
- If Playtest appears stuck, note the last passage and choice, reload the draft, and repeat that same route once.
- If a route error persists, send Creator Support the passage names and expected path rather than a private account token.