Update 1.2.5

Patch notes:

- Added option to unequip equipable items

- Permanently fixed issue where the user was, under some conditions, able to select "Continue" despite not having a save file, resulting in a softlock on the title screen

- Attempting to interact with the crystal switches used in a handful of puzzles several times consecutively in a short time frame would crash the game. This has been fixed.

- Players were forced to rewatch a late-game cutscene (and walk through the area leading up to it) if they failed to defeat the boss that followed said cutscene. This has been changed, and players are now able to face the boss without having to replay the part leading up to it.

- Interacting with a tree found in the game's first area at a specific point in progression would crash the game. This has been fixed.

- In two particular character interactions, your previous inputs would, under some conditions, influence the dialogue of the character you were talking to, leading to dialogue from different "branches" being mixed up. This has been fixed, and one new line of dialogue has been added for one of the dialogue choices to make the end of the conversation feel less abrupt.

DEVELOPER NOTE:

I received an email about a game crash that would occur after obtaining Tay's old guitar from the mayor, then going to the diner and asking for a glass of milk. (Thanks again for the report, by the way!) 

However, after having played through the opening and performing a variety of different actions prior to the point where the game is "supposed" to crash, I was unable to replicate it on both the Steam and Itch builds of the game. If anyone else is able to replicate this from a fresh save file, I would love to hear how you were able to get it to happen. Until I'm able to find the exact cause of it, I won't be able to fix it. Even looking through the code, I'm unable to see how the error that was spat out was even produced. It could be a machine-specific thing. I've tried this on both my PC and laptop, and my playtesters have run into no issues regarding the interaction.

(For anyone who's encountered any major bugs, feel free to get in touch via bootcatstudio@gmail.com! )