SQS Syntax - Revision history

Lou Montana: Some wiki formatting

2022-09-02T20:27:41Z

Some wiki formatting

← Older revision		Revision as of 22:27, 2 September 2022
Line 1:		Line 1:
	{{TOC\|side\|1\|}}		{{TOC\|side\|1\|}}
	[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in ~~{{GameCategory\|arma1\|link=y}}~~. It can only be used for [[Script File\|scripts]], but not for [[Function\|functions]], in the [[~~ArmA: Mission Editor\|~~Mission Editor]] or in addon config files. The ~~alternative~~ syntax is [[SQF Syntax]].		[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available (although considered obsolete) in later titles. It can only be used for [[Script File\|scripts]], but not for [[Function\|functions]], in the [[Mission Editor]] or in addon config files. The newer script syntax is [[SQF Syntax]].


Line 7:		Line 7:
	Binding rules:		Binding rules:

	* [[Statement\|Statements]] are separated by '''line breaks''' ~~''and''~~ '''semicolons''' (;) ''and'' '''commas''' (,)~~. This~~ means that a statement ''~~must~~ not'' span over multiple lines.		* [[Statement\|Statements]] are separated by '''line breaks''', '''semicolons''' (;) and '''commas''' (,) - this means that a statement ''can not'' span over multiple lines (e.g a [[switch]] usage must be all inlined).
	* ~~Curled~~ braces ({ }) ~~group code to '''blocks'''. A block~~ is considered a single statement, thus may not span over multiple lines.		* A [[Code\|code block]] (defined by curled braces <sqs inline>{ }</sqs>) is considered a single statement, thus may not span over multiple lines either.

	=== Example ===		=== Example ===
Line 34:		Line 34:
	<sqs>if (_value == 1) then { hint "Value is 1" } else { hint "Value is not 1" }</sqs>		<sqs>if (_value == 1) then { hint "Value is 1" } else { hint "Value is not 1" }</sqs>

	There exist also special structures limited to SQS syntax.		There exist also special structures limited to SQS syntax, listed below.

	=== Tilde ===		=== Tilde ===
Line 52:		Line 52:
	=== Label ===		=== Label ===

	~~You~~ may ~~define labels~~ in the code by beginning a line with {{hl\|#}}, followed by the name ~~of the label~~ (without spaces).		Labels may be defined in the code by beginning a line with {{hl\|#}}, followed by the label's name (without spaces).
	~~You may use the command~~ [[goto]] at any point of the [[Script File\|script]] to jump to this label (and potentially create a loop).		The [[goto]] command can then be used at any point of the [[Script File\|script]] to jump to this label (and potentially create a loop).

	<sqs>		<sqs>
Line 66:		Line 66:
	=== Conditional ===		=== Conditional ===

	~~You may query a~~ [[Boolean]] condition ~~and define~~ code, that is executed ''only'' when ~~the~~ condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with {{hl\|?}}, followed by the condition and {{hl\|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.		A [[Boolean]] condition can be used in order to run code that is executed ''only'' when said condition is {{hl\|[[true]]}}. Note that there is no such equivalent for "[[else]]".
			A conditional line must start with {{hl\|?}}, followed by the condition and {{hl\|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;).
			The conditional statement, like other statements, ends with the end of the line.

	<sqs>? alive target : hint "target is alive, let's destroy it"; target setDammage 1</sqs>		<sqs>? alive target : hint "target is alive, let's destroy it"; target setDammage 1</sqs>
Line 80:		Line 82:

	Due to the line-based nature of [[SQS Syntax\|SQS scripts]], it is not possible to create multiline string constants in them.		Due to the line-based nature of [[SQS Syntax\|SQS scripts]], it is not possible to create multiline string constants in them.
	To overcome this limitation ~~you~~ can ~~store multiline~~ in separate ~~SQF [[Function\|function]] files~~ and ~~load them~~ using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).		To overcome this limitation multiline text can be stored in a separate text file and loaded using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).


	== Limitations ==		== Limitations ==

	In ~~'''~~{{ofp}} ~~v1.96'''~~, if a single line of a sqs file is longer than 4096 characters, ~~{{ofp}}~~ will return an error and will not execute the line.		In {{GameCategory\|ofp\|link= y}}, if a single line of a sqs file is longer than 4096 characters, the game will return an error and will not execute the line.

Lou Montana: Add Tilde operator

2022-07-10T23:47:13Z

Add Tilde operator

← Older revision		Revision as of 01:47, 11 July 2022
Line 20:		Line 20:
	== Comments ==		== Comments ==

	A line beginning with a '''semicolon''' (;) is considered a comment and ignored by the game engine.		A line beginning with a '''semicolon''' ({{hl\|;}}) is considered a comment and ignored by the game engine.

	=== Example ===		=== Example ===
Line 31:		Line 31:
	The control structures listed in the article [[Control Structures]] may also be used in SQS syntax. Note that they must be written '''within a single line''' due to the above rules.		The control structures listed in the article [[Control Structures]] may also be used in SQS syntax. Note that they must be written '''within a single line''' due to the above rules.

	=== ~~Example~~ ===		; Example
			<sqs>if (_value == 1) then { hint "Value is 1" } else { hint "Value is not 1" }</sqs>

			There exist also special structures limited to SQS syntax.

			=== Tilde ===

	~~<sqs>if~~ (~~_value==1) then~~ {~~hint "Value is 1"~~} ~~else {hint "Value is not 1"~~}~~</sqs>~~		The tilde ({{hl\|~}}) symbol tells the script to wait X amount of seconds (see [[sleep]] in SQF):

	~~There exist also special structures limited to SQS syntax~~.		<sqs>
			hint "3..."
			~1
			hint "2..."
			~1
			hint "1..."
			~1
			hint "GO!"
			</sqs>

	=== Label ===		=== Label ===

	You may define labels in the code by beginning a line with {{hl\|#}}, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.		You may define labels in the code by beginning a line with {{hl\|#}}, followed by the name of the label (without spaces).
			You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label (and potentially create a loop).

	<sqs>		<sqs>
	#Label1		#Label1

	hint "~~repeating~~"		~1
			hint format ["a second has passed. time: %1", round time]

	goto "Label1"		goto "Label1"
Line 64:		Line 79:
	== Notes ==		== Notes ==

	Due to line-based nature of [[SQS Syntax\|SQS scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).		Due to the line-based nature of [[SQS Syntax\|SQS scripts]], it is not possible to create multiline string constants in them.
			To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).

Lou Montana: Some wiki formatting

2022-07-01T13:46:52Z

Some wiki formatting

← Older revision		Revision as of 15:46, 1 July 2022
Line 1:		Line 1:
	{{TOC\|side\|1\|}}		{{TOC\|side\|1\|}}
	[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script File\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].		[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script File\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].


	== Rules ==		== Rules ==

	Binding rules:		Binding rules:

Line 9:		Line 11:

	=== Example ===		=== Example ===

	STATEMENT 1		STATEMENT 1
	STATEMENT 2; STATEMENT 3, STATEMENT 4		STATEMENT 2; STATEMENT 3, STATEMENT 4

	BLOCK { STATEMENT 5; STATEMENT 6 }		BLOCK { STATEMENT 5; STATEMENT 6 }


	== Comments ==		== Comments ==

	A line beginning with a '''semicolon''' (;) is considered a comment and ignored by the game engine.		A line beginning with a '''semicolon''' (;) is considered a comment and ignored by the game engine.

	=== Example ===		=== Example ===
	; this is my comment
			<sqs>; this is my comment</sqs>


	== Language Constructs ==		== Language Constructs ==

	The control structures listed in the article [[Control Structures]] may also be used in SQS syntax. Note that they must be written '''within a single line''' due to the above rules.		The control structures listed in the article [[Control Structures]] may also be used in SQS syntax. Note that they must be written '''within a single line''' due to the above rules.

	=== Example ===		=== Example ===
	[[if]] (_value==1) [[then]] {[[hint]] "Value is 1"} [[else]] {[[hint]] "Value is not 1"}
			<sqs>if (_value==1) then {hint "Value is 1"} else {hint "Value is not 1"}</sqs>

	There exist also special structures limited to SQS syntax.		There exist also special structures limited to SQS syntax.

	=== Label ===		=== Label ===

	You may define labels in the code by beginning a line with {{hl\|#}}, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.		You may define labels in the code by beginning a line with {{hl\|#}}, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.

	#Label1		<sqs>
			#Label1
	~~CODE~~
			hint "repeating"
	[[goto]] "Label1"
			goto "Label1"
			</sqs>

	=== Conditional ===		=== Conditional ===

	You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with {{hl\|?}}, followed by the condition and {{hl\|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.		You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with {{hl\|?}}, followed by the condition and {{hl\|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.

	? ~~CONDITION~~ : ~~STATEMENT~~ 1~~; STATEMENT 2~~		<sqs>? alive target : hint "target is alive, let's destroy it"; target setDammage 1</sqs>

	=== @ ===		=== @ ===

	Much like the [[waitUntil]] statement in [[SQF Syntax]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]].		Much like the [[waitUntil]] statement in [[SQF Syntax]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]].

	@ ~~CONDITION~~		<sqs>@not alive target</sqs>


	== Notes ==		== Notes ==
	Due to line-based nature of [[SQS Syntax\|~~Sqs~~ scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).
			Due to line-based nature of [[SQS Syntax\|SQS scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).


	== Limitations ==		== Limitations ==

	In '''{{ofp}} v1.96''', if a single line of a sqs file is longer than 4096 characters, {{ofp}} will return an error and will not execute the line.		In '''{{ofp}} v1.96''', if a single line of a sqs file is longer than 4096 characters, {{ofp}} will return an error and will not execute the line.


	== See also ==		== See also ==

	* [[SQF Syntax]]		* [[SQF Syntax]]
	* [[Script File]]		* [[Script File]]
	* [[Statement]]		* [[Statement]]
	* [[Block]]		* [[Block]]


	[[Category: Syntax]]		[[Category: Syntax]]

Lou Montana: Text replacement - "`([^= ]+)<\/tt>" to "{{hl|$1}}"`

2021-11-15T23:17:43Z Text replacement - "<tt>([^= ]+)<\/tt>" to "{{hl|$1}}" ← Older revision Revision as of 01:17, 16 November 2021 Line 29: Line 29: === Label === === Label === You may define labels in the code by beginning a line with <tt>#</tt>, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File|script]] to jump to this label. You may define labels in the code by beginning a line with {{hl|#}}, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File|script]] to jump to this label. #Label1 #Label1 Line 38: Line 38: === Conditional === === Conditional === You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl|true}}. Note that there is no equivalent for "else". A conditional line must start with <tt>?</tt>, followed by the condition and <tt>:</tt>, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line. You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl|true}}. Note that there is no equivalent for "else". A conditional line must start with {{hl|?}}, followed by the condition and {{hl|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line. ? CONDITION : STATEMENT 1; STATEMENT 2 ? CONDITION : STATEMENT 1; STATEMENT 2

Lou Montana: Text replacement - "([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}" 2021-11-15T22:56:15Z Text replacement - "<tt>([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}" ← Older revision Revision as of 00:56, 16 November 2021 Line 38: Line 38: === Conditional === === Conditional === You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is <tt>true</tt>. Note that there is no equivalent for "else". A conditional line must start with <tt>?</tt>, followed by the condition and <tt>:</tt>, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line. You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl|true}}. Note that there is no equivalent for "else". A conditional line must start with <tt>?</tt>, followed by the condition and <tt>:</tt>, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line. ? CONDITION : STATEMENT 1; STATEMENT 2 ? CONDITION : STATEMENT 1; STATEMENT 2 Lou Montana: Text replacement - "Script (File)" to "Script File" 2021-08-28T17:23:36Z Text replacement - "Script (File)" to "Script File" ← Older revision Revision as of 19:23, 28 August 2021 Line 55: Line 55: == See also == == See also == * [[SQF Syntax]] * [[SQF Syntax]] * [[Script (File)]] * [[Script File]] * [[Statement]] * [[Statement]] * [[Block]] * [[Block]] [[Category: Syntax]] [[Category: Syntax]] Lou Montana: Text replacement - "[[Script (File)|" to "[[Script File|" 2021-08-28T17:20:53Z Text replacement - "[[Script (File)|" to "[[Script File|" ← Older revision Revision as of 19:20, 28 August 2021 Line 1: Line 1: {{TOC|side|1|}} {{TOC|side|1|}} [[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script (File)|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]]. [[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script File|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]]. == Rules == == Rules == Line 29: Line 29: === Label === === Label === You may define labels in the code by beginning a line with <tt>#</tt>, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script (File)|script]] to jump to this label. You may define labels in the code by beginning a line with <tt>#</tt>, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File|script]] to jump to this label. #Label1 #Label1 Lou Montana: Text replacement - "[[sqs syntax" to "[[SQS Syntax" 2021-03-24T22:09:38Z Text replacement - "[[sqs syntax" to "[[SQS Syntax" ← Older revision Revision as of 00:09, 25 March 2021 Line 48: Line 48: == Notes == == Notes == Due to line-based nature of [[sqs syntax|Sqs scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros). Due to line-based nature of [[SQS Syntax|Sqs scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros). == Limitations == == Limitations == Lou Montana: Text replacement - "\[\[SQS[ _]syntax" to "[[SQS Syntax" 2021-03-24T22:07:27Z Text replacement - "\[\[SQS[ _]syntax" to "[[SQS Syntax" ← Older revision Revision as of 00:07, 25 March 2021 Line 1: Line 1: {{TOC|side|1|}} {{TOC|side|1|}} [[SQS syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script (File)|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]]. [[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script (File)|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]]. == Rules == == Rules == Lou Montana: Text replacement - "\[\[SQF[ _]syntax" to "[[SQF Syntax" 2021-03-24T22:01:19Z Text replacement - "\[\[SQF[ _]syntax" to "[[SQF Syntax" ← Older revision Revision as of 00:01, 25 March 2021 Line 1: Line 1: {{TOC|side|1|}} {{TOC|side|1|}} [[SQS syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script (File)|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF syntax]]. [[SQS syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax|syntax]] in [[:Category:Operation Flashpoint|{{ofp}}]] and is still available in {{GameCategory|arma1|link=y}}. It can only be used for [[Script (File)|scripts]], but not for [[Function|functions]], in the [[ArmA: Mission Editor|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]]. == Rules == == Rules == Line 43: Line 43: === @ === === @ === Much like the [[waitUntil]] statement in [[SQF syntax]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]]. Much like the [[waitUntil]] statement in [[SQF Syntax]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]]. @ CONDITION @ CONDITION Line 54: Line 54: == See also == == See also == * [[SQF syntax]] * [[SQF Syntax]] * [[Script (File)]] * [[Script (File)]] * [[Statement]] * [[Statement]]

← Older revision		Revision as of 01:17, 16 November 2021
Line 29:		Line 29:

	=== Label ===		=== Label ===
	You may define labels in the code by beginning a line with ~~<tt>~~#~~</tt>~~, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.		You may define labels in the code by beginning a line with {{hl\|#}}, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.

	#Label1		#Label1
Line 38:		Line 38:

	=== Conditional ===		=== Conditional ===
	You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with ~~<tt>~~?~~</tt>~~, followed by the condition and ~~<tt>~~:~~</tt>~~, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.		You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with {{hl\|?}}, followed by the condition and {{hl\|:}}, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.

	? CONDITION : STATEMENT 1; STATEMENT 2		? CONDITION : STATEMENT 1; STATEMENT 2

← Older revision		Revision as of 00:56, 16 November 2021
Line 38:		Line 38:

	=== Conditional ===		=== Conditional ===
	You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is ~~<tt>~~true~~</tt>~~. Note that there is no equivalent for "else". A conditional line must start with <tt>?</tt>, followed by the condition and <tt>:</tt>, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.		You may query a [[Boolean]] condition and define code, that is executed ''only'' when the condition is {{hl\|true}}. Note that there is no equivalent for "else". A conditional line must start with <tt>?</tt>, followed by the condition and <tt>:</tt>, followed by one or more commands. Multiple commands are separated by commas (,) or semicolons (;). The conditional statement ends with the end of the line.

	? CONDITION : STATEMENT 1; STATEMENT 2		? CONDITION : STATEMENT 1; STATEMENT 2

← Older revision		Revision as of 19:23, 28 August 2021
Line 55:		Line 55:
	== See also ==		== See also ==
	* [[SQF Syntax]]		* [[SQF Syntax]]
	* [[Script (File)]]		* [[Script File]]
	* [[Statement]]		* [[Statement]]
	* [[Block]]		* [[Block]]

	[[Category: Syntax]]		[[Category: Syntax]]

← Older revision		Revision as of 19:20, 28 August 2021
Line 1:		Line 1:
	{{TOC\|side\|1\|}}		{{TOC\|side\|1\|}}
	[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script (File)\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].		[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script File\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].

	== Rules ==		== Rules ==
Line 29:		Line 29:

	=== Label ===		=== Label ===
	You may define labels in the code by beginning a line with <tt>#</tt>, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script (File)\|script]] to jump to this label.		You may define labels in the code by beginning a line with <tt>#</tt>, followed by the name of the label (without spaces). You may use the command [[goto]] at any point of the [[Script File\|script]] to jump to this label.

	#Label1		#Label1

← Older revision		Revision as of 00:09, 25 March 2021
Line 48:		Line 48:

	== Notes ==		== Notes ==
	Due to line-based nature of [[~~sqs syntax~~\|Sqs scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).		Due to line-based nature of [[SQS Syntax\|Sqs scripts]] it is not possible to create multiline string constants in them. To overcome this limitation you can store multiline in separate SQF [[Function\|function]] files and load them using [[loadFile]] or [[preprocessFile]] (the second uses C-like preprocessor with // or /* */ comments and #define macros).

	== Limitations ==		== Limitations ==

← Older revision		Revision as of 00:07, 25 March 2021
Line 1:		Line 1:
	{{TOC\|side\|1\|}}		{{TOC\|side\|1\|}}
	[[SQS ~~syntax~~]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script (File)\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].		[[SQS Syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script (File)\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].

	== Rules ==		== Rules ==

← Older revision		Revision as of 00:01, 25 March 2021
Line 1:		Line 1:
	{{TOC\|side\|1\|}}		{{TOC\|side\|1\|}}
	[[SQS syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script (File)\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF ~~syntax~~]].		[[SQS syntax]] (where SQS stands for Status Quo Script) was the main [[Syntax\|syntax]] in [[:Category:Operation Flashpoint\|{{ofp}}]] and is still available in {{GameCategory\|arma1\|link=y}}. It can only be used for [[Script (File)\|scripts]], but not for [[Function\|functions]], in the [[ArmA: Mission Editor\|Mission Editor]] or in addon config files. The alternative syntax is [[SQF Syntax]].

	== Rules ==		== Rules ==
Line 43:		Line 43:

	=== @ ===		=== @ ===
	Much like the [[waitUntil]] statement in [[SQF ~~syntax~~]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]].		Much like the [[waitUntil]] statement in [[SQF Syntax]], @ will evaluate a certain condition, and the script will pause until @ returns [[true]].

	@ CONDITION		@ CONDITION
Line 54:		Line 54:

	== See also ==		== See also ==
	* [[SQF ~~syntax~~]]		* [[SQF Syntax]]
	* [[Script (File)]]		* [[Script (File)]]
	* [[Statement]]		* [[Statement]]

SQS Syntax - Revision history

Lou Montana: Some wiki formatting

Lou Montana: Add Tilde operator

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "([^= ]+)<\/tt>" to "{{hl|$1}}"

Lou Montana: Text replacement - "([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}"

Lou Montana: Text replacement - "Script (File)" to "Script File"

Lou Montana: Text replacement - "[[Script (File)|" to "[[Script File|"

Lou Montana: Text replacement - "[[sqs syntax" to "[[SQS Syntax"

Lou Montana: Text replacement - "\[\[SQS[ _]syntax" to "[[SQS Syntax"

Lou Montana: Text replacement - "\[\[SQF[ _]syntax" to "[[SQF Syntax"

Lou Montana: Text replacement - "`([^= ]+)<\/tt>" to "{{hl|$1}}"`

Lou Montana: Text replacement - "`([a-zA-Z0-9\. _"\\']+)<\/tt>" to "{{hl|$1}}"`