SteveyP

Active Member
Jul 1, 2017
911
3,231
DPC constantly checks with each new update for some variables that some mods/cheats writes into the saves/and/or persistent file. Editing the save and then resaving it inside the game doesn't do anything like that, nor adds any (new) variables to check on later. I have such one save just for tests and experiments. I modified it several times, resaved, then edited again, and so on. It doesn't crash on "Jacob scene" in EP9, nor in Helen scene in EP10. And I'm 99.99% sure it will pass any checks in future episodes. Since you not adding any variables that are not exist in the original game or to be more correct, the ones, DPC usually checks for, you're safe.

- give it a try

Just edit the save file in the EP7 or EP8 (after the Patrick scene) by editing the particular variable and then load/resave it and play the game till the EP10 end - you'll not get any troubles. I did it already, so you can check it by yourself. Don't exxagerate DPC's talents and programming skills. He spoils easy life for cheat/mods users, but this happens for a long-known and obvious reason - they store their variables and "tags" where they can be checked. That's about it.

Another option - you can use the , which never writes any variables or stuff into the game saves or persistent file. And, btw, you can also use this mod to alter any variable w/o need to use the save editor. Edit variable and resave the game... The only cons of this method - you probably will not be able to edit bios and other stuff. So, while I edit my saves, I also modify bios records to correct state. To get a perfect result and to avoid confusing myself.
Yes. That's what I wanted to say, Scrappy mod. I mixed up things because I don't use any. But that's it, and it's very easy to override. As you said, to make the game "crash" (actually, it's just a "quit"), DPC has to add a conditional to the code. In Scrappy's mod case, it was this (I guess you know all this because I think you make mods yourself, but I'm writing for everyone):

Python:
if persistent.mod_wtenabled != None:
    $ renpy.quit()
So, you can just type in the console "$ persistent.mod_wtenabled == None" and the game won't crash.

How to find it? Just search the code for "renpy.quit()" and you'll know every instance and variable checked to make the game "crash" (and, if you miss one and the game "crashes," you'll know there will be a command like that in the part the game terminated.



Indeed, it is. See ZenoMod answer above confirming it.
Thanks a lot for your help guys. I'll give these suggestions a look through. I'm not particularly savvy with code or things of that nature, so your explanations are a big help! If all goes to worse, I can always go back to Plan A and brute force my saves.
 

anony66

Newbie
Oct 9, 2017
83
178
What we thinking? February 14 seems like the most likely release date no?
If by "February" you mean "March", then yes. Rendering is supposed to finish next weekend, and only then the beta begins, so let's say 10.02. Somebody posted some time ago that the beta took 25 days last time, and the trend with that is the same as with dev time: it's only getting longer with every update. 25 days would put us at 07.03., which would mean release 14.03. If we are very lucky and it goes faster, 07.03. If something goes wrong, 21.03.
 

Lizzardcheese

Newbie
May 25, 2024
38
99
If by "February" you mean "March", then yes. Rendering is supposed to finish next weekend, and only then the beta begins, so let's say 10.02. Somebody posted some time ago that the beta took 25 days last time, and the trend with that is the same as with dev time: it's only getting longer with every update. 25 days would put us at 07.03., which would mean release 14.03. If we are very lucky and it goes faster, 07.03. If something goes wrong, 21.03.
Nicely broken down.
Also, great Sigs.
 
  • Heart
Reactions: anony66
4.70 star(s) 1,638 Votes