- Sep 17, 2018
- 134
- 774
I will release the update with a important notice attached, though the issue isn't localized to saves from .3.6. It affects any save that was saved in and past .3.6 due to whatever the issue within the .3.6 content is fucking them up.
- Sep 17, 2018
- 134
- 774
Updated to v0.4.0, read the important notice before attempting to load a save from v0.3.7 or v0.3.6 and coming to complain about it.
- Sep 17, 2018
- 134
- 774
I changed the relevant parts to have it proceed... unless I've been a tit and packaged the wrong version, and packaged the one I have as a pre-release bug squashing test bed for which game progress wasn't a focus. Give me a minute to download it and check.
Edit: Can confirm I had packaged the correct version, can you send me your log file for me to debug with please.
Sorry im new to this but do you need the log file from the main folder or the traceback file ?
EDIT: i dont get an error message i just get the endscreen from 3.7.0
Last edited:
- Sep 17, 2018
- 134
- 774
That's really fuckin odd, which link did you get the mod from?
Edit: Try this, put it in the game folder.
- Sep 17, 2018
- 134
- 774
doesn´t work but could an old save prevent me from going further. ive tride it with an old save that worked but not a brand new save
- Sep 17, 2018
- 134
- 774
Yeah give a new save a try, it could be a different presentation of the same issue causing saves to be completely fucked by something in .3.6's content. If it's still not letting you progress from there shoot me a DM and I'll do my best to help you.
- Sep 17, 2018
- 134
- 774
Just remember to make a save before reaching .3.6's content else you'll likely have to do more restarts for future updates until I or Laik figure out what in .3.6's content is fucking saves up.ok thank you for youre time im trying a new one now
Code:
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_main_menu.rpym", line 28, in script
python hide:
File "renpy/ast.py", line 928, in execute
renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
File "renpy/python.py", line 2245, in py_exec_bytecode
exec(bytecode, globals, locals)
File "renpy/common/_layout/screen_main_menu.rpym", line 28, in <module>
python hide:
File "renpy/common/_layout/screen_main_menu.rpym", line 35, in _execute_python_hide
ui.interact()
File "renpy/ui.py", line 298, in interact
rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
File "renpy/display/core.py", line 3325, in interact
repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, pause=pause, pause_start=pause_start, **kwargs)
File "renpy/display/core.py", line 4160, in interact_core
rv = root_widget.event(ev, x, y, 0)
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/transition.py", line 48, in event
return self.new_widget.event(ev, x, y, st) # E1101
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/screen.py", line 727, in event
rv = self.child.event(ev, x, y, st)
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1323, in event
rv = super(Window, self).event(ev, x, y, st)
File "renpy/display/layout.py", line 273, in event
rv = d.event(ev, x - xo, y - yo, st)
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 1323, in event
rv = super(Window, self).event(ev, x, y, st)
File "renpy/display/layout.py", line 273, in event
rv = d.event(ev, x - xo, y - yo, st)
File "renpy/display/layout.py", line 1102, in event
rv = i.event(ev, x - xo, y - yo, cst)
File "renpy/display/layout.py", line 273, in event
rv = d.event(ev, x - xo, y - yo, st)
File "renpy/display/behavior.py", line 983, in event
return handle_click(self.clicked)
File "renpy/display/behavior.py", line 918, in handle_click
rv = run(action)
File "renpy/display/behavior.py", line 330, in run
return action(*args, **kwargs)
File "renpy/common/00action_file.rpy", line 462, in __call__
renpy.load(fn)
File "renpy/loadsave.py", line 771, in load
log.unfreeze(roots, label="_after_load")
File "renpy/python.py", line 2200, in unfreeze
self.rollback(0, force=True, label=label, greedy=greedy, on_load=True)
File "renpy/python.py", line 2014, in rollback
self.load_failed()
File "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?
Windows-10-10.0.19041
Ren'Py 7.4.11.2266
Nephilim 0.4.0
Sat Mar 23 20:50:58 2024- Sep 17, 2018
- 134
- 774
I've just emboldened something you obviously ignored.
- Mar 16, 2018
- 990
- 11,797
- Sep 26, 2020
- 2,975
- 2,312
IT WILL HAVE THE SAME SAVE ISSUES?? CUZ I CAN LOAD ONLY 0,35 SAVE AND SADLY i can't skip using ctrl...i already restarted this 3 times argh....this is bad..
- Aug 23, 2021
- 538
- 1,095
No need to yell. Yes, a 0.3.6/0.3.7 save will give the same error on load with LaikDink's latest version of the mod. As pointed out multiple times above, a save from 0.3.5 is the most recent that will load without the error.