goto: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (template:command argument fix)
m (Text replacement - "{{Feature | Warning | " to "{{Feature|warning|")
 
(50 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Command|= Comments
{{RV|type=command
____________________________________________________________________________________________


| ofp |= Game name
|game1= ofp
|version1= 1.00


|1.00|= Game version
|game2= ofpe
____________________________________________________________________________________________
|version2= 1.00


| In [[sqs syntax|SQS script]] only: Go to given label.
|game3= arma1
|version3= 1.00


String argument is used here.
|game4= arma2
Make sure to use double quotes around label name in goto. Define the label with #. Note that labels are not case sensitive and that labels are searched for from the top of the script, so multiple occurrences of a label will only result in the top most one ever being found.|DESCRIPTION=
|version4= 1.00
____________________________________________________________________________________________


| '''goto''' label |SYNTAX=
|game5= arma2oa
|version5= 1.50


|p1= label: [[String]] |PARAMETER1=
|game6= tkoh
|version6= 1.00


| [[Nothing]] |RETURNVALUE=
|game7= arma3
____________________________________________________________________________________________
|version7= 0.50


| |SEEALSO=
|gr1= Program Flow


}}
|descr= Break script flow and go to given label (defined by '''#''' - '''NOT''' to be confused with [[SQF Syntax|SQF]]'s [[a_hash_b|hash sign]]!)
{{Feature|warning|This command only works in [[SQS Syntax]].}}
{{Feature|informative|Note that labels are not case sensitive and are searched for from the top of the script, so multiple occurrences of a label will only result in the topmost one ever being found.}}


<h3 style="display:none">Notes</h3>
|s1= [[goto]] label
<dl class="command_description">
<!-- Note Section BEGIN -->


<dd class="notedate">Posted on August 4, 2006 - 10:52
|p1= label: [[String]]
<dt class="note">'''[[User:Hardrock|hardrock]]'''<dd class="note">''Notes from before the conversion:''


* This function works only inside of [[sqs syntax|SQS script]].
|r1= [[Nothing]]
*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
|x1= <sqs>
[[if]] (condition) [[then]] {[[goto]] "wait"}
goto "myLabel"
player setDamage 1


#myLabel
hint "you successfully avoided death!"
</sqs>


It is better to use the [https://community.bistudio.com/wiki?title=Script_syntax&oldid=14554 @] command to wait for a condition to be true, or put a small delay into the wait loop.
|seealso= [[Control_Structures#SQS_syntax_.28deprecated.29|SQS Control Structures]] [[SQS to SQF conversion]]
}}


{{Note
|user= Hardrock
|timestamp= 20060804105200
|text= ''Notes from before the conversion:''


Example
* This function works only inside of [[SQS Syntax|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:
<sqs>
#wait
if (condition) then { goto "wait" }
</sqs>


*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.
It is better to use the '''@''' command to wait for a condition to be true, or put a small delay into the wait loop.


*Unless you really want the loop to execute multiple times during a frame, you should include a small delay.
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.
}}


*You would need to have many scripts running for this to be a significant issue.
{{Note
 
|user= UNN
*Deciding whether to use a script with a loop or a trigger or even a [[Script syntax|@]] statement to detect a condition is a complicated matter and should be subject to experimentation.
|timestamp= 20060804121700
 
|text= A goto command called within a [[forEach]] loop will only execute a single jump to [[goto]], once the [[forEach]] loop has finished:
 
<sqs>{ goto "wait" } forEach [0, 1, 2, 3, 4]</sqs>
<dd class="notedate">Posted on August 4, 2006 - 12:17
}}
<dt class="note">'''[[User:UNN|UNN]]'''<dd class="note">
 
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]
 
 
<!-- Note Section END -->
</dl>
 
<h3 style="display:none">Bottom Section</h3>
 
 
[[Category:Scripting Commands|GOTO]]
[[Category:Scripting Commands OFP 1.99|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands OFP 1.96|GOTO]]
[[Category:Scripting Commands OFP 1.46|GOTO]]
[[Category:Scripting Commands ArmA|GOTO]]
[[Category:Command Group: Program Flow|GOTO]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]

Latest revision as of 21:46, 16 May 2024

Logo A0.png1.00ofpe logo.png1.00Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

Description

Description:
Break script flow and go to given label (defined by # - NOT to be confused with SQF's hash sign!)
⚠
This command only works in SQS Syntax.
ⓘ
Note that labels are not case sensitive and are searched for from the top of the script, so multiple occurrences of a label will only result in the topmost one ever being found.
Groups:
Program Flow

Syntax

Syntax:
goto label
Parameters:
label: String
Return Value:
Nothing

Examples

Example 1:
goto "myLabel" player setDamage 1 #myLabel hint "you successfully avoided death!"

Additional Information

See also:
SQS Control Structures SQS to SQF conversion

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
Hardrock - c
Posted on Aug 04, 2006 - 10:52 (UTC)
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.
UNN - c
Posted on Aug 04, 2006 - 12:17 (UTC)
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]
Retrieved from "https://community.bistudio.com/wiki?title=goto&oldid=364521"