|
|
11.
|
|
|
The list of nvl-mode text blocks.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:35
|
|
|
12.
|
|
|
The python state consists of the variables in the store that have changed since the game began, and all objects reachable from those variables. Note that it's the change to the variables that matters - changes to fields in objects will not cause those objects to be saved.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:37
|
|
|
13.
|
|
|
In this example::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:42
|
|
|
14.
|
|
|
only `b` will be saved. A will not be saved because it does not change once the game begins. `O` is not saved because it does not change - the object it refers to changes, but the variable itself does not.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:51
|
|
|
15.
|
|
|
What isn't Saved
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:57
|
|
|
16.
|
|
|
Python variables that are not changed before the game begins will not be saved. This can be a major problem if a variable that is saved and one that is refer to the same object. (Alias the object.) In this example::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:59
|
|
|
17.
|
|
|
`a` and `b` are aliased. Saving and loading may break this aliasing, causing `a` and `b` to refer to different objects. Since this can be very confusing, it's best to avoid aliasing saved and unsaved variables. (This is rare to encounter directly, but might come up when an unsaved variable and saved field alias.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:73
|
|
|
18.
|
|
|
There are several other kinds of state that isn't saved:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:79
|
|
|
19.
|
|
|
control flow path
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:84
|
|
|
20.
|
|
|
Ren'Py only saves the current statement, and the statement it needs to return to. It doesn't remember how it got there. Importantly, if code (like variable assignments) is added to the game, it won't run.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:82
|
