goto: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) (Fix description, add example and remove link to "Script syntax" deleted page) |
Lou Montana (talk | contribs) m (Text replacement - "Category:Scripting Commands ArmA2" to "Category:Scripting Commands Arma 2") |
||
Line 70: | Line 70: | ||
[[Category:Scripting Commands OFP 1.99|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands OFP 1.99|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands ArmA|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands | [[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Command Group: Program Flow|{{uc:{{PAGENAME}}}}]] | [[Category:Command Group: Program Flow|{{uc:{{PAGENAME}}}}]] |
Revision as of 11:05, 10 January 2020
Description
- Description:
- Break script flow and go to given label (defined by # - NOT to be confused with SQF's hash sign!)
- Groups:
- Uncategorised
Syntax
Examples
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Notes
- Posted on August 4, 2006 - 10:52
- hardrock
- Notes from before the conversion:
- This function works only inside of SQS script.
- 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.
- Because of the searching order, it is faster to place loops which are executed often at the top of a script.
- Labels are not case sensitive.
- Loops which look something like the example below should be avoided as many of them could cause the mission to slow down:
#wait if (condition) then {goto "wait"}
It is better to use the @ command to wait for a condition to be true, or put a small delay into the wait loop. Example:- While it is not required to include a delay in a loop, such a loop without a delay can cause the script to slow the game down, as the loop will be executed many times before the game engine interrupts the script.
- Unless you really want the loop to execute multiple times during a frame, you should include a small delay.
- You would need to have many scripts running for this to be a significant issue.
- Deciding whether to use a script with a loop or a trigger or even a @ statement to detect a condition is a complicated matter and should be subject to experimentation.
- Posted on August 4, 2006 - 12:17
- UNN
- A goto command called within a forEach loop will only execute a single jump to goto, once the forEach loop has finished: {goto "wait"} forEach [0, 1, 2, 3, 4]
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands OFP 1.46
- Scripting Commands OFP 1.96
- Scripting Commands OFP 1.99
- Scripting Commands ArmA
- Scripting Commands Arma 2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters
- Command Group: Program Flow