|
|
121.
|
|
|
To take advantage of the replay mode, a scene should begin with a label, and end with a call to renpy.end_replay. The scene should make no assumption as to the state of the layers or variables, which can be very different in normal and replay mode. (In replay code, the label is invoked with a black screen.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:294
|
|
|
122.
|
|
|
For example::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:300
|
|
|
123.
|
|
|
With the scene define like that, the replay can be invoked with the Replay action::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:324
|
|
|
124.
|
|
|
There is one store variable used by replay mode:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:329
|
|
|
125.
|
|
|
When in replay mode, this is sent to the label at which replay mode was started. Outside of replay mode, this is None.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:333
|
|
|
126.
|
|
|
In addition, :var:`config.enter_replay_transition` and :var:`config.exit_replay_transition` are used when entering and exiting replay mode, respectively.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:336
|
|
|
127.
|
|
|
The following variables and actions are used in replay mode:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/rooms.rst:340
|
|
|
128.
|
|
|
An action that ends the current memory.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/replay:5
|
|
|
129.
|
|
|
An action that starts `label` as a replay.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/replay:9
|
|
|
130.
|
|
|
`scope`
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/replay:13
|
