I really can't believe that the developer has created a new game with the same old save transfer problem? Surely a solution could have been worked out by now? Perhaps a more permanent install, with a patch update for new content, could keep the download size down and enable the continuation of the saves. Or alternatively investigate how Renpy does it by creating a permanent game folder that updates in the user profile on the pc? Just a thought
This has been brought up before, more times than I care to count, so it bears repeating...
again it would seem.
Faerin has mentioned in the past (during MotH's development) that creating a permanent save location caused nothing but problems for players (he didn't specify the issues or elaborate on the subject and I didn't need to ask why, it's his games, his decision).
Fast-forward to the very first tech demo release of MnS... Faerin again considered the idea of a persistent save location so that players didn't have to transfer saves with every monthly update. And again, that would have caused nothing but problems. So he decided to "stick with what's worked" in the past, since the last 2 games (MotH and MwM) both worked in the same way. This is why I asked one of the moderators to kindly put a note in OP that saves
must be transferred over with each new update, and that if the game folder with the previous saves are deleted for any reason before the saves are moved over, you would need to start over again.
There's no reason Faerin needs to do any "investigations" into why Ren'Py does one thing, and Unity does another if this is the game engine he chooses to use.