|
|
24.
|
|
|
When :var:`config.developer` or :var:`config.fast_skipping`` is True, pressing the fast_skip key (by default, ">") causes the the game to immediately skip to the next important interaction. For this purpose, an important interaction is one that is not caused by a say statement, transition, or pause command. Usually, this means skipping to the next menu, but it will also stop when user-defined forms of interaction occur.
|
|
|
|
|
When :var:`config.developer` or :var:`config.fast_skipping`` is True, pressing the fast_skip key (by default, ">") causes the the game to immediately skip to the next important interaction. For this purpose, an important interaction is one that is not caused by a say statement, transition, or pause command. Usually, this means skipping to the next menu, but it will also stop when user-defined forms of interaction occur.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:75
|
|
|
25.
|
|
|
Warping to a Line
|
|
|
|
|
Warping to a Line
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:85
|
|
|
26.
|
|
|
Ren'Py supports warping to a line in the script, without the developer to play through the entire game to get there. While this warping technique has a number of warnings associated with it, it still may be useful in providing a live preview.
|
|
|
|
|
Ren'Py supports warping to a line in the script, without the developer to play through the entire game to get there. While this warping technique has a number of warnings associated with it, it still may be useful in providing a live preview.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:87
|
|
|
27.
|
|
|
To invoke warping, run Ren'Py with the ``--warp`` command-line argument followed by a filename:line combination, to specify where you would like to warp to. For example ::
|
|
|
|
|
To invoke warping, run Ren'Py with the ``--warp`` command-line argument followed by a filename:line combination, to specify where you would like to warp to. For example ::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:92
|
|
|
28.
|
|
|
(Where `my_project` is the full path to the base directory of your project.)
|
|
|
|
|
(Where `my_project` is the full path to the base directory of your project.)
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:98
|
|
|
29.
|
|
|
When warping is invoked, Ren'Py does a number of things. It first finds all of the scene statements in the program. It then tries to find a path from the scene statements to every reachable statement in the game. It then picks the reachable statement closest to, but before or at, the given line. It works backwards from that statement to a scene statement, recording the path it took. Ren'Py then executes the scene statement and any show or hide statements found along that path. Finally, it transfers control to the found statement.
|
|
|
|
|
When warping is invoked, Ren'Py does a number of things. It first finds all of the scene statements in the program. It then tries to find a path from the scene statements to every reachable statement in the game. It then picks the reachable statement closest to, but before or at, the given line. It works backwards from that statement to a scene statement, recording the path it took. Ren'Py then executes the scene statement and any show or hide statements found along that path. Finally, it transfers control to the found statement.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:100
|
|
|
30.
|
|
|
There are a number of fairly major caveats to the warp feature. The first is that it only examines a single path, which means that while the path may be representative of some route of execution, it's possible that there may be a bug along some other route. In general, the path doesn't consider game logic, so it's also possible to have a path that isn't actually reachable. (This is only really a problem on control-heavy games, especially those that use a lot of python code.
|
|
|
|
|
There are a number of fairly major caveats to the warp feature. The first is that it only examines a single path, which means that while the path may be representative of some route of execution, it's possible that there may be a bug along some other route. In general, the path doesn't consider game logic, so it's also possible to have a path that isn't actually reachable. (This is only really a problem on control-heavy games, especially those that use a lot of python code.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:108
|
|
|
31.
|
|
|
The biggest problem, though, is that no python code is executed before the statement that is warped to. This means that all variables will be uninitialized, which can lead to crashes when they are used. To overcome this, one can define a label ``after_warp``, which is called after a warp but before the warped-to statement executes. The code reached by this label can set up variables in the program, and then return to the preview.
|
|
|
|
|
The biggest problem, though, is that no python code is executed before the statement that is warped to. This means that all variables will be uninitialized, which can lead to crashes when they are used. To overcome this, one can define a label ``after_warp``, which is called after a warp but before the warped-to statement executes. The code reached by this label can set up variables in the program, and then return to the preview.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:116
|
|
|
32.
|
|
|
The warp feature requires :var:`config.developer` to be True to operate.
|
|
|
|
|
The warp feature requires :var:`config.developer` to be True to operate.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:123
|
|
|
33.
|
|
|
Debug Functions
|
|
|
|
|
Debug Functions
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/developer_tools.rst:127
|
