It seems like maybe a <<nobr>> is missing? Considering you added the timer on the settings page, is the <<nobr>> missing from the statement for that? I'm not super familiar with Twine's language, so guessing here
Viewing post in v1.1: Mobile compatability, timer, and cheat mode comments
Yeah, there are 3 types of code I can use:
HTML macros, which look like <br> and <div>
Twine macros, which look like <<if>> and <<nobr>>
And javascript commands, which look like Math.round().
Of the first two types, some macros are alone, like <br>, and some require closing statements, like </div> and <</nobr>>. Specifically, there has to be exactly 1 closing statement for every opening statement, otherwise it'll show an error. It may still work as advertised, but that big red box is pretty distracting.
I know I put a <<nobr>> there after seeing the error the first time, but I bet I put it slightly out of place, like [( ]). Totally wonky
Kind of. Both halves are present; it's that they can't see each other.
All of the braced statements can be nested, but you have to put both sides in the same container. For instance, this would work perfectly fine:
<<if>>
<<nobr>>
<</nobr>>
<</if>>
But this would break (and already did, as you just saw):
<<nobr>>
<<if>>
<</nobr>>
<</if>>
Even if the if statement is true, it checks for errors and for when it needs to stop considering the <<nobr>> before actually evaluating it. I'm not sure exactly what form this problem takes in the settings screen, but I need to recount the <<if>>s and <</if>>s used to say "minutes" and "hours" only when you have a plural amount of them.
This game would've been beyond impossible if I didn't have a sudden inexplicable drive to make this the best damn BE game you ever did play halfway through. Everything you expect to be simple, that you don't even think about when you see it, probably took over a whole page of code. Nothing "just works", everything takes a stupid amount of background work to assemble all the pieces that wouldn't be nearly as much trouble if it didn't have to adapt to an ever-changing value.
Except the commas in the numbers, apparently that's just <<=$size.toLocaleString()>> with javascript and it just fucken works. Bit of a shame, too; I'm pretty sure I could do that with my own code by using rounding and logarithms.
I feel the pain. I'm glad you were able to persevere through such a limited engine to make such a wonderful game, I installed Twine myself and while it seems easy on the surface it for sure is complicated.
If the two snips you mentioned do not work:
- <<if>>
- <<nobr>>
- <</nobr>>
- <</if>>
and
- <<nobr>>
- <<if>>
- <</nobr>>
- <</if>>
Would this one work?
- <<nobr>>
- <<if>>
- <</if>>
- <</nobr>>
I saw you had a reddit, gonna message you on there so we don't clog your games update threads up :)