You can perform actions once the typewriter reaches a specific position in the text. (For this reason, actions work only if the typewriter is enabled)
Example: waiting for X seconds or waiting for the player input.
You can add actions to your text by using rich text tags.
Actions’ formatting follows this formula: “<actionID>” or “<actionID=attribute1,attribute2,...>” for eventual parameters/attributes (just like events/messages).
Actions tags are case insensitive, <waitfor> and <waitFor> will produce the same results.
Actions support multiple parameters, after the ‘=’ sign and all separated by a comma.
Example: <waitfor=1.5> or <playaudio=tada,laugh,dub>
⚠️ Floating point numbers must use a period, not a comma.
✔️ <speed=0.5>
❌ <speed=0,5>
As with Effects, you’ll find Actions stored inside their databases. You can add and remove as many as you prefer, create specific ones and also program your own via C++.
You can use the following built-in actions in your text.
Wait for Seconds
tag: waitfor
description: Waits for X seconds before continuing to show the text.
attributes: float (wait duration)
usage_example: waitfor=1.5
Wait for Input
tag: waitinput
description: Waits for the player input"
usage_example: waitinput
Speed
tag: speed
description: Multiplies the typewriter speed
attributes: float (speed multiplier)
usage_example: speed=2
Remember that you can also skip the typewriter inside specific parts of the text by using the "<notype>" tag, read more here: Skip Specific Parts of the Text
