goto: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(An attempt to correct several misconceptions of loops and label based on extensive personal testing.) |
||
| Line 25: | Line 25: | ||
'''Example:''' | '''Example:''' | ||
'''goto''' " | '''''goto''' "Skip"''<br> | ||
. ''these lines''<br> | |||
. ''will be''<br> | |||
. ''skipped''<br> | |||
''#Skip | |||
| Line 32: | Line 37: | ||
Define the label with '''#'''. | Define the label with '''#'''. | ||
Labels are case | The search for labels always begins at the top of the script so that if there are multiple occurrences of a label the first occurrence will always be the one found. Labels are not case sensitive, and for the avoidance of doubt later versions of Flashpoint do not require that loops using a '''goto''' contain a delay. Deciding whether to use a script with a loop or a trigger or an @ statement is a complicated one and should be subject to experimentation. | ||
Revision as of 08:48, 23 May 2006
goto label
Operand types:
label: String
Type of returned value:
Description:
In script only: Go to given label.
Note: String argument is used here.
Be sure to use double quotes around label name in goto.
Example:
goto "Skip"
. these lines
. will be
. skipped
#Skip
Comments:
Define the label with #.
The search for labels always begins at the top of the script so that if there are multiple occurrences of a label the first occurrence will always be the one found. Labels are not case sensitive, and for the avoidance of doubt later versions of Flashpoint do not require that loops using a goto contain a delay. Deciding whether to use a script with a loop or a trigger or an @ statement is a complicated one and should be subject to experimentation.