Ifvar conditions - Revision history

Hendricks266 at 19:05, 15 December 2024

2024-12-15T19:05:58Z

← Older revision		Revision as of 12:05, 15 December 2024
Line 1:		Line 1:
	<span {{code}}>'''if'''<'''conditional'''> <[[gamevar]]> <constant\|gamevar> <then_branch> ['''[[else]]''' <else_branch>]</span>		<span {{code}}>'''if'''<'''conditional'''> <gamevar> <constant\|gamevar> <then_branch> ['''[[else]]''' <else_branch>]</span>

	<span {{code}}>'''ifvar'''<'''conditional'''> <[[gamevar]]> <constant> <then_branch> ['''[[else]]''' <else_branch>]</span>		<span {{code}}>'''ifvar'''<'''conditional'''> <gamevar> <constant> <then_branch> ['''[[else]]''' <else_branch>]</span> ''(deprecated)''

	~~<span {{code}}>'''ifvarvar'''<'''conditional'''> <[[gamevar]]> <[[gamevar]]> <then_branch> [~~'''~~[[else]]~~'~~'' <else_branch>]</span>~~

			<span {{code}}>'''ifvarvar'''<'''conditional'''> <gamevar> <gamevar> <then_branch> ['''[[else]]''' <else_branch>]</span> ''(deprecated)''

	Ifvar conditions are [[if condition]]s that apply to [[gamevar]]s.		Ifvar conditions are [[if condition]]s that apply to [[gamevar]]s.
Line 12:		Line 11:
	If the comparison returns true, the game will execute the code in the ''<then_branch>''. If false, the ''<else_branch>'' may be executed if present, otherwise the block is skipped.		If the comparison returns true, the game will execute the code in the ''<then_branch>''. If false, the ''<else_branch>'' may be executed if present, otherwise the block is skipped.

	The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.		The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces (<code>{</code> and <code>}</code>). For performance reasons, do not use curly braces for single commands.

	To negate a conditional (e.g. you want to ~~compute a~~ '''~~nand~~''') place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.		To negate a conditional (e.g. you want to check that an '''and''' is ''not'' true) place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.

	See also: [[~~Else~~]]		See also: [[else]]

	== Chaining if statements ==		== Chaining if statements ==

Hendricks266: /* Types of ifvar conditions */

2024-12-15T18:42:48Z

Types of ifvar conditions

← Older revision		Revision as of 11:42, 15 December 2024
Line 48:		Line 48:
	\|-		\|-
	\|e		\|e
	\|==		\|<code>==</code>
	\|=		\|=
	\|equal to		\|equal to
	\|-		\|-
	\|n		\|n
	\|!=		\|<code>!=</code>
	\|≠		\|≠
	\|not equal to		\|not equal to
	\|-		\|-
	\|g		\|g
	\|>		\|<code>></code>
	\|>		\|>
	\|greater than		\|greater than
	\|-		\|-
	\|ge		\|ge
	\|>=		\|<code>>=</code>
	\|≥		\|≥
	\|greater or ~~equals~~		\|greater or equal
	\|-		\|-
	\|a		\|a
	\|		\|
	\|		\|
	\|unsigned greater than ~~(both operands~~)		\|above (unsigned greater than)
	\|-		\|-
	\|ae		\|ae
	\|		\|
	\|		\|
	\|unsigned greater or equal ~~(both operands~~)		\|above or equal (unsigned greater or equal)
	\|-		\|-
	\|l		\|l
	\|<		\|<code><</code>
	\|<		\|<
	\|less than		\|less than
	\|-		\|-
	\|le		\|le
	\|<=		\|<code><=</code>
	\|≤		\|≤
	\|less or equal		\|less or equal
Line 90:		Line 90:
	\|		\|
	\|		\|
	\|unsigned less than ~~(both operands~~)		\|below (unsigned less than)
	\|-		\|-
	\|be		\|be
	\|		\|
	\|		\|
	\|unsigned less or equal ~~(both operands~~)		\|below or equal (unsigned less or equal)
	\|-		\|-
	\|and		\|and
	\|&		\|<code>&</code>
	\|		\|
	\|bitwise AND		\|bitwise AND
	\|-		\|-
	\|or		\|or
	\|<nowiki>\|</nowiki>		\|<code><nowiki>\|</nowiki></code>
	\|		\|
	\|bitwise OR		\|bitwise OR
	\|-		\|-
	\|xor		\|xor
	\|^		\|<code>^</code>
	\|		\|
	\|bitwise XOR		\|bitwise XOR
	\|-		\|-
	\|both		\|both
	\|<nowiki>&&</nowiki>		\|<code><nowiki>&&</nowiki></code>
	\|		\|
	\|logical AND: both are non-zero		\|logical AND: both are non-zero
	\|-		\|-
	\|either		\|either
	\|<nowiki>\|\|</nowiki>		\|<code><nowiki>\|\|</nowiki></code>
	\|		\|
	\|logical OR: either are non-zero		\|logical OR: either are non-zero
	\|}		\|}

			The above and below operators are useful for validating that a gamevar is a valid index into an array, because by interpreting its value as [[Wikipedia:signedness\|unsigned]] when comparing against the array size, you can rule out when the gamevar is negative and when it is larger than or equal to the array size in one comparison operation instead of two.

	{{varsuffix}}		{{varsuffix}}

Doom64hunter: Undo revision 14162 by Doom64hunter (talk) (just had a double brainfart...)

2021-01-12T13:37:01Z

Undo revision 14162 by Doom64hunter (talk) (just had a double brainfart...)

← Older revision		Revision as of 06:37, 12 January 2021
Line 14:		Line 14:
	The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.		The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.

	To negate a conditional, place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.		To negate a conditional (e.g. you want to compute a '''nand''') place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.

	See also: [[Else]]		See also: [[Else]]

Doom64hunter: I am dumb

2021-01-12T13:32:49Z

I am dumb

← Older revision		Revision as of 06:32, 12 January 2021
Line 14:		Line 14:
	The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.		The branches may consist of a single command, or if multiple commands need to be executed, a block of code enclosed in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.

	To negate a conditional ~~(e.g. you want to compute a '''nand''')~~ place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.		To negate a conditional, place a [[nullop]] inside the ''<then>'' branch, and put the code to be executed inside the ''<else>'' branch.

	See also: [[Else]]		See also: [[Else]]

Doom64hunter: Removed comment stating "less than or equal to conditionals are unnecessary" and added the missing conditional types.

2021-01-12T13:03:42Z

Removed comment stating "less than or equal to conditionals are unnecessary" and added the missing conditional types.

@@ Line 1: / Line 1: @@
-'''ifvar'''<'''conditional'''> <[[gamevar]]> <constant><br>
+<span {{code}}>'''if'''<'''conditional'''> <[[gamevar]]> <constant|gamevar> <then_branch>  ['''[[else]]''' <else_branch>]</span>
-Ifvar conditions are special [[if condition]]s that apply to [[gamevar]]s.  These statements work by comparing the two inputs using the conditional provided as part of the command.  If the resulting comparison or operation is true, the game will then execute the code specified. If only one CON command is to be performed, simply put it after the condition.  For best reading, put it on the same line or on the following line, indented.  For longer chains, enclose the code in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands.  [[Else]] statements can also be used.  If you want to do nothing, followed by an else, in place of a command you can write <code>[[nullop]]</code> or <code>{ }</code>.
+<span {{code}}>'''ifvar'''<'''conditional'''> <[[gamevar]]> <constant> <then_branch> ['''[[else]]''' <else_branch>]</span>
 {| {{prettytable}}
@@ Line 11: / Line 51: @@
 |=
 |equal to
 |-
 |l
@@ Line 17: / Line 82: @@
 |less than
 |-
-|g
+|le
-|>
+|<=
-|>
+|&le;
-|greater than
+|less or equal
 |-
-|n
+|be
-|!=
-|&ne;
-|not equal to
+|unsigned less or equal (both operands)
 |-
 |and
@@ Line 41: / Line 111: @@
+|
 |bitwise XOR
 |-
 |either
@@ Line 47: / Line 122: @@
 |logical OR: either are non-zero
 |}
 {{varsuffix}}

Jblade: didn't see the ife stuff was already there

2020-08-02T05:36:34Z

didn't see the ife stuff was already there

← Older revision		Revision as of 22:36, 1 August 2020
Line 48:		Line 48:
	\|}		\|}

	Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary. ~~As a shorthand you can drop the 'var' from the command and just use ife for ifvare, ifn for ifvarn, .etc~~		Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary.

	{{varsuffix}}		{{varsuffix}}

Jblade at 05:35, 2 August 2020

2020-08-02T05:35:37Z

← Older revision		Revision as of 22:35, 1 August 2020
Line 2:		Line 2:
	'''ifvarvar'''<'''conditional'''> <[[gamevar]]> <[[gamevar]]>		'''ifvarvar'''<'''conditional'''> <[[gamevar]]> <[[gamevar]]>

	Ifvar conditions are special [[if condition]]s that apply to [[gamevar]]s. These statements work by comparing the two inputs using the conditional provided as part of the command. If the resulting comparison or operation is true, the game will then execute the code specified. If only one CON command is to be performed, simply put it after the condition. For best reading, put it on the same line or on the following line, indented. For longer chains, enclose the code in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands. [[Else]] statements can also be used. If you want to do nothing, followed by an else, in place of a command you can write <code>[[nullop]]</code> or <code>{ }</code>.		Ifvar conditions are special [[if condition]]s that apply to [[gamevar]]s. These statements work by comparing the two inputs using the conditional provided as part of the command. If the resulting comparison or operation is true, the game will then execute the code specified. If only one CON command is to be performed, simply put it after the condition. For best reading, put it on the same line or on the following line, indented. For longer chains, enclose the code in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands. [[Else]] statements can also be used. If you want to do nothing, followed by an else, in place of a command you can write <code>[[nullop]]</code> or <code>{ }</code>.

	{\| {{prettytable}}		{\| {{prettytable}}
Line 48:		Line 48:
	\|}		\|}

	Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary.		Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary. As a shorthand you can drop the 'var' from the command and just use ife for ifvare, ifn for ifvarn, .etc

	{{varsuffix}}		{{varsuffix}}

Hendricks266 at 07:12, 4 January 2016

2016-01-04T07:12:36Z

← Older revision		Revision as of 00:12, 4 January 2016
Line 1:		Line 1:
	'''ifvar'''<'''conditional'''> <[[gamevar]]> <~~value~~><br>		'''ifvar'''<'''conditional'''> <[[gamevar]]> <constant><br>
	'''ifvarvar'''<'''conditional'''> <[[gamevar]]> <~~value~~>		'''ifvarvar'''<'''conditional'''> <[[gamevar]]> <[[gamevar]]>

	Ifvar conditions are special [[if condition]]s that apply to [[gamevar]]s. These statements work by comparing the two inputs using the conditional provided as part of the command. If the resulting comparison or operation is true, the game will then execute the code specified. If only one CON command is to be performed, simply put it after the condition. For best reading, put it on the same line or on the following line, indented. For longer chains, enclose the code in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands. [[Else]] statements can also be used. If you want to do nothing, followed by an else, in place of a command you can write <code>[[nullop]]</code> or <code>{ }</code>.		Ifvar conditions are special [[if condition]]s that apply to [[gamevar]]s. These statements work by comparing the two inputs using the conditional provided as part of the command. If the resulting comparison or operation is true, the game will then execute the code specified. If only one CON command is to be performed, simply put it after the condition. For best reading, put it on the same line or on the following line, indented. For longer chains, enclose the code in curly braces ("{" and "}"). For performance reasons, do not use curly braces for single commands. [[Else]] statements can also be used. If you want to do nothing, followed by an else, in place of a command you can write <code>[[nullop]]</code> or <code>{ }</code>.

Hendricks266 at 00:25, 25 May 2012

2012-05-25T00:25:56Z

← Older revision		Revision as of 17:25, 24 May 2012
Line 53:		Line 53:

	[[Category:Gamevar manipulation]]		[[Category:Gamevar manipulation]]
			[[Category:If conditions]]

Hendricks266 at 03:33, 25 February 2011

2011-02-25T03:33:58Z

← Older revision		Revision as of 20:33, 24 February 2011
Line 50:		Line 50:
	Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary.		Since CON variables are integer-only, "less-than or equal to" (le, <=, ≤) and "greater-than or equal to" (ge, >=, ≥) conditionals are unnecessary.

	~~Commands with an additional "var" suffix take [[gamevar]]s rather than constants or [[define]]d labels for their inputs.~~		{{varsuffix}}

	[[Category:Gamevar manipulation]]		[[Category:Gamevar manipulation]]