DotGraph Proofing Format

If rendering of the graph fails (i.e., you only see the dot source file) or you need the output in a different format, the dot source can also be rendered using the free desktop program Graphviz, or rendered online at GraphvizFiddle or WebGraphviz.


Notes: The start node is double-circled, as are any unreachable nodes. Traced nodes are hex-shaped. When color is on, nodes that are linked but do not exist are colored white. When color by length is on, all other nodes are colored in shades of red (shorter than average) to blue (longer than average) based on the relative length of their contents.
The cluster and color by tag options use the first tag on each passage unless Use last tag is checked; optionally detected special tags are ignored in this ordering. Optional detection of an "End" tag changes the shape of "End" passages to an egg (and puts diagonals on loose ends and disconnected nodes). Optional detection of a "checkpoint" tag changes the shape of checkpoint passages to a diamond. The omit by tag(s) option omits the passage regardless of tag order.
Stray or misplaced nodes can result from the omit tags setting, or from duplicate passage names or other linking issues. The image format is SVG.
0 nodes, 0 leaves, 0 links, and 0 links per node.

Dot Source

The internal title of the starting scene should be Start. It's written in plain text, with only markdown-style formatting allowed. This scene ends with some choices, to which we navigate using internal names for the linked scenes: * Go to [[Scene 2]]. * Go to [[The End]].This scene offers readers some more choices. They can [[go back to a previous scene using an inline, descriptive link->Start]], a short inline link like [[Start]], or with links at the end like they saw before. * Go back to [[Start]]. * Go on to [[Scene 3]]. * [[You can also go to the next section using a descriptive title for the reader.->Scene 3]] * [[Scene 2a<-You can format the longer link in either direction.]] * Go to [[The End]].A digression. * Go back to [[Scene 2]].Feel free to structure your story in Scrivener as you wish. You can put all your scenes at the top level, or divide them into sections and even subsections. All text sections will be complied into story nodes. Any folder names and notes will be ignored. * Read about [[story formats|Scene 4]]. * Go to [[The End]].Twine's story formats control the final appearance of your story, as well as any gamebook scripting (e.g., variables to track your character's hit points or inventory, etc.), even down to the details of italics and indentation. Most story formats use Markdown formatting, e.g., single asterisks to indicate *italics*, double asterisks for **boldface**, and double tildes for ~~strikethrough~~. Some story formats, such as SugarCube, use their own formatting language. SugarCube formatting is based on TiddlyWiki markup, and uses double slashes for //italics//, double apostrophes for ''boldface'', and double underscores for __underlining__. * Go on to [[The End]].The End is nigh! ''The end.''