Twine Version: 2.3.5
Story Format: Harlowe 1.2.4
I realize this is a very general question, so I’m mostly looking for a starting point for solving any of these issues and suggestions on any resources that might explain them better.
I am working on a story that I anticipate will become big enough to slow down the interface in Twine (I’m at around 300 passages and barely in the beginning of the first chapter) and although the story I planned out is quite big, I suspect a large amount of the passages in the project are unnecessary. I have implemented features that I like and I have been able to make things work on a surface level, but I feel that I lack “common sense” when it comes to the code.
For example, I have many instances where Passage 1 will lead to an “invisible” Passage 2 that only exists to execute code before moving on to Passage 3, which I’ve read somewhere is bad, though I wouldn’t be able to say why. I would change this if I only knew some other way. I also tend to use if/else statements to solve everything I want to do with the game, which feels excessive. I’ve spent time reading the wiki of course, but it does not offer much context in terms of efficiency.
In other words, the game functions almost exactly like I want it to at the moment, but if someone more experienced looked over the code, I’m sure they would start feeling nauseous real fast. And my worry is that if I keep going with the same method, it will cause problems down the line and I’ll have to overhaul the entire thing to make it work.
Currently I am looking into using grunt-entwine-quickstart to eventually combine multiple stories and hopefully export it as a desktop application. I’d be interested to hear from anyone who has done this or used a similar method.
I’m pretty set on using my current story format as it is the only one where I can get backgrounds, audio and video to work and it’s the only format I’m familiar with. It is also the version I used when I created the structure of the game. If using the newer version will be easier in the long run I’m open to changing it provided it doesn’t fundamentally change too much in terms of how the coding works or mess up the work I’ve already started.
I suppose the most important questions are 1. Can I export variables between separate html files to save player choices and 2. Is there any resource for Twine specifically where I can find basic “do’s and don’ts”, such as how many if/else statements are acceptable within a passage and so on.
Otherwise I’m interested to hear viewpoints on how to best structure a story with many variables and passages without slowing down the interface too much.