At this point, I'm uncertain. The current situation is that you've essentially got one big game that's split across two different Ren'Py versions. If you leave it as is, players moving to S2 will lose their S1 saves and that compromises their replays. If you repackage S1 to use the newer Ren'Py version that S2 uses, it's likely to also be that S1 users lose their existing saves, but new ones would work fine. And, finally, if you change S2 back to the old Ren'Py version that S1 uses, S2 saves will be broken.
The "easiest" way is to create a transfer tool in S1, with Python for example. Instead of saving it via Ren'Py you create an own save format where you save all the variables of the game in the state the player set at the end of the game. In S2 you use an import tool which reads out the variables and sets them in Ren'Py. I'm sure there're some guys on GitHub who already did that and made the code available.
EDITED ANSWER: The task is to not burn existing saves. I think the easiest route here is just to upgrade Ren'Py on Season 1 and put up with the pain of losing persistence. Mostly, I think the general rule is that you just don't change Ren'Py versions mid-project unless there are really serious reasons for doing so.
, would be to make a new S1 build with the same newer version as S2 uses. S1 saves will still work in both S1 and S2 on the new Ren'Py. The achievements and lore will be lost in S1, but replays will rebuild those and persistence will be retained between S1 and S2 from there onwards.
What if Season 2 was downgraded to 7.4, is that a possibilitySo, I just made a build of 0.7 (AKA Season 1) on Ren'Py 7.6.1, which is the same as the version of Ren'Py used for Season 2. Starting it auto-nukes all of the Season 1 persistence that was created with the 7.4.10 build. The lore and achievements are all scrubbed in the same fashion as happens when starting the Season 2 game. At the most basic, then, this is a matter of Ren'Py versions really, really needing to be the same for all Projekt: Passion seasons, period.
My advice, which is worth what you've paid for it
People will inevitably complain, but making a new S1 build has better long-term benefits. Upgrading Ren'Py on S1 will preserve the gaming experience for new players discovering PP for the first time and starting with S1. So, I think that's the wise move for keeping all those newcomers to the title happy on Steam. That's where the big money is.
S2 itself appears to work absolutely fine under 7.4.10. I did not test whether S2 saves made under 7.6.1 would work on S2 under 7.4.10. There is a risk that S2 saves from the newer Ren'Py might not work if S2 is back-ported.
I'm sorry, but an uncaught exception occurred.
While running game code:
File "renpy/common/00action_file.rpy", line 462, in __call__
renpy.load(fn)
Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
-- Full Traceback ------------------------------------------------------------
Full traceback:
File "renpy/common/_layout/screen_load_save.rpym", line 35, in script
$ ui.interact()
File "/Applications/renpy-7.4.10-sdk/renpy/ast.py", line 928, in execute
renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
File "/Applications/renpy-7.4.10-sdk/renpy/python.py", line 2245, in py_exec_bytecode
exec(bytecode, globals, locals)
File "renpy/common/_layout/screen_load_save.rpym", line 35, in <module>
$ ui.interact()
File "/Applications/renpy-7.4.10-sdk/renpy/ui.py", line 298, in interact
rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
File "/Applications/renpy-7.4.10-sdk/renpy/display/core.py", line 3315, in interact
repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, pause=pause, pause_start=pause_start, **kwargs)
File "/Applications/renpy-7.4.10-sdk/renpy/display/core.py", line 4155, in interact_core
rv = root_widget.event(ev, x, y, 0)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/transition.py", line 48, in event
return self.new_widget.event(ev, x, y, st) # E1101
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/screen.py", line 727, in event
rv = self.child.event(ev, x, y, st)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1313, in event
rv = super(Window, self).event(ev, x, y, st)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 273, in event
rv = d.event(ev, x - xo, y - yo, st)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/layout.py", line 1100, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "/Applications/renpy-7.4.10-sdk/renpy/display/behavior.py", line 979, in event
return handle_click(self.clicked)
File "/Applications/renpy-7.4.10-sdk/renpy/display/behavior.py", line 914, in handle_click
rv = run(action)
File "/Applications/renpy-7.4.10-sdk/renpy/display/behavior.py", line 322, in run
new_rv = run(i, *args, **kwargs)
File "/Applications/renpy-7.4.10-sdk/renpy/display/behavior.py", line 329, in run
return action(*args, **kwargs)
File "renpy/common/00action_file.rpy", line 462, in __call__
renpy.load(fn)
File "/Applications/renpy-7.4.10-sdk/renpy/loadsave.py", line 771, in load
log.unfreeze(roots, label="_after_load")
File "/Applications/renpy-7.4.10-sdk/renpy/python.py", line 2200, in unfreeze
self.rollback(0, force=True, label=label, greedy=greedy, on_load=True)
File "/Applications/renpy-7.4.10-sdk/renpy/python.py", line 2014, in rollback
self.load_failed()
File "/Applications/renpy-7.4.10-sdk/renpy/python.py", line 1932, in load_failed
raise Exception("Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?")
Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
Darwin-21.6.0-x86_64-i386-64bit
Ren'Py 7.4.10.2178
Projekt: Passion 0.11
Mon May 13 08:41:29 2024So is downgrading to 7.4 a viable solution or no?
Bro that's like every render from the update. Glad you liked it so much!
This is so sweet
It appears to be so. There does not appear to be any problem with also going back to PP 0.7 and getting new achievements. With both 0.7 and 0.11 on 7.4.10, persistence and saves seem fine.
We could still go around the neighborhood with a pellet rifle and nobody gave us grief - mid 70s.
Every time I see the MC I remember this kid I knew when I was twelve and laugh. He loved playing cops and robbers. He always had his shirt pulled up over his face and carried a cap gun. It looks so goofy.
That was back in the days when no one freaked out about a kid with a toy gun. Yes, I am that old.
