Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Story Map not linking

I'm new to twine. I just made a node with this construction. The node works fine, but the Story Map doesn't show the path that links to the next node, "Picking Flavors". I could probably live without it... but my 11-year-old daughter can't. Any suggestions?
You say:

(link: "cup")[(set: $container to "cup")(goto: "Picking Flavors")]
(link: "cone")[(set: $container to "cone")(goto: "Picking Flavors")]

Comments

  • Just clarifying. This is in Harlowe.
  • edited July 2016
    The Automatically Create Missing Passage(s) and the Show Passage Connections for Passage Links features of the Twine 2 application only support Standard Markup based Links.

    eg. Text and Target the same or Text->Target or Target

    Each Story Format has different ways to create passage links and currently the Twine 2 application only supports the ones that are common to all Story Formats.

    Some people have worked out "tricks"or "hacks" to fool the Passage Connections feature in to showing arrows for Macro-based and Advanced Markup based links but I can't find the relevant threads.
  • I've come across this - my work around is to have an invisible link at the bottom of the passage which will create the map link - i.e.
    (link: "cup")[(set: $container to "cup")(goto: "Picking Flavors")]
    
    <!--Invisible link to link to the continuing passage in the story map-->
    [[ |Picking Flavors]]
    

    I've seen other examples where people wrap an if around the 'invisible' link to ensure it never shows, probably better practice to be honest.
  • I guess I'll wait until the app has caught up with the language. I shouldn't be in workaround territory within 20 minutes of writing my first passage... Back to Inklewriter. :-(
  • jaylender wrote: »
    I guess I'll wait until the app has caught up with the languages. ftfy
    Each Story Format defines it's own macro language syntax and list of available macros (if it has a macro language), it also defines the HTML structure and default CSS used by the story and it's engine, and all other features available to the Author.
Sign In or Register to comment.