shazba
Engaged Member
- Aug 4, 2020
- 3,506
- 19,668
- 585
For all the people complaining when changes break saves. I'd like to enlighten y'all.
When you save in a Renpy game, it saves a pointer to the current statement that's executing (like loading a render, or putting a sentence on the screen).
If you add one single line to the code somewhere before the save, that pointer is misaligned, and when you load the save, it'll load one step backwards.
If you delete a whole lot of code before point where the save was done, when you reload it's gonna load much further down the code, and maybe there isn't even code there. Probably a good time for the game to crash.
But wait, there's more.
What if a new variable was added to the game, but it was added in a section before your save and then gets referenced after your save? Renpy doesn't like that. Crash!
Going back and changing existing code has an inherent potential to break saves. So does that mean a developer, who is in the middle of creating their game should never go back and fix things? No. That would be silly to expect a game to be perfect on the first pass.
There are ways to minimise the potential for these save breaking changes, but it requires experience and foresight. A lot of developers are cutting their teeth on these projects, learning along the way.
Now, you wouldn't play the game if you weren't enjoying it, and you wouldn't complain if you weren't playing the game. So at least the developer is creating a game you're enjoying.
So yeah, it's a pain in the ass to have to start again, but whatever.
Me? I already deleted this game, I think it's shit.
When you save in a Renpy game, it saves a pointer to the current statement that's executing (like loading a render, or putting a sentence on the screen).
If you add one single line to the code somewhere before the save, that pointer is misaligned, and when you load the save, it'll load one step backwards.
If you delete a whole lot of code before point where the save was done, when you reload it's gonna load much further down the code, and maybe there isn't even code there. Probably a good time for the game to crash.
But wait, there's more.
What if a new variable was added to the game, but it was added in a section before your save and then gets referenced after your save? Renpy doesn't like that. Crash!
Going back and changing existing code has an inherent potential to break saves. So does that mean a developer, who is in the middle of creating their game should never go back and fix things? No. That would be silly to expect a game to be perfect on the first pass.
There are ways to minimise the potential for these save breaking changes, but it requires experience and foresight. A lot of developers are cutting their teeth on these projects, learning along the way.
Now, you wouldn't play the game if you weren't enjoying it, and you wouldn't complain if you weren't playing the game. So at least the developer is creating a game you're enjoying.
So yeah, it's a pain in the ass to have to start again, but whatever.
Me? I already deleted this game, I think it's shit.