Twine Version: 2.3.9
Story Format: Sugarcube 2.33.0
I couldn’t find anyone talking about it so I don’t know what would be causing it, especially since its not doing anything else as far as I can tell. The error appears in a white box before the passage screen loads.
Apologies! An error has occurred. You may be able to continue, but some parts may not work properly.
Error: TempState.macroTypeQueue is undefined.
Any advice on why it could be happeing, or how to force it to stop appearing, would be much appreciated. Thank you.
It’s hard to tell without seeing what code you’re using which might invoke such an error. However, since it appears that the error might be related to the
<<type>> macro, then you might want to update to SugarCube v2.33.1, which improves that macro a bit.
Code goes here.
Can include multiple lines.
Simply comment out enough that the error goes away, and then comment out less and less, until the error reappears. Whatever new bit of code you uncommented last will likely be where the error is triggered from.
Hope that helps!
Ah, you made it sound like the problem was happening at the very beginning, since you said that the problem happens “before the passage screen loads.” I assumed that meant it happened before the first passage loads.
If you need to test on a later passage, simply save the game just before the problem occurs, comment out the code, publish the game, reload the HTML (
CTRL+F5), load the save, and then go to the passage to trigger the error.
Doing what I just described should do it. However, you can’t trigger it otherwise without knowing the cause of the problem, and the cause of the problem is what we’re trying to figure out.
Basically, you need to figure out the cause, and then either fix it yourself, or if you can’t do that, show us the code so we can take a look.
Let us know what you figure out.
It’s been passed around a few times in threads here, but I’ve personally found this a great tool for troubleshooting. It doesn’t catch everything, but can catch a good amount of little bugs or typos in the code.
Just continue to narrow down the code that triggers the problem in the StoryInit passage like that.
Either that, or show us the code, if it’s not a huge amount.