Hello, all,
I am so frustrated now but I don't know what I'm doing. I have looked through questions all over this forum and none of them seem to apply to this.
When I try to save my Twine story ("Publish to File,") I get an HTML file. When I open it (I have Chrome), I get a wall of text. All the text in my story, in fact--and none of it is code. Just all the text, all stacked up. I thought I must have been opening it wrong or something, because it will work alright when I click the ladybug to test or play the game in the editor itself, but somehow all I can get when I open the file outside Twine is a freakin' wall of text.
I thought I was just stupid and tried uploading it to philome.la to see if it would turn out then, but when I dragged the file in I got a message that I didn't appear to be uploading a Twine file.
What am I doing to make this happen? I just downloaded Twine today (2.0.6) and I have a PC and Chrome and I don't know what else to tell you.
Sorry if this is the dumbest question anyone has ever asked on here.
Comments
Can you upload your story here so that I can help?
I work for an academic camp and the story isn't my work--it's my students'--so I cannot legally upload it.
If this means no one can help me without the file I understand. But it's all the text I entered into all the boxes with no sign of code or direction, and it's the entire story (every option) at once with no formatting or anything.
Like @Sage suggested, I'd suggest attaching the HTML file here. I cannot imagine a copyright infringement issue. It's a textbook example of fair use. If needed, PM it to me. Anyway, you already were going to upload it to philome.la, which would have been thousands of times more public than this forum! ;-)
Also, can you try to make another game from scratch real fast? Just make one or two passages, then export like normal. If it doesn't work, attach that HTML file instead.
I noticed someone else had this issue. Might be something very simple, but I just don't know what it is. Sorry.
Great idea.
Great question.
I tried Harlowe, Snowman, and SugarCube and changing between those didn't change the output.
When I save the file it saves it as whatever name I gave the story .html, so no numbers or "Twine Archive" language in the filename.
A test story that displays the same issue is attached.
http://superheropress.com/margaret/
Dunno. No idea why it works for Sage, either. Sorry. :-(
Try that Margaret.
Whatever glitch she hit the first time, I avoided by trying it again.
Where are you getting the "published" file? If you're using the executable version, and you're grabbing the file out of the Twine document directory's Stories directory, then that's the problem. The Stories directory is where Twine 2 stores your story archives, not published stories.
I was trying to get my files from a folder named "Twine" that showed up in "My Documents" today, but apparently I needed to be getting them from somewhere in "App Data."
Thank you all for putting up with me!!!!
Using App Data probably only works because it is your local (in-editor) copy. You will have dependency issues that way, I'm almost certain.
If margaret is using the browser-based version, then yes that would have to be the case.
On the other hand (as I said previously), if they're using the executable version (the NW.js-based version) then Twine 2 stores your story archives in a directory on your system (rather than in the browser, as the browser-based version has to do). So, if they're thinking that they are supposed to grab their stories from that directory, what they'll actually be getting is the archive for that story, rather than the published file.
They said "I just downloaded Twine today (2.0.6) and I have a PC", which I'm assuming means they're running the executable (NW.js-based) version in Windows. If that's true, Twine 2 should have created a Twine directory, within their Documents directory, which contains a Stories directory, which contains their saved story archives (saved normally, not via the Archive menu item, which creates an archive of all your stories).
Make sense?
You should get it from wherever you published it to. The Publish story menu item opens a standard Save As dialog, so you can choose where to save the published file. Just save it to your desktop or something. There's no need to go spelunking into your AppData directory unless that is where you saved it.