Ren'Py Screen Language and Python State: Predict System Synchronization

Answer

In Ren'Py 8.x the prediction system does not keep a predicted screen as the visible screen. When a show screen statement is executed, the screen is (re‑)evaluated against the current Python/store state at that moment. Therefore, if a Python variable that the screen reads is changed after the prediction phase but before the show screen command, the rendered screen uses the new value – the engine forces a fresh evaluation and does not display stale data from the prediction.

Confirmed facts

• Prediction is primarily used to preload images and other assets; it may evaluate the screen body early to determine which images to load.
• The visible screen is always created or refreshed at show‑time (or after an interaction restart) using the current state.
• Changing state after the screen has been shown does not automatically update the on‑screen values; you need to call renpy.restart_interaction() or trigger an action that does so.

Likely explanation

Because the prediction phase may have already evaluated expressions (e.g., image names) based on the state at prediction time, a rapid state change can cause the predictor to load the wrong images, leading to a brief hitch when the correct images are later demanded. However, the final text, bars, or other dynamic content that depends on the same variable will reflect the up‑to‑date state because the screen is re‑evaluated at show time.

Steps to ensure correct behavior

1. Make any changes to the Python/store variables that the screen depends on before issuing show screen.
2. If you must change the variable after show screen and need the screen to reflect the new value immediately, add a restart:

   $ renpy.restart_interaction()
   

3. Alternatively, pass volatile values as screen parameters when you call show screen; parameters are captured at call time and are not affected by later store changes unless you re‑show the screen.

Missing diagnostic detail

Are you accessing the changing value directly from the store inside the screen body, or are you passing it as a screen parameter? Knowing this determines whether you need to restart the interaction or simply re‑show the screen with updated parameters.