Conditions and Values - Revision history

EK at 12:03, 9 June 2025

2025-06-09T12:03:20Z

EK at 09:31, 16 January 2024

2024-01-16T09:31:55Z

EK at 22:12, 15 January 2024

2024-01-15T22:12:37Z

EK at 23:31, 23 February 2023

2023-02-23T23:31:48Z

EK at 12:59, 5 January 2023

2023-01-05T12:59:36Z

EK at 09:14, 20 October 2022

2022-10-20T09:14:04Z

EK at 20:46, 15 October 2022

2022-10-15T20:46:19Z

EK at 13:56, 10 October 2022

2022-10-10T13:56:49Z

EK at 18:31, 9 October 2022

2022-10-09T18:31:16Z

EK at 18:31, 8 October 2022

2022-10-08T18:31:58Z

← Older revision		Revision as of 12:03, 9 June 2025
Line 10:		Line 10:
	* <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition\|"Change condition"]] action part.		* <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition\|"Change condition"]] action part.
	* <span class="inlinecode>Combined:</span> This allows you to combine several conditions, values, and Lua queries through logical operators ("and", "or", "negate"). It is not possible to set the value of combined conditions directly; their value results from the variables/statements it is made up of.		* <span class="inlinecode>Combined:</span> This allows you to combine several conditions, values, and Lua queries through logical operators ("and", "or", "negate"). It is not possible to set the value of combined conditions directly; their value results from the variables/statements it is made up of.
		+
		+
		+	If you want to query conditions through Lua script, be aware that you have to use the <span class="inlinecode>system.getCondition</span> function to get the value of combined conditions:
		+
		+	<syntaxhighlight lang="lua">
		+	-- works for single conditions only
		+	if Conditions["door_closed"].Value then
		+	-- do something
		+	end
		+
		+	-- works for all conditions, including combined conditions
		+	if system.getCondition(Conditions["door_closed"]) then
		+	-- do something
		+	end
		+	</syntaxhighlight>

@@ Line 7: / Line 7: @@
 [[File:Conditions.png|thumb|Adding conditions]]
-<strong>Conditions</strong> are boolean based variables and contain either the value of "true" or "false". You can create 2 types of conditions:<br/>
+<strong>Conditions</strong> are boolean based variables and contain a value of either "true" or "false". You can create 2 types of conditions:<br/>
 * <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition|"Change condition"]] action part.
-* <span class="inlinecode>Combined:</span> This allows you to combine several conditions, values, and Lua queries through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the variables/statements it is made up of.
+* <span class="inlinecode>Combined:</span> This allows you to combine several conditions, values, and Lua queries through logical operators ("and", "or", "negate"). It is not possible to set the value of combined conditions directly; their value results from the variables/statements it is made up of.

@@ Line 9: / Line 9: @@
 <strong>Conditions</strong> are boolean based variables and contain either the value of "true" or "false". You can create 2 types of conditions:<br/>
 * <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition|"Change condition"]] action part.
-* <span class="inlinecode>Combined:</span> This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
+* <span class="inlinecode>Combined:</span> This allows you to combine several conditions, values, and Lua queries through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the variables/statements it is made up of.

← Older revision		Revision as of 23:31, 23 February 2023
Line 62:		Line 62:

	[[File:Object condition.png\|thumb\|250px\|Control object visibility through condition]]		[[File:Object condition.png\|thumb\|250px\|Control object visibility through condition]]
−	The second use case for conditions and values is linking them directly to objects~~, dialogs~~ and interface buttons via the "Properties" tab for the aforementioned objects, to quickly determine if the object is active (shown) or disabled (hidden). If disabled then all images and animations for the object will be hidden and all actions associated with the object will also be disabled; the cursor will not recognize the object anymore. This is very useful for quickly changing the environment of the scene or any other scenes for that matter, regardless of whether they are a playable scene, cut-scene or menu.	+	The second use case for conditions and values is linking them directly to objects and interface buttons via the "Properties" tab for the aforementioned objects, to quickly determine if the object is active (shown) or disabled (hidden). If disabled then all images and animations for the object will be hidden and all actions associated with the object will also be disabled; the cursor will not recognize the object anymore. This is very useful for quickly changing the environment of the scene or any other scenes for that matter, regardless of whether they are a playable scene, cut-scene or menu.
		+
		+	Besides objects and interface buttons, you can also disable/enable dialog parts by linking a condition or a value to them.

@@ Line 53: / Line 53: @@
 == Build "if…else" queries ==
-[[File:Game logic example.png|thumb|Try to open a locked chest]]
+[[File:Game logic example.png|thumb|250px|Try to open a locked chest]]
 The obvious use of conditions and values is for building your game logic through "if…else" queries: if a condition is true, do one thing; if it is false, do another thing. Or: if a value is greater than 5, do one thing; if it is less than 5 but greater than 0, do a second thing; if it is less than 0, do a third thing.
@@ Line 61: / Line 61: @@
 == Disable/Enable objects ==
-[[File:Object condition.png|thumb|Control object visibility through condition]]
+[[File:Object condition.png|thumb|250px|Control object visibility through condition]]
 The second use case for conditions and values is linking them directly to objects, dialogs and interface buttons via the "Properties" tab for the aforementioned objects, to quickly determine if the object is active (shown) or disabled (hidden). If disabled then all images and animations for the object will be hidden and all actions associated with the object will also be disabled; the cursor will not recognize the object anymore. This is very useful for quickly changing the environment of the scene or any other scenes for that matter, regardless of whether they are a playable scene, cut-scene or menu.
 <div style="clear:both"></div>
 {{toc}}

@@ Line 1: / Line 1: @@
 <strong>Conditions and Values</strong> are a fundamental necessity when it comes to game development as they allow us to dictate the events that can take place, have taken place or have yet to take place. They can also be used in "if…else" queries to determine if an event, or multiple events should be allowed to occur based on a condition's value or the integer number of a value.
-Both conditions and values can be defined in various locations throughout the editor; there are "Conditions" and "Values" tabs everywhere. From the engine's perspective it doesn't matter where you add them, because they are accessible from anywhere. To keep track of your game logic it makes sense though to add them in places where they logically belong. – ''If you need a condition called "key_taken" to control the visibility of a key object, you should add this condition at the key object or at the corresponding scene rather than at, let's say a character that appears somewhere else in your game. But wherever you put it, you may always link it for setting the state/visibility of your key.''
+Both conditions and values can be defined in various locations throughout the editor; there are "Conditions" and "Values" tabs everywhere. From the engine's perspective it doesn't matter where you add them, because they are accessible from anywhere. To keep track of your game logic it makes sense though to add them in places where they logically belong. – ''If you need a condition called "key_taken" to control the visibility of a key object, you should add this condition to the key object or to the corresponding scene rather than to, let's say a character that appears somewhere else in your game. But wherever you put it, you may always link it for setting the state/visibility of your key.''
@@ Line 8: / Line 8: @@
 [[File:Conditions.png|thumb|Adding conditions]]
 <strong>Conditions</strong> are boolean based variables and contain either the value of "true" or "false". You can create 2 types of conditions:<br/>
-* <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition|"Change condition" action part]].
+* <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition|"Change condition"]] action part.
 * <span class="inlinecode>Combined:</span> This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
@@ Line 17: / Line 17: @@
 [[File:Values.png|thumb|Adding values]]
-<strong>Values</strong> are first and foremost integer based variables. When adding them, you define an initial value which may be a fixed or a random number from a range you set. During the game you have multiple options inside of the [[Action Parts#Set value|"Set value" action part]] such as directly setting a new integer value (=), adding to current value (+), subtracting from current value (-), multiplying current value (*), and dividing the current value (/). You can also link another value variable to take its number value. The [[Action Parts#Set random value|"Set random value" action part]] allows you to set a random value.
+<strong>Values</strong> are first and foremost integer based variables. When adding them, you define an initial value which may be a fixed or a random number from a range you set. During the game you have multiple options inside of the [[Action Parts#Set value|"Set value"]] action part such as directly setting a new integer value (=), adding to current value (+), subtracting from current value (-), multiplying current value (*), and dividing the current value (/). You can also link another value variable to take its number value. The [[Action Parts#Set random value|"Set random value"]] action part allows you to set a random value.
@@ Line 48: / Line 48: @@
-''Example 1:<br>Let's say you have an integer type value called "money" which contains the initial value of 100.''
+See the [[Text#Display_values|text page]] for some examples.

← Older revision		Revision as of 20:46, 15 October 2022
Line 65:		Line 65:


−	== ~~Control object states~~ ==	+	== Disable/Enable objects ==

	[[File:Object condition.png\|thumb\|Control object visibility through condition]]		[[File:Object condition.png\|thumb\|Control object visibility through condition]]

@@ Line 8: / Line 8: @@
 [[File:Conditions.png|thumb|Adding conditions]]
 <strong>Conditions</strong> are boolean based variables and contain either the value of "true" or "false". You can create 2 types of conditions:<br/>
-#<span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the "Change condition" action part.
+* <span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the [[Action Parts#Change condition|"Change condition" action part]].
-#<span class="inlinecode>Combined:</span> This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
+* <span class="inlinecode>Combined:</span> This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
@@ Line 17: / Line 17: @@
 [[File:Values.png|thumb|Adding values]]
-<strong>Values</strong> are first and foremost integer based variables. When adding them, you define an initial value which may be a fixed or a random number from a range you set. During the game you have multiple options inside of the "Set value" action part such as directly setting a new integer value (=), adding to current value (+), subtracting from current value (-), multiplying current value (*), and dividing the current value (/). You can also link another value variable to take its number value. The "Set random value" action part allows you to set a random value.
+<strong>Values</strong> are first and foremost integer based variables. When adding them, you define an initial value which may be a fixed or a random number from a range you set. During the game you have multiple options inside of the [[Action Parts#Set value|"Set value" action part]] such as directly setting a new integer value (=), adding to current value (+), subtracting from current value (-), multiplying current value (*), and dividing the current value (/). You can also link another value variable to take its number value. The [[Action Parts#Set random value|"Set random value" action part]] allows you to set a random value.
 === String variables ===
-It is also possible to use a value as a string variable instead of as an integer variable. You may set the initial string, but you can't change the string value via the "Set value" or any other action part, nor can you use the string value in an action part "if…else" query or link it to an object. You need Lua scripting to make use of string type values:
+It is also possible to use a value as a string variable instead of as an integer variable. You may set the initial string when adding the value, but you can't change the string via the "Set value" or any other action part, nor can you use the string value in an action part "if…else" query or link it to an object. You need Lua scripting to make use of string type values:
 <syntaxhighlight lang="lua">
@@ Line 62: / Line 62: @@
 The obvious use of conditions and values is for building your game logic through "if…else" queries: if a condition is true, do one thing; if it is false, do another thing. Or: if a value is greater than 5, do one thing; if it is less than 5 but greater than 0, do a second thing; if it is less than 0, do a third thing.
-Use the "If condition" and "If value" action parts to create these structures. There are more "If" action parts available querying other aspects of the game.
+Use the "If condition" and "If value" action parts to create these structures. There are more [[Action Parts#Condition.2C_If.2C_Value|"If" action parts]] available querying other aspects of the game, such as "If character has item", "If character is on scene", or "If language is current language".

@@ Line 8: / Line 8: @@
 [[File:Conditions.png|thumb|Adding conditions]]
 <strong>Conditions</strong> are boolean based variables and contain either the value of "true" or "false". You can create 2 types of conditions:<br/>
-#'''Variable''': This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the "Change condition" action part.
+#<span class="inlinecode>Variable:</span> This is a single condition which contains a boolean value of "true" or "false". When adding it, you define an initial value and can change that value at any time during the game through the "Change condition" action part.
-#'''Combined''': This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
+#<span class="inlinecode>Combined:</span> This allows you to combine several conditions through logical operators ("and", "or", "negate"). It is not possible to directly set the value of combined conditions; their value results from the conditions it is made up of.
@@ Line 44: / Line 44: @@
 You may print out values as part of a text, both integer and string type values. Use the following markup:
-* Integers: <code><v=value_name></code>
+* Integers: <span class="inlinecode><v=value_name></span>
-* Strings: <code><vs=value_name></code>
+* Strings: <span class="inlinecode><vs=value_name></span>