#status: fixed

[valiant-if]

To the anon that reported the isn't/aren't mistake: I accidentally deleted the ask, but thank you for the report! The mistake in question is related to pronoun plurization, so I either forgot to code it in or coded it incorrectly. I will take a look and fix it for the next update. Thanks again!

[valiant-if]

Little coding(?) thing on this choice

[[Because the crew of the Valiant holds all the cards here.|ch2.switch2bb][aggressive to "distrustful]]

Hi, anon!

I know which passage has the choice in question, but the text I have in the Twine file doesn't match what you've sent me, so I'm not quite sure where the error is yet. Are you able to send me a screenshot of what you're seeing?

[valiant-if]

I'm on a new save, and getting a different kind of error in the same spot as people were getting on old saves. The option to mention talking to Switch is jumbled code and not clickable. It's still not clickable even after progressing through the option that is available, so the game is stuck after the first conversation.

Hello!

This was due to some missing code within the link that caused improper formatting. I've fixed the link in all variations that it appears, and you should be able to advance through that choice now. Let me know if it still gives any problems.

Funny thing is, I actually caught this bug a week or two ago, but apparently I only fixed it for the Timid response and not for any of the others. Woops! 😅

Thank you so much for the report!

[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!

[valiant-if]

Hi!! I literally just found you, and I was so lucky, because I really really liked the demo😍 I just wanted to tell you that I think I found a problem with coding (at least I think it's coding, I don't know anything about that😅): in the choice to agree/disagree with CAIT to attract the attention of the Captain, the scenarios of "agree with her, but she needs to ask permission" and "disagree with her but can't tell her what to do" are inverted. I'll put the screenshot too to be more clear.

Anyway, thank you for your work, I'm really looking forward to reading the next part ❤️

Hi! I'm so glad you enjoyed the demo, thanks for reading!

And thank you for letting me know! I had a Twine bug a while back that caused some issues, and I bet that happened when I went to fix them. I will take a look and get that fixed very soon!