|
|
20.
|
|
|
`new`
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:19
|
|
|
21.
|
|
|
The value of the field in the newer object.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:19
|
|
|
22.
|
|
|
`current`
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:24
|
|
|
23.
|
|
|
The value of the field in the current persistent object. This is provided for cases where the identity of the object referred to by the field can't change.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:22
|
|
|
24.
|
|
|
The function is expected to return the new value of the field in the persistent object.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:26
|
|
|
25.
|
|
|
Saves the persistent data to disk.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/persistent:31
|
|
|
26.
|
|
|
Multi-Game Persistence
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/persistent.rst:74
|
|
|
27.
|
|
|
Multi-Game persistence is a feature that lets you share information between Ren'Py games. This may be useful if you plan to make a series of games, and want to have them share information.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/persistent.rst:76
|
|
|
28.
|
|
|
To use multipersistent data, a MultiPersistent object must be created inside an init block. The user can then update this object, and save it to disk by calling its save method. Undefined fields default to None. To ensure the object can be loaded again, we suggest not assigning the object instances of user-defined types.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/persistent.rst:80
|
|
|
29.
|
|
|
Creates a new MultiPersistent object. This should only be called inside an init block, and it returns a new MultiPersistent with the given key.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/persistent.rst:88
|
