|
|
36.
|
|
|
There are certain types that cannot be pickled:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:138
|
|
|
37.
|
|
|
Render objects.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:140
|
|
|
38.
|
|
|
Iterator objects.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:141
|
|
|
39.
|
|
|
File-like objects.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:142
|
|
|
40.
|
|
|
Inner functions and lambdas.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:143
|
|
|
41.
|
|
|
By default, Ren'Py uses the cPickle module to save the game. Setting :var:`config.use_cpickle` will make Ren'Py use the pickle module instead. This makes the game slower, but is better at reporting save errors.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:145
|
|
|
42.
|
|
|
Save Functions and Variables
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:151
|
|
|
43.
|
|
|
There is one variable that is used by the high-level save system:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:153
|
|
|
44.
|
|
|
This is a string that is stored with each save. It can be used to give a name to the save, to help users tell them apart.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:157
|
|
|
45.
|
|
|
There are a number of high-level save actions and functions defined in the :ref:`screen actions <screen-actions>`. In addition, there are the following low-level save and load actions.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/save_load_rollback.rst:160
|
