Just dropping by to say that :
- The new save system is, well, new. I didn't expect it to go smooth as butter
- It's very hard to test for save-related bugs, because everyone will save at different points of the game.
- You may be thrown back a few labels every once in a while, especially when jumping versions (like loading a 0.19.0 save in 0.19.1). To avoid this, save often, and in places where no dialogue happens (like on the map for instance), and while not in a dialogue.
- We're going to address the issue above, but it is going to be arduous. We've got some leads to potentially fix this, but nothing's set in stone yet, and whichever way we choose is going to require major reworks on the whole structure of the game
- If you want the technical details : it's because of how the renpy return stack works, and particularly, how jumps do not reset the return stack, forcing us to chop it up to not leak memory everywhere. Additionnally, renpy's return stack is specific to each version of a build. It's a nightmare to untangle.
- I've seen some issues with outfits not being saved (especially with diane) and that causes issues. I'm looking into that at the moment.
- I think it's pretty clear as to why save stuff is so hard to test for : even with 100,000 testers, these issues only came up D+4 after release. Comme quoi...
- There may be some other bugs, to report regarding the save system, but in order for us to notice them, please refrain from opening 60 tickets about the same bug. It really drowns proper bug reports in a sea of useless ones. If you want to notify that you're also affected by the bug, just leave a comment on it, and preferably attach a save file. And people wonder why we restrict the bug tracker to $1 patreons. It would be unusable otherwise!
- Speaking of the bug tracker, for those of you who have access to it, please behave, as mentionned above, reporting the same thing more than once is doing us, and you, by proxy, a disservice. For real, I don't even check the public bug tracker anymore(mil still does though, and send us the verified bugs on gitlab), since it's filled to the brim with useless bug reports, with barely an explanation, no save or log files attached. Proper etiquette would go a long way in making sure the bugs are noticed, and then promptly fixed. Thank you.
