#valiant error reports

[valiant-if]

howdy, not the original person btw |˶˙ᵕ˙ )ﾉﾞ

No idea if you've found it or if this is useful in the slightest but I started from the beginning

The top one says

Error: cannot find a closing tag for macro <<if>><<if $path_romance isnot 0>>…

Don't know if it's useful because this is essentially wizardry for me ¯\_(ツ)_/¯

Was just looking at the choice that leads to the above and encountered the below when I hit "We don't have to talk about that. We can talk about something else."

Well, I just really like this story and I really like the characters too

sorry if this is barely coherent lol

This is so helpful, thank you so much! 🤗

Now that I can see it, the second screenshot is probably the one the report was about. I had a hard time pinpointing it because this one-on-one has a lot of different roads to reach the same passages, so I just didn't go down the right ones in my testing. But, hey, you found a second error too! (It's crazy what one extra letter in a macro will do to the entire passage's code.)

Thank you again for finding this and sending it to me! And Also for your kind words; I am glad you are enjoying it so far.

For anyone encountering these errors, I have fixed them in the public demo already, so you should be able to play through this scene without issue. These fixes will be included in the early access demo update this weekend.

[valiant-if]

Re: Error Report

Hey, all! I very recently got a report regarding the public demo of an error in the Path conversation branch at the end of Chapter 2.

Unfortunately, the error report didn't give me the details I need to figure out what the actual issue is. It was marked as a continuity error, but then the report mentioned two of the choices were marked red in error without any mention of the error message being received. In my testing of the issue, I was not able to replicate anything described by the report, so I'm responding to it here in the hopes that I can either pinpoint the issue or offer some advice. So:

1.) Has anyone playing on either version of the demo noticed any error messages popping up in Path's end-of-chapter-2 scene? If so, can you copy and paste the error message into the error report form or send a screenshot to my askbox here on tumblr? I've been scouring the scene to try and replicate any similar error but haven't gotten anything on my end, but maybe I'm not looking in the right place.

2.) On the chance that no one else is having this error and the person who sent the report is active here: make sure you are playing through on a new save. My best guess for why you would be getting the error and I am not able to replicate it is that your save file might be running off of an outdated variable list, which can cause havoc with the coding. If your save file is brand new and you're still getting the error, please resubmit the error report with the exact error message copy-and-pasted or send a screenshot to me here on tumblr!

Thanks so much for the help!

[valiant-if]

Patch Released!

Hey, everyone! I've updated the demo with a fix for the personality calculation. I also identified a secondary error that prevented "stoic" from being assigned as the main stat entirely. This too has been fixed.

As an aside note, a tiebreaker scenario is something that is on my to-do list for the future—I already have the code written for it but need to find the best place to implement it. For now, if two stats are tied at the highest stat, it will default to whichever one comes first in the widget. That order is timid > friendly > aggressive > flippant > stoic.

Enjoy! Thanks so much to the person that reported that initial error!

[valiant-if]

Hey, everyone! Someone reported an error that's pretty detrimental since it involves a typo in the code that calculates your highest personality stat; this is used a lot in the ch2 aftermath scenes. I've identified the issue, but Itch.io seems to be down at the moment (or at least I can't access it right now). I will update the demo with the corrected code as soon as I'm able to.

[valiant-if]

Hey all! I've received the following error report through forms:

For the benefit of those who don't read the changelog notes:

This is known error when using an old save. You must start a new save or you will encounter this error. It's a result of old Twine variables and new Twine variables not matching up. The only fix for it is making sure to start a new save. Before I released the public update, I tested it myself on an old save and on a new save and confirmed that this does not happen on new saves. If you are on a new save and it still happens for you, you may need to clear cookies in your browser to make sure it isn't saving outdated information. Beware, however, that this will erase saves from any Twine or Dashingdon games that you play!

As a general rule of thumb, if you encounter any strange errors when playing a new update, it helps me out a lot if you make sure the error can be replicated (or not) on a brand new game.

I know having to play a new save every single time there is an update can be a pain, but sometimes there is no way around it during development of a Twine game. Generally, if I know for sure that old saves will cause problems, I will let you know in the changelog, so make sure to check it before you play to save yourselves some time!

Thanks to the individual who made the report!