Variables - Revision history

U3312106 at 06:59, 3 March 2023

2023-03-03T06:59:20Z

U3312106: Added a description

2021-02-11T10:53:36Z

Added a description

U3312106: Fixed link

2020-02-16T21:42:57Z

Fixed link

U3312106: Changed one word because it did not make any sense before

2019-11-08T01:21:50Z

Changed one word because it did not make any sense before

U3312106: Some grammar corrections

2019-11-06T22:17:58Z

Some grammar corrections

U3312106: Some grammar corrections

2019-11-04T11:37:22Z

Some grammar corrections

U3312106 at 00:16, 4 November 2019

2019-11-04T00:16:47Z

U3312106: Removed one line and corrected one description

2019-11-04T00:05:22Z

Removed one line and corrected one description

U3312106: Added one note

2019-11-03T22:44:30Z

Added one note

U41991654: Grammar fixes & optimizations

2019-11-03T21:51:55Z

Grammar fixes & optimizations

@@ Line 418: / Line 418: @@
 :You can increase the number of areas but you also need to increase the value of '''b_area_amount_int''' variable if you want to do that.
 :Link to the multiplayer mission that contains this set of triggers:
 :[https://drive.google.com/uc?export=download&id=1OxB0E0TVt5mZtS3_mPmMLPBzsH2aVaxn test_gamemode_tanks.blk]

@@ Line 61: / Line 61: @@
 * value: Select the type of value (checked - True, unchecked - False)
 * input_var: Select if you want to input the value from other variables
-* fromDescriptor: unknown
+* fromDescriptor: Makes the action load values from the server, can not be used by players
 </div></div>
 |-
@@ Line 76: / Line 76: @@
 * source_var: Select if you want to input values from ongoing battle (overwrites current '''value''')
 * input_var: Select if you want to input the value from other variables
-* fromDescriptor: unknown
+* fromDescriptor: Makes the action load values from the server, can not be used by players
 </div></div>
 |-
@@ Line 90: / Line 90: @@
 * value: Set the number
 * input_var: Select if you want to input the value from other variables
-* fromDescriptor: unknown
+* fromDescriptor: Makes the action load values from the server, can not be used by players
 </div></div>
 |-
@@ Line 104: / Line 104: @@
 * value: Set the text
 * input_var: Select if you want to input the value from other variables
-* fromDescriptor: unknown
+* fromDescriptor: Makes the action load values from the server, can not be used by players
 </div></div>
 |-
@@ Line 126: / Line 126: @@
 * value: Set the text
 * input_var: Select if you want to input the value from other variables
-* fromDescriptor: unknown
+* fromDescriptor: Makes the action load values from the server, can not be used by players
 </div></div>
 |-

@@ Line 419: / Line 419: @@
 :Link to the multiplayer mission that contains this set of triggers:
-:[http://drive.google.com/uc?export=download&id=1OxB0E0TVt5mZtS3_mPmMLPBzsH2aVaxn test_gamemode_tanks.blk]
+:[https://drive.google.com/uc?export=download&id=1OxB0E0TVt5mZtS3_mPmMLPBzsH2aVaxn test_gamemode_tanks.blk]
 :Remember that you need to remove '''https://''' part of this link to make it work in War Thunder.
 [[Category:War Thunder CDK]]
 [[Category:Custom missions]]

@@ Line 109: / Line 109: @@
 |}
 :* Using '''varAddString''' action
-:: This way you can add a text to existing string variable by adding a '''value''' in the field with same name or a number and setting it selected amount of shown '''digits''' (for example if you add a '''3''' number and set '''digits''' to '''2''' then it will be shown as '''03'''), you can also input all these values from other variables
+:: This way you can add a text to existing string variable by adding a '''value''' in the field with same name or a number and set selected amount of shown '''digits''' (for example if you add a '''3''' number and set '''digits''' to '''2''' then it will be shown as '''03'''), you can also input all these values from other variables
 ::{| class="wikitable" style="width: 90%;"
 |+

@@ Line 109: / Line 109: @@
 |}
 :* Using '''varAddString''' action
-:: This way you can add a text to existing string variable by adding a '''value''' in the field with same name or a number and seting it selected amount of shown '''digits''' (for example if you add a '''3''' number and set '''digits''' to '''2''' then it will be shown as '''03'''), you can also input all these values from other variables
+:: This way you can add a text to existing string variable by adding a '''value''' in the field with same name or a number and setting it selected amount of shown '''digits''' (for example if you add a '''3''' number and set '''digits''' to '''2''' then it will be shown as '''03'''), you can also input all these values from other variables
 ::{| class="wikitable" style="width: 90%;"
 |+
@@ Line 260: / Line 260: @@
 :: They can't overlap with each other because if that happens it can break the mission, there should be at least 5 meters of free space between areas
 :* Rename all areas to b_area_01, b_area_02, b_area_03 etc.
-:: Remember that they can't be named in random order, it's the best to name them from the left to the right or in reverse order
+:: Remember that they can't be named in random order, it is the best to name them from the left to the right or in reverse order
 Here's a screenshot showing how it should look:
@@ Line 275: / Line 275: @@
 :'''Events'''
 ::* Periodic Event = 0.01
-::: Set it to 0.01 so it will be able stwich between areas as fast as it's possible
+::: Set it to 0.01 so it will be able switch between areas as fast as it is possible
 :'''Conditions'''
 ::* varCompareInt (var_value = b_area_int, value = 0, var_value_other = b_area_amount_int, comparison_func = equal)
-::: This condition will keep changing the number of '''b_area_int''' variable (at the start of mission it's set to 0) until it reaches 36
+::: This condition will keep changing the number of '''b_area_int''' variable (at the start of mission it is set to 0) until it reaches 36
 :'''Actions'''
 ::: This part will start working once the trigger will reach the '''36''' number
@@ Line 312: / Line 312: @@
 :'''Events'''
 ::* Periodic Event = 0.01
-::: Just like before, to make it work as fast as it's possible
+::: Just like before, to make it work as fast as it is possible
 :'''Conditions'''
 ::* varCompareInt (var_value = "@b_area_string_check", value = 1 comparison func = "equal")
@@ Line 337: / Line 337: @@
 ===Creating triggers that give a number to ''b_area_xx_int'' variables and keep checking them until the mission ends===
-This trigger works like '''first_time_check_all_areas''', the only big difference is the part under '''Actions''', this time it's used to reset trigger state when '''b_area_int''' it reaches 36, other difference is a trigger that is enabled at the end of '''Actions''' and '''Else''', it's set to '''check_if_no_one_in_area''' now.
+This trigger works like '''first_time_check_all_areas''', the only big difference is the part under '''Actions''', this time it is used to reset trigger state when '''b_area_int''' it reaches 36, other difference is a trigger that is enabled at the end of '''Actions''' and '''Else''', it is set to '''check_if_no_one_in_area''' now.
 :'''Trigger name''' = "switch_area"
 :'''Events'''
 ::* Periodic Event = 0.01
-::: Set it to 0.01 so it will be able stwich between areas as fast as it's possible
+::: Set it to 0.01 so it will be able switch between areas as fast as it is possible
 :'''Conditions'''
 ::* varCompareInt (var_value = b_area_int, value = 0, var_value_other = b_area_amount_int, comparison_func = equal)
-::: This condition will keep changing the number of '''b_area_int''' variable (at the start of mission it's set to 0) until it reaches 36
+::: This condition will keep changing the number of '''b_area_int''' variable (at the start of mission it is set to 0) until it reaches 36
 :'''Actions'''
 ::* varSetInt (value = 0, var = "b_area_int")
@@ Line 409: / Line 409: @@
 ::: If there are any units from the B team it will add 2 to it (2 = B team color) and if it already added 1 in the previous action then it will set it's color to white (3 - neutral color)
 ::* triggerEnable (target = "@when_t1" target = "@when_t2" target = "@when_both")
-::: When it's done with checking players it will enable triggers which will show an icon with proper color on the minimap
+::: When it is done with checking players it will enable triggers which will show an icon with proper color on the minimap
 :'''Else'''
 ::* triggerEnable (target = "@when_t1" target = "@when_t2" target = "@when_both")
-::: When it's done with checking players it will enable triggers which will show an icon with proper color on the minimap
+::: When it is done with checking players it will enable triggers which will show an icon with proper color on the minimap
 :After that, it will work exactly like in the previous part (3.).

@@ Line 5: / Line 5: @@
 Variables in mission editor are used to store information like text, numbers or booleans used for creating true or false statements, they can be used to optimize code of your mission and also to create things that are normally impossible without using them.
 If you create a string variable named '''t1_unit_01''' you will be able to see it in '''target''' or '''object''' tab which you can find in actions similar to '''unitSetProperties''' where you can select AI or player units, it's name will be displayed as '''@t1_unit_01''', it will be displayed similarly in other actions too.
-As mentioned before, they can also be used to optimize missions, but only when you need a really high amount of triggers that do perform similar functions, in case of small mission you won't even notice a difference and usually you will need more triggers than when just using simple actions without variables, so this article will explain how to use them and make a good use of them.
+As mentioned before, they can also be used to optimize missions, but only when you need a really high amount of triggers that do perform similar functions, in case of small mission you won't even notice a difference and usually you will need more triggers than when just using simple actions without variables, so this article will explain how to use them and show a good use of them.
 You can find some basic information about [https://wiki.warthunder.com/Triggers#List_of_all_Actions actions] and [https://wiki.warthunder.com/Triggers#List_of_all_Conditions conditions] with variables [https://wiki.warthunder.com/Triggers here], all their names start with '''var'''.
@@ Line 226: / Line 226: @@
 ===Adding variables===
-:: The first step to get things done is to add variables that you will need for your mission
+The first step to get things done is to add variables that you will need for your mission
 :* '''b_area_string'''
 :: String variable, it will store area's name and be used to check current area
@@ Line 254: / Line 254: @@
 ===Adding areas===
-:: The second step is to add areas
+The second step is to add areas
 :* Create 36 box areas that are placed next to each other
 :: It should create one big 6x6 box, so it should have 6 columns and 6 rows
@@ Line 321: / Line 321: @@
 ::: If the number of '''b_area_xx_int''' variable is set to 1 then it will show an icon with A team color, then enable '''switch_area''' trigger (it's name is stored in '''switch_area_string''' string) which will switch the area name to check to the next one (b_area_01 -> b_area_02, b_area_02 -> b_area_03 etc.)
 :'''Else'''
-::*missionShowMapIcon
+::*missionShowMapIcon (show = false, team = "both")
 ::*triggerDisable (target = "@when_t1")
 ::: If the number of '''b_area_xx_int''' variable is NOT set to 1 then it won't show the icon and just disable this trigger
@@ Line 330: / Line 330: @@
 ::* Copy this trigger two times and set the name of copies to '''when_t2''' and '''when_both''', then change their '''value'''s in '''varCompareInt''' to '''2''' for '''when_t2''' and '''3''' for '''when_both'''.
 ::* Change the color of icon in '''missionShowMapIcon''' (under '''actions''') to '''Team B''' for '''when_t2''' and  '''White''' for '''when_both'''.
-::* Change the '''target'<nowiki/>'' in '''''<nowiki/>''triggerDisable''' action, switch it to '''@when_t2''' for '''when_t2''' and '''@when_both''' for '''when_both''.
+::* Change the '''target''' in '''triggerDisable''' action, switch it to '''@when_t2''' for '''when_t2''' and '''@when_both''' for '''when_both'''.
 Now go back to the window with '''Variables''' and set values of all '''b_area_xx_int''' (xx = number) variables to 1, 2 or 3.
@@ Line 396: / Line 396: @@
 ''Note: If you wonder why there's the var set to '''@b_area_string_check''' and not '''b_area_string_check''' in '''varSetInt''' action.''
-If you just set it to '''b_area_string_check''' then it would look for this value: '''b_area_string_check:t = b_area_01_int'''
+''If you just set it to '''b_area_string_check''' then it would look for this value: '''b_area_string_check:t = b_area_01_int'''''
-If you set it to '''@b_area_string_check''' then it will look for this value: '''b_area_01_int:t = 0''' so it can check and set the number stored in currently checked area
+''If you set it to '''@b_area_string_check''' then it will look for this value: '''b_area_01_int:t = 0''' so it can check and set the number stored in currently checked area''
 :'''Trigger name''' = "check_if_t2_in_area"
@@ Line 414: / Line 414: @@
 ::: When it's done with checking players it will enable triggers which will show an icon with proper color on the minimap
-After that, it will work exactly like in the previous part (3.).
+:After that, it will work exactly like in the previous part (3.).
-if you did everything properly, then now this entire set of triggers should work like it was explained in the description of this section.
+:If you did everything properly, then now this entire set of triggers should work like it was explained in the description of this section.
-You can increase the number of areas but you also need to increase the value of '''b_area_amount_int''' variable if you want to do that.
+:You can increase the number of areas but you also need to increase the value of '''b_area_amount_int''' variable if you want to do that.
 :Link to the multiplayer mission that contains this set of triggers:

← Older revision		Revision as of 22:44, 3 November 2019
Line 13:		Line 13:

	:* You can't store more than one information in the same variable		:* You can't store more than one information in the same variable
		+	:* All of these instructions from this article are valid for both singleplayer and multiplayer missions

	= Basics =		= Basics =

@@ Line 4: / Line 4: @@
 Variables in mission editor are used to store information like text, numbers or booleans used for creating true or false statements, they can be used to optimize code of your mission and also to create things that are normally impossible without using them.
-If you create a string variable named '''t1_unit_01''' you will be able to see it in '''target''' or '''object''' tab which you can find in actions similar to '''unitSetProperties''' where you can select AI or player units, it's name will be displayed as '''@t1_unit_01''', t will be displayed in similar way in other actions too.
+If you create a string variable named '''t1_unit_01''' you will be able to see it in '''target''' or '''object''' tab which you can find in actions similar to '''unitSetProperties''' where you can select AI or player units, it's name will be displayed as '''@t1_unit_01''', it will be displayed similarly in other actions too.
 As mentioned before, they can also be used to optimize missions, but only when you need a really high amount of triggers that do perform similar functions, in case of small mission you won't even notice a difference and usually you will need more triggers than when just using simple actions without variables, so this article will explain how to use them and make a good use of them.
@@ Line 22: / Line 22: @@
 :1. Choose on the side toolbar '''Variables''', you can find it under '''Triggers''' tab
-:: Now you should bo able to see a window with multiple tabs that can be pressed, '''Add''' for adding new variables, '''Edit''' for editing, '''Del''' for deleting and '''Up''' and '''Down''' to move them.
+:: Now you should be able to see a window with multiple tabs that can be pressed, '''Add''' for adding new variables, '''Edit''' for editing, '''Del''' for deleting and '''Up''' and '''Down''' to move them.
 :2. Press '''Add''' to add a new variable
-:: After pressing it a new window should appear, you can select a name for it under '''Variable name:''' and select it's type under '''Variable type:''', there are 10 of them, but for now I'll only explain how to use string (text), interger (number without a fractional component), real (number with a fractional component) and bool (used for creating true or false statements)
+:: After pressing it a new window should appear, you can select a name for it under '''Variable name:''' and select its type under '''Variable type:''', there are 10 of them, but for now I'll only explain how to use string (text), integer (number without a fractional component), real (number with a fractional component) and bool (used for creating true or false statements)
 :3. Set the variable name to '''t1_unit_string_01''' and it's type to '''string'''
-:: Now you should have created a new string variable, the next thing to do is set it's value and assign it to something
+:: Now you should have created a new string variable, the next thing to do is set its value and assign it to something
 :4. Select created variable
-:: After selecting there should appear a new field where you can set it's value
+:: After selecting there should appear a new field where you can set its value
 :5. Set the variable value to '''t1_unit_01'''
 :: Now you need a new action where you can assign this variable
 :6. Go to the '''Triggers / Missions Obj. Navigat''' tab, find an '''unitSetProperties''' action and create it
 :7. Press '''object''' and select '''@t1_unit_string_01''', then scroll down and enable '''cannotShoot''' option
-:: It should assign a variable to this action and give it a simple propertie, now we need an unit which will use it
+:: It should assign a variable to this action and give it a simple property, now we need a unit which will use it
 :8. Create a new '''armada unit''' and call it '''t1_unit_01''' and make it a player unit
 :: If everything went without any issues then your unit shouldn't be able to fire and that will mean that you properly assigned a variable to unitSetProperties action
@@ Line 200: / Line 200: @@
 ::: var = t1_unit_int | type = integer | value = 12
-:: Now I want it to set the string to a name of unit that has a higher number (by 1)
+:: Now I want it to set the string to the name of a unit that has a higher number (by 1)
 ::: '''Actions:'''
@@ Line 214: / Line 214: @@
 == Creating a set of triggers that checks multiple areas for units ==
-This set of triggers is meant to check if there are units in selected area, then if there's at least one unit from the '''A''' or '''B''' team in it the mission should mark this area on the minimap with a color depending on which team is at this moment in that area.
+This set of triggers is meant to check if there are units in a selected area, then if there's at least one unit from the '''A''' or '''B''' team in it the mission should mark this area on the minimap with a colour depending on which team is at this moment in that area.
 If there are both teams in the same area then it should give it white neutral marking on the minimap.
-Mission should have 36 of those areas and they should be placed next to each other.
+The mission should have 36 of those areas and they should be placed next to each other.
 Here's a screenshot showing how it should look:
 [[File:Minimap for Variables article.jpg|left|thumb|232x232px]]
 {{break}}
-To make everything work properly you need 8 triggers, one that checks all areas at the start of mission, one that checks all areas later when the first one is disabled, three for checking if there are any units in them and from what team they are, another three triggers to mark all areas and obviously variables, in this case 42 of them.
+To make everything behave as intended, you need 8 triggers, one that checks all areas at the start of mission, one that checks all areas later when the first one is disabled, three for checking if there are any units in them and from what team they are, another three triggers to mark all areas and obviously variables, in this case 42 of them.
 ===Adding variables===
@@ Line 255: / Line 255: @@
 :: The second step is to add areas
 :* Create 36 box areas that are placed next to each other
-:: It should create a one big 6x6 box, so it should have 6 columns and 6 rows
+:: It should create one big 6x6 box, so it should have 6 columns and 6 rows
 :: Don't forget to set their size to 2000x2000 meters
 :: They can't overlap with each other because if that happens it can break the mission, there should be at least 5 meters of free space between areas
@@ Line 300: / Line 300: @@
 ::: It will enable all triggers that are needed to add an icon on the minimap
-Three similar triggers which main function will be to add an icon on the minimap
+Three similar triggers which the main function will be to add an icon on the minimap
 :'''Trigger name''' = "when_t1" - it will check the number assigned to '''b_area_xx_int''' (xx = number) variables, 1 - set the icon color to A team
@@ Line 307: / Line 307: @@
 This one is for '''when_t1'''
-Every time only one of these trigger will be used and the rest of them will disable itself it they don't meet the condition
+Every time only one of these triggers will be used and the rest of them will abort should they not meet the condition
 :'''Events'''
@@ Line 325: / Line 325: @@
-Now you will need to copy this trigger to make it work for every color (blue, red and white)
+Now you will need to copy this trigger to make it work for every colour (blue, red and white)
 ::* Copy this trigger two times and set the name of copies to '''when_t2''' and '''when_both''', then change their '''value'''s in '''varCompareInt''' to '''2''' for '''when_t2''' and '''3''' for '''when_both'''.
@@ Line 414: / Line 414: @@
 ::: When it's done with checking players it will enable triggers which will show an icon with proper color on the minimap
-After that it will work exactly like in previous part (3.).
+After that, it will work exactly like in the previous part (3.).
 if you did everything properly, then now this entire set of triggers should work like it was explained in the description of this section.
-You can increase the amount of areas but you also need to increase the value of '''b_area_amount_int''' variable if you want to do that.
+You can increase the number of areas but you also need to increase the value of '''b_area_amount_int''' variable if you want to do that.
 Link to the multiplayer mission that contains this set of triggers: