Meushi
Well-Known Member
- Aug 4, 2017
- 1,146
- 12,799
- 672
You don't have a clue what you're talking about. The RPYC is a COMPILED version of the RPY file... recompiling it WITH THE DAMN GAME IT IS INTENDED FOR will NOT change compatibility! That's idiotic! Now go educate yourself, this is stupid.
Oh no, what a shame...I'm ignoring the other topic, already put them on ignore so I don't see their posts about it again.
I'm sure Night Hawk has lots of programming experience, unfortunately he's apparently unfamiliar with the mechanics of how RenPy saves work & their reliance on maintaining RPYC files for save comparability between releases.
To reiterate, Night Hawk is mistaken on this matter. The SG patch now includes an RPYC file. As with all RenPy games, use the included RPYC if you don't want rollback errors and broken saves in the future..rpyc files use what they call an AST tree. PyTom's original blog post is here :You must be registered to see the links
It explains (at least implicitly) why deleting an .rpyc would break things, whilst forced recompiles wouldn't.
The basics are that when the game is incrementally built, each new iteration of the .rpyc file is based on the previous version. It grows and varies over time. As soon as you delete an .rpyc file, that previous "history" is lost and RenPy has to start from scratch with a new AST tree.
Sadly Night Hawk's reluctance to consider advice means he's unlikely to see this information, and will continue to operate under a misconception on the importance of retaining RPYC files to maintain save comparability.
Given my ignorance & cluelesness, people will have to make up their own mind about who has the wrong end of the stick on this issue.