|
|
1.
|
|
|
Special Screen Names
|
|
|
|
|
Special Screen Names
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:6
|
|
|
2.
|
|
|
There are two kinds of special screen names in Ren'Py. The first are screens that will be automatically displayed when Ren'Py script language commands (or their programmatic equivalents) are run. The other type are menu screens. These have conventional names for conventional functionality, but screens can be omitted or changed as is deemed necessary.
|
|
|
|
|
There are two kinds of special screen names in Ren'Py. The first are screens that will be automatically displayed when Ren'Py script language commands (or their programmatic equivalents) are run. The other type are menu screens. These have conventional names for conventional functionality, but screens can be omitted or changed as is deemed necessary.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:8
|
|
|
3.
|
|
|
On this page, we'll give example screens. It's important to realize that, while some screens must have minimal functionality, the screen system makes it possible to add additional functionality to screens. For example, while the standard say screen only displays text, the screen system makes it easy to add features like skipping, auto-forward mode, or muting.
|
|
|
|
|
On this page, we'll give example screens. It's important to realize that, while some screens must have minimal functionality, the screen system makes it possible to add additional functionality to screens. For example, while the standard say screen only displays text, the screen system makes it easy to add features like skipping, auto-forward mode, or muting.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:15
|
|
|
4.
|
|
|
Some special screens take parameters. These parameters can be accessed as variables in the screen's scope.
|
|
|
|
|
Some special screens take parameters. These parameters can be accessed as variables in the screen's scope.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:22
|
|
|
5.
|
|
|
Some of the screens also have special ids associated with them. A special id should be assigned to a displayable of a given type. It can cause properties to be assigned to that displayable, and can make that displayable accessible to calling code.
|
|
|
|
|
Some of the screens also have special ids associated with them. A special id should be assigned to a displayable of a given type. It can cause properties to be assigned to that displayable, and can make that displayable accessible to calling code.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:25
|
|
|
6.
|
|
|
In-Game Screens
|
|
|
|
|
In-Game Screens
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:31
|
|
|
7.
|
|
|
These screens are automatically displayed when certain Ren'Py statements execute.
|
|
|
|
|
These screens are automatically displayed when certain Ren'Py statements execute.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:33
|
|
|
8.
|
|
|
Say
|
|
|
|
|
Say
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:39
|
|
|
9.
|
|
|
The ``say`` screen is called by the say statement, when displaying ADV-mode dialogue. It is displayed with the following parameters:
|
|
|
|
|
The ``say`` screen is called by the say statement, when displaying ADV-mode dialogue. It is displayed with the following parameters:
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:41
|
|
|
10.
|
|
|
`who`
|
|
|
|
|
`who`
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/screen_special.rst:44
|
