52
edits
Help:Text modding: Difference between revisions
Jump to navigation
Jump to search
m
→Choices: Tweaks to variable_kind control and choice control's unknown value.
m (Fix citations (again, because glitches)) |
m (→Choices: Tweaks to variable_kind control and choice control's unknown value.) |
||
| Line 117: | Line 117: | ||
variable_kind: 19 | variable_kind: 19 | ||
name: Gerudo_CarryIce_s | name: Gerudo_CarryIce_s | ||
</syntaxhighlight>The purpose of <code>variable_kind</code> is | </syntaxhighlight>The purpose of <code>variable_kind</code> refers to the kind of Game Flag that is referenced (this includes strings, int and float values). | ||
The value of <code>name</code> is the name of the variable to insert. | The value of <code>name</code> is the name of the variable to insert. | ||
| Line 161: | Line 161: | ||
The value of <code>cancel_index</code> is the choice that is selected when the player presses the B button. It refers to the same zero-indexed list as <code>selected_index</code>. From a game design standpoint, this should usually refer to the last choice. | The value of <code>cancel_index</code> is the choice that is selected when the player presses the B button. It refers to the same zero-indexed list as <code>selected_index</code>. From a game design standpoint, this should usually refer to the last choice. | ||
As implied by its name, the purpose of <code>unknown</code> is not understood. It | As implied by its name, the purpose of <code>unknown</code> is not understood. It has been observed that in instances where dialogue choices only include two options, the unknown field is set to <code>6</code>. Similarly for cases where there are 3 or 4 options the values <code>8</code> and <code>10</code> are used respectively. | ||
To implement branching-path dialogue with this control node, the associated event flow must have the switch-type event <code>EventSystemActor::GeneralChoiceX</code>, where <code>X</code> is the number of choices available. | To implement branching-path dialogue with this control node, the associated event flow must have the switch-type event <code>EventSystemActor::GeneralChoiceX</code>, where <code>X</code> is the number of choices available. | ||
| Line 236: | Line 236: | ||
If you encounter issues, make sure that the indentation in your message files matches the examples in this guide. The YAML format is strict with this because the indentations have special structural meaning. | If you encounter issues, make sure that the indentation in your message files matches the examples in this guide. The YAML format is strict with this because the indentations have special structural meaning. | ||
== References == | ==References== | ||
<references /> | <references /> | ||