Changes

Jump to navigation Jump to search
15 bytes added ,  03:56, 23 August 2023
no edit summary
Line 492: Line 492:  
|-
 
|-
 
| <samp>quickQuestion {{t|question}}#{{t|answer1}}#{{t|answer2}}#{{t|answer3}}(break){{t|answer1 script}}(break){{t|answer2 script}}(break){{t|answer3 script}}</samp>
 
| <samp>quickQuestion {{t|question}}#{{t|answer1}}#{{t|answer2}}#{{t|answer3}}(break){{t|answer1 script}}(break){{t|answer2 script}}(break){{t|answer3 script}}</samp>
| Show a dialogue box with an optional question and some answers. The answer scripts are sequences of commands separated by <samp>\\</samp>. When the player chooses an answer, the relevant answer script is executed and then the event continues. Usually used when an NPC's response will depend on the answer chosen but nothing else in the event has to depend on it. *Note: If quickQuestion is used immediately at the start of an event block such as "ExampleEvent": "quickQuestion [rest of the event]" it will cause a dialogue loop where the dialogue options will endlessly repeat themselves. Adding another command in front of quickQuestion resolves this issue.
+
| Show a dialogue box with an optional question and some answers. The answer scripts are sequences of commands separated by <samp>\\</samp>. When the player chooses an answer, the relevant answer script is executed and then the event continues. Usually used when an NPC's response will depend on the answer chosen but nothing else in the event has to depend on it. *Note: If quickQuestion is used immediately at the start of an event block (Example: "ExampleEvent": "quickQuestion [rest of the event]"), it will cause a dialogue loop. Adding another command in front of quickQuestion resolves this issue (Example: "ExampleEvent": "pause 1/quickQuestion [rest of the event]").
 
|-
 
|-
 
| <samp>removeItem {{t|object ID}}</samp>
 
| <samp>removeItem {{t|object ID}}</samp>
19

edits

Navigation menu