Mod Ren'Py Our Red String JDMOD [0.12.1.2.a] [JohnDupont]

[Vengeance_11]

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "renpy/common/000statements.rpy", line 609, in execute_call_screen
    store._return = renpy.call_screen(name, *args, **kwargs)
Exception: Screen willup is not known.


-- Full Traceback ------------------------------------------------------------

Full traceback:
  File "game/JDMOD/scripts/story/chapter_6.rpyc", line 12545, in script
  File "C:\Users\x\OneDrive\Games\Our Red String\renpy\ast.py", line 2232, in execute
    self.call("execute")
  File "C:\Users\x\OneDrive\Games\Our Red String\renpy\ast.py", line 2220, in call
    return renpy.statements.call(method, parsed, *args, **kwargs)
  File "C:\Users\x\OneDrive\Games\Our Red String\renpy\statements.py", line 281, in call
    return method(parsed, *args, **kwargs)
  File "renpy/common/000statements.rpy", line 609, in execute_call_screen
    store._return = renpy.call_screen(name, *args, **kwargs)
  File "C:\Users\x\OneDrive\Games\Our Red String\renpy\exports.py", line 3167, in call_screen
    show_screen(_screen_name, _transient=True, *args, **kwargs)
  File "C:\Users\x\OneDrive\Games\Our Red String\renpy\display\screen.py", line 1185, in show_screen
    raise Exception("Screen %s is not known.\n" % (name[0],))
Exception: Screen willup is not known.


Windows-10-10.0.22631 AMD64
Ren'Py 8.0.3.22090809
Our Red String v12.2_FULL
Thu May 23 18:53:19 2024

This happened a few times in the early chapters of the game when playing as Lena, but didn't appear to affect Ian.

 

[Tutaeru]

You probably saved on a frame that doesnt allow to continue the game, try going back a bit or use a previous save before that one.

That ended up working thank you, though i'm not sure why saves on the screen where it specifically tells you to save don't work.

 

[BigGuy4by5]

Hi, Is the free version of mod 12.2b released?

 

[JohnDupont]

That ended up working thank you, though i'm not sure why saves on the screen where it specifically tells you to save don't work.

A bit of explanation:
In the base game, at the end of a chapter, the game jumps from the script of the chapter to the master_script:
This script is used to:

• depending on the chapter number, jump to the next chapter or call the 'to be continued' screen ;
• update some variables. It's very useful to introduce variables a posteriori.

In the previous version, the order was: chapter12prologue_script → master_script

With the mod, the 'end of chapter save' screen is added between the two. Because it's not in either, it doesn't get updated and should stay safe.
chapter12prologue_script → 'end of chapter save' screen → master_script

In this last update, the instructions of jumping to the master_script was changed to jump to chapter12_script.
In the current version, the order is chapter12prologue_script → chapter12_script → master_script

After you loaded this save, you were in the 'end of chapter save' screen and the only path forward was the master_script followed by the 'to be continued' screen.
'end of chapter save' screen → master_script

When you went back, you arrived at the end of chapter12prologue_script and were able to receive the updated instruction which sent you to chapter12_script.

This can only happen when a chapter is subdivided into a prologue, main part and/or epilogue.