Noticeable bug fixes and minor changes:

• Fixed save corruption issues relating to improper save version checking
• Main menu changes
• Seperated the continue button and the new game button
• Added a label to tell you which mission you are loading into pressing continue
• Changed the continue button to "Start Next Mission" when there is not a current level save and there is an uncompleted "next level" to be played
• Scroll buttons now grey out when the maximum scroll in that direction is reached
• Scroll buttons now scroll more with a single press (when applicable)
• The test sound button now has a cooldown
• Fixed music preview in the First Time Setup (Was also causing music in game to not function properly)
• Fixed an issue where the current objective would not activate when loading a save in M1

Known Issues:

• Reloading a save between different mission objectives at the train station will cause the battle music to not trigger
• There is a jitter in the animation for cancelling the standard staff melee combo
• Buffs run their timers during cutscenes

Dev Note:

This is a bit of an emergency update, since I noticed a super major issue when making updates to the first time setup screen. This issue is the save corruption issue in bold.
Technical explanation: This occurred in two situations, one required going into the game's save folder and deleting VersionInfo.dat, but the other is as simple as going through the FTS screen and restarting the game. The games version was written incorrectly when completing the FTS screen, which then would run a script to "update" the Stages.dat file, delete the current stage progress file, which, since the Stages.dat would be corrupted.
I apologize for the troubles, if you suspect your save file was corrupted (Usually shown by disappearing high scores), the player count is low enough I could probably manually fix it if you reach out to me on whatever platform is easiest for you.
In addition to fixing this, some features and fixes coming in the next major update were instead added here. Once again, I'm sorry I didn't catch this sooner, or the issue with loading M1 saves.