Howdy, Stranger!

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

A few things missing...(images, StoryInit, memory limit)

I've been playing around with Twine 2 recently, and for the most part I am fond of the changes, especially to the interface, which is now gorgeous. There are, however, a few features from Twine 1.4 that I'm missing, and I just wanted to find out if I am, indeed, overlooking something, or if these were taken out.

-Images: I really appreciate the ability to embed images in Twine 1.4, and am making heavy use of this feature in my current projects. It has made managing visuals relatively hassle free and straight forward, at least for me. Has this feature been removed from Twine 2? If so, would I just have to reference image files the old fashioned way (<img src="...)?

-The StoryInit special passage: I know that most of the special passages have been rendered redundant, but this one has a very important practical purpose, in my opinion, especially in more complex games/stories that make heavy use of conditional logic. Is there a way/place to initialize my variables and etc.?

-The Size/Space Limit: This isn't something that's missing but is rather something a bit undesirable that's been added. Anyone out there making large, complex stories? Has it ever been a problem so far? If so, is there a way around it? It makes me uncomfortable that there's a literal, physical limit to how big I can make my piece, even if the confines are fairly generous.

Any info on one or all of these issues would be very much appreciated. I've read a bit about the latter problem (mostly just hoping to hear directly from creators who are actually dealing with it), but have been having a hard time figuring out the first two.

Comments

  • The SugarCube story format still supports using a StoryInit passage to initialize your variables, all you have to do is create and correctly title the passage yourself.
    When using the Harlowe story format you can initialize your variables in the first passage, you can do something similar when using Snowman 2.

    The browser defines the default size limit of it's local storage (5-10MB), which is where Twine 2 stores the projects your are developing.

    Most, if not all, Twine 1 projects that have a TWS file size larger than this limit are that size because they are embedding images within the project's file(s). Projects of this type generally run into memory errors when trying to build the HTML file, and the main way to get around this memory issue is to not embed the images and to use external files instead. The browser local storage limit is what stops images being embeddable in Twine 2.

    All three Twine 2 story formats support the use of external images. SugarCube has its [img[]] markup, and all three story formats support the standard HTML <a scr=""> tag.
  • Thanks! That answers it all, I think. Embedded images were nice to have, but I can live with external files. There are even some advantages. Good to know about StoryInit in SugarCube. That's likely the format I'll be using most often anyway, so it works out well. Thanks a second time for the quick and thorough response!
  • What would be a nice feature, is it is actually possible, is if the code behind the "Publish to File" option was able to embed your external images within the HTML file it is creating, this would get around both the local storage and the packaging external image with story HTML file issues.
Sign In or Register to comment.