- Jan 19, 2020
- 12,382
- 48,980
Fans,TheGreys,
Bud... you messed up. You should NOT have released this update in this condition. I really wish you would have reached out to me before deploying it.
Folks, your old saves are mostly going to be fucked (Ep3.5EA and prior). You see when the dev built the retail package he did not base the new script files off the original RPYC files... meaning your save location pointers RenPy uses to load your save at the exact point within the VN are lost. He packaged it with brand newly created RPYC's which have zero file pointers in them.
I can fix all of this in the mod update... maybe for you folks running unmodded too, but there will be many many players who don't either visit this site or don't read the threads and there could end up with a mix of two sets of folks:
This could become a real mess real quick. I'll see what I can do but a "patch" should be easy enough for me to create based on the Ep3.5EA script files. I need a bit of time though... BBL.
- Those that have their original file save pointers via a fix to be created (I'm working on it)
- Those who do not
I need some help from you folks that play (and always have) unmodded to give me an approximate amount of your old saves are loading. I'm having a larger discrepancy on my end with unmodded versus modded and I'm trying to help TheGreys out with some potential RenPy issues.
Know that there are many grammatical and other dialogue fixes versus the last update (approximately 1,000 edits) so some rollback is to be expected depending on each save location. What I'm looking for are exceptions when RenPy errors out when it exhausts how far it can try to rollback to find a solid label starting point for the old save. In those cases you will have complete load failure... those are the ones to account for.
Ping me or reply to this message so I'm noted please. Thank you in advance.
Last edited: