Please specify version and format if asking for help, or apply optional tags above:
Twine Version: 2.3.9
Story Format: 2.1.0
Maybe I’m just not searching the right terms, but I haven’t seen anyone else asking and I wanted to check and make sure I’m not overcomplicating things.
I have a MEMORY passage: players can unlock memories and return to the passage to read them. Some of the memories are somewhat long, so to make them more readable I broke them into chunks that the player clicks to read more of. It ensures that they read thoroughly instead of skimming and helps with pacing. Originally I had this set up very simply, like so:
{text1text1text1text1text1text1text1text1text1text
<p>[∨]<memory1-2|</p>]
(click: ?memory1-2)[text2text2text2text2text2text2text2text2text2text2
<p>[∨]<memory1-3|</p>]
(click: ?memory1-3)[text3text3text3text3text3text3text3text3text3text3
<p>[∨]<memory1-4|</p>]}
But I quickly realized that doing it this way meant that, every time someone left the MEMORY page and then returned, all the text they’d previously clicked to reveal would be hidden again. I want them to click to reveal during their first read-through, but be able to leave and return and find all the text permanently revealed.
I know that I can work around this with variables - I came up with this, which I think works:
text1text1text1text1text1text1text1
<p>[∨]<memory1-2|</p><p>[]<replace1-2|</p>
{(click: ?memory1-2)[(set: $memoryone2 to "clicked")]
(live:)[(if: $memoryone2 is "clicked")[text2text2text2text2text2text2text2
<p>[∨]<memory1-3|</p><p>[]<replace1-3|</p>]]
(click: ?memory1-3)[(set: $memoryone3 to "clicked")]
(live:)[(if: $memoryone3 is "clicked")[text3text3text3text3text3text3text3text3text3
<p>[∨]<memory1-4|</p><p>[]<replace1-4|</p>]]
Is that a sensible way to handle this? Will it be a problem if I have 25 “(live:)” commands running on the page at once? Is there an extremely easy permanent click-replace command that I just can’t find? I don’t want to be overly convoluted.
My other (extremely ignorant) question is that as I was testing my new solution on my laptop, I realized that tap-clicking the “∨” worked to expand it, but regular-clicking on my trackpad did not. Only taps. I tested this in several other apps but the difference only appears to be in Twine. Is this a weird Twine thing? Twine doesn’t distinguish between types of clicks, does it?