Hi! I'm super new to this (as in just started using Twine today) with incredibly basic CSS/HTML knowledge. I''m trying to make something that doesn't really use complicated variables but still incorporates past "knowledge." So, my workaround involves using (if: (history:) contains "xyz" [] like so -
Merry1
-"Merry1" will give you a description of the woman with the option to go back, where you would then see the following -
(if: (history:) contains "Merry1") [The woman has now noticed you.]
I also figured out to get that to work with links, thanks to other helpful threads on this forum.
The only problem - besides not knowing how to make the history reset if I were to send someone back to the beginning, which is a problem for another day - is that when I test it out, there's a big blank space where the text is going to appear. While I guess that would forecast that the player needs to click on things to make sure that space is filled, is there any way to hide it to make it look more natural?
Thanks in advance!
Comments
But from what I understand of what you are saying, you can try to use the (if:) macro first with an (else:) for the text that is normally displayed. You can also use the { and } brackets at the start and end of the code, and that would/should deal with your space issues.
Here's what I mean:
I have attached a HTML file for you to check out and see if it works the way you want it to.
For example in your "beginning" passage you could put:
Then in your other passage (that has "A grinning youg woman...") you would set it up like this:
And in Merry1 you would add the following code (along with the link going back to the previous passage):
That way, each time you send someone back to the "beginning" passage, the $merry variable is reset to false, and they would have to go through to Merry1 again before seeing "The woman has now noticed you."
There is probably a way of resetting the (history:) or removing certain passages from it, but I am not familiar with that method, which is why I am suggesting a simple variable based one.
For most stories this may not cause a problem because generally they don't have than many passages within the Readers path through the story, but if you are planing on creating a RPG or a story that has long paths then it can become an issue if (history:) is used too often.