First off I should say that I am aware there's a space at the start of my location names; that was an accident I made early on and it was easier to standardize it for the story then go back and replace every instance of the location's name.
So in debug mode this code works properly:
before (link: "departing" )[(set: $Batteries to $Batteries+1)(goto: " Atrium")]
However, after playing the published story, I get this error: There's no passage named ' Atrium'.
There is absolutely a passage named " Atrium" (space included), I hold the fact that it works in debug mode as evidence of this. I know it's not the formatting of the code, because this works just fine:
(link: "outside" )[(set: $Garage to 0)(goto: " Garage")]
Can anyone tell me what it is that I'm missing?
Maybe upload the published story and I could have a look?
Browser: Firefox 16.0.2, 32 Bit
OS: Mac OS X 10.5.8, 64 Bit
Any and all help is greatly appreciated!
This: Should be this:
I don't know why it works in debug mode (that would be a question for Leon). Personally, I'd have expected that (link markup containing a line break) to throw an error or simply fail to parse, rather than parse and try to link to " \nAtrium".
You have: When you should have:
In fact, you seem to be using hard line breaks virtually everywhere. As a suggestion, within paragraphs you should probably stick with soft line breaks (i.e. let it wrap at the window, don't use a hard line break). You'll probably end up with fewer of these gotchas.
There's other places in the normal text that don't have linebreaks until the story is published. Do I have a display setting wrong or something?
As an example of what is going on, here's what the "
Supply Closet" passage looks like in the published HTML file you posted: If you open it in a decent text editor, not word processor, you should be able to see what I mean. In fact, all your passages are, bizarrely, being hard wrapped at around 72 characters. Actually, if you have a text editor and are able to see what I mean in the published HTML file, you could also try exporting your story (via Archive in the sidebar) and looking at the exported HTML archive to see if it the passages in it are also being hard wrapped at around 72 characters.
I'm unsure if this is causative, however, you are running an old version of Firefox (v16.0.2). It could be that old-Firefox + Twine 2 = hijinks. If you tried my suggestion to export your story above and it did not contain the offending hard breaks, then you might try importing that archive into Twine 2 in a different, more up-to-date, browser as a test. If everything looks good in your story in the other browser and when published it works as intended (I'd eyeball the published HTML too), then you'll have narrowed it down to your Firefox, at least.
I just thought of something else. Do you have any add-ons installed in Firefox which might be tinkering with
Both can automatically add / replace standard characters with others.