|
|
6.
|
|
|
When the user gets an ending that causes the gallery to be unlocked, the flag must be set to True. ::
|
|
|
|
|
When the user gets an ending that causes the gallery to be unlocked, the flag must be set to True. ::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:33
|
|
|
7.
|
|
|
As persistent data is loaded before the init code is run, persistent data should only contain types that are native to python or Ren'Py. Alternatively, classes that are defined in ``python early`` blocks can be used, provided those classes can be pickled and implement equality.
|
|
|
|
|
As persistent data is loaded before the init code is run, persistent data should only contain types that are native to python or Ren'Py. Alternatively, classes that are defined in ``python early`` blocks can be used, provided those classes can be pickled and implement equality.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:38
|
|
|
8.
|
|
|
Merging Persistent Data
|
|
|
|
|
Merging Persistent Data
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:44
|
|
|
9.
|
|
|
There are cases where Ren'Py has to merge persistent data from two sources. For example, Ren'Py may need to merge persistent data stored on a USB drive with persistent data from the local machine.
|
|
|
|
|
There are cases where Ren'Py has to merge persistent data from two sources. For example, Ren'Py may need to merge persistent data stored on a USB drive with persistent data from the local machine.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:46
|
|
|
10.
|
|
|
Ren'Py does this merging on a field-by-field basis, taking the value of the field that was updated more recently. In some cases, this is not the desired behavior. In that case, the :func:`renpy.register_persistent` function can be used.
|
|
|
|
|
Ren'Py does this merging on a field-by-field basis, taking the value of the field that was updated more recently. In some cases, this is not the desired behaviour. In that case, the :func:`renpy.register_persistent` function can be used.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:50
|
|
|
11.
|
|
|
For example, if we have a set of seen endings, we'd like to take the union of that set when merging data. ::
|
|
|
|
|
For example, if we have a set of seen endings, we'd like to take the union of that set when merging data. ::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:55
|
|
|
12.
|
|
|
Persistent Functions
|
|
|
|
|
Persistent Functions
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/persistent.rst:69
|
|
|
13.
|
|
|
Registers a function that is used to merge values of a persistent field loaded from disk with values of current persistent object.
|
|
|
|
|
Registers a function that is used to merge values of a persistent field loaded from disk with values of current persistent object.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/inc/persistent:5
|
|
|
14.
|
|
|
`field`
|
|
|
|
|
`field`
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/inc/persistent:9
|
|
|
15.
|
|
|
The name of a field on the persistent object.
|
|
|
|
|
The name of a field on the persistent object.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/inc/persistent:9
|
