Lemma Soft Forums

I think Ren'Py get seriously benefit from some sort of internal code updater/refresher.
Let's say you've finished out half of your project and decide to slot in something new, but it's an unreasonable distance in just to bugcheck. And it's bugged. So you change things, and have to reach that stage ALL OVER AGAIN just to find that something's still wrong.

It may require a lot of additional code and may already be in place in 6.14, but I wouldn't know. If it is in 6.14, it'd make upgrading from 6.13 infinitely more worthwhile.

Are you asking for something different than what shift+R gives you?

Until I (admitadly recently) discovered Shift+R, I just used to save the game. Sometimes I'd have to scroll back a few lines of text before saving, mind.

Shift-R didn't help in my case.

Here's what: I had a weapon defined simply as "Pipe" and in later revisions became "Grotty Pipe". I load an (admittedly) really old save file to try it out, it's still "Pipe", so I hit Shift-R. Still just "Pipe".
Given that my weapons are all defined at boot time, Shift-R really should've done something. I reasoned that as it didn't change the string value, it would continue using the old data. I tried rolling back to before the previous choice and THEN Shift-R'ing just in case, but nothing.

All I'm asking is that it rebuilds the game using the current data. So I won't lose the basic armour I have on a Shift-R.

EDIT: Though that's probably a hole in my code, I'll look at that.

The save function is mostly useless for bug checking (unless you perfectly understand and remember what would be saved or not).
You need to implement some special codes to imitate "start from some check points" or something similar thing. That every programmers are doing everyday.

I think it's not impossible to implement the auto save data updater thing, but it'll get more unpredictable bugs instead.

I was afraid of that. But at least I have confirmation of my fears. I'll just have to be really careful.