By default Twine 2 only looks for double square bracketed sequences when creating its story map connection arrows.
Examples of the DSB link markup variants:
/* "Home" is both the passage name and link text. */
[[Home]]
/* "Home" is the passage name, "Go home" is the link text. */
[[Go home|Home]]
[[Go home->Home]]
[[Home<-Go home]]
You didn’t mention how you’re actually creating links, but we can assume you aren’t using any DSB links, or look-a-likes, since connection arrows aren’t being generated for your project.
Let’s assume you’re doing something like the following:
<<link "Go home" "Home">> … <</link>>
That won’t cause Twine 2 to generate connection arrows by default because there aren’t any DSB sequences there.
All is not lost, however, as many of SugarCube’s macros that accept passage names, for whatever reason, also accept a syntax that’s exactly the same as the DSB link markup. For example, the previous <<link>><</link>>>
can also be written as:
<<link [[Go home|Home]]>> … <</link>>
That DSB sequence will be seen by Twine 2’s default link identifier and a connection arrow will be generated.
Alternatively. If you don’t want to adjust your links to use DSB sequences, then you could add comments with DSB sequence in them. For example, the following also generates connection arrows:
/* [[Go home|Home]] */
<<link "Go home" "Home">> … <</link>>
The reason that works is because Twine 2 doesn’t actually understand what it’s seeing, it simply looks for DSB sequences. The sequences could be:
- actual DSB link markup,
- the DSB syntax accepted as an argument to macros,
- a completely nonfunctional comment,
- or even, erroneously, a nested array literal—e.g.,
[[2, 4, 8]]
.
Twine 2 can’t differentiate, so they all get collected and connection arrows generated—maybe even passages created.
PS: I’m serious about the last sequence example above, if you ever need to nest arrays put spaces between the square brackets so that they don’t form a DSB sequence—e.g., [ [2, 4, 8] ]
—or you’ll be fighting Twine 2 over creating a passage based on it.