0 votes
by (120 points)
edited by
When I go on twinery.org it loads normally, but when I press use it online it's just a white screen. It doesn't load or anything. It's frustrating because I now can't access 5 weeks of work. Anyone have a fix? Edit: I was able to access it through the wiki, but then all my stories were gone. Still at a loss.

1 Answer

0 votes
by (68.6k points)

The online release of Twine 2 stores your project data in your browser's local storage—specifically, Web Storage.  Anything which clears your browser's local storage, will delete your project data.  The only way to be sure you do not suffer data loss in the online release is to routinely use its archival feature—the Archive item in the sidebar.

That said, it may simply be a protocol issue.  You can access the online release of Twine 2 via both the HTTP and HTTPS protocols.  Each receives a separate local storage instance from the browser, so it's important that you use the exact same URL when accessing the online release, elsewise Twine 2 won't be able to see your data.

Here are relevant URLs.  Try both to see which may have your data:

If you're simply getting a blank page with one of those URLs, try forcing a reload—commonly bound to F5, among other things, in most desktop browsers today.


PS: If you've ever used Publish to create a compiled version of your project and still have one of those files around, then, all else failing, you may import that to recover, at least, some of your project.  Though I'd save that as an absolute last resort.

by (120 points)
Well the https did work. But all of my work was stored on the http link.
by (100 points)
I'm actually having the same problem; when I click 'use it online', it loads onto a completely blank page. I tried those links out of curiosity, the first didn't work, and the second opened the library but without anything in it. Help would be much appreciated, thank you!
by (68.6k points)

To both chiba & samakther.

Twine 2 was recently updated to version 2.2.0, which includes the online release.  Did you try forcing a reload on the HTTP URL?  It's possible that your resource cache is out of sync with the current version.  If that is the case, forcing a reload could fix it.