Namespace - Revision history

Lou Montana: Some wiki formatting

2024-08-26T13:59:25Z

Some wiki formatting

← Older revision		Revision as of 15:59, 26 August 2024
Line 2:		Line 2:
	{{GVI\|arma2\|1.00}}		{{GVI\|arma2\|1.00}}

	A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace.		A [[Namespace]] is a container for [[Variables]].
			Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables.
			Scripts and functions are always executed in the context of some namespace.

	The default namespace is the [[missionNamespace]].		The default namespace is the [[missionNamespace]].


	== Namespaces ==		== Namespaces ==

	{\| class="wikitable"		{\| class="wikitable"
	! Game !! Namespace !! Description !! Lifetime		! Game
			! Namespace
			! Description
			! Lifetime
	\|-		\|-
	\| {{GVI\|arma2\|1.00}}		\| {{GVI\|arma2\|1.00}}
Line 32:		Line 39:
	\| {{GVI\|arma3\|2.00}}		\| {{GVI\|arma3\|2.00}}
	\| [[localNamespace]]		\| [[localNamespace]]
	\| This namespace is like the [[missionNamespace]], except that its variables can not be sent over network (e.g. with [[publicVariable]]) or ~~serialized~~.		\| This namespace is like the [[missionNamespace]], except that its variables can not be sent over network (e.g. with [[publicVariable]]) or serialised.
	\| style="background-color: lightgreen" \| Mission duration		\| style="background-color: lightgreen" \| Mission duration
	\|-		\|-
Line 46:		Line 53:
	\|}		\|}

	~~== Namespace Serialization ==~~
	Only the [[missionNamespace]] is serialized, i.e. only the variables from this namespace are saved when the game is saved (e.g. with [[saveGame]]) and loaded when the game is loaded (e.g. with [[loadGame]]). This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]] - UI elements are temporary and therefore exempt from serialization by default.

	== Scripting ~~with Namespaces~~ ==		== Serialisation ==

			Only the [[missionNamespace]] is serialised, as in only the variables from this namespace are saved when the game is saved (e.g. with [[saveGame]]) and loaded when the game is loaded (e.g. with [[loadGame]]).
			This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]] - UI elements are temporary and therefore exempt from serialisation by default.


			== Scripting ==

	Interacting with namespaces is not difficult:		Interacting with namespaces is not difficult:
	* The [[getVariable]] and [[setVariable]] commands can be used to work with variables from different namespaces.		* The [[getVariable]] and [[setVariable]] commands can be used to work with variables from different namespaces.
	* The [[with]]-do-construct can be used to switch the context of an entire code block to another namespace.		* The [[with]]-[[do]] construct can be used to switch the context of an entire code block to another namespace.
	* The [[currentNamespace]] command can be used to obtain the namespace which the calling script is running in.		* The [[currentNamespace]] command can be used to obtain the namespace which the calling script is running in.


	[[Category: Data Types]]		[[Category: Data Types]]
	[[Category: Introduced with Arma 2 version 1.00]]		[[Category: Introduced with Arma 2 version 1.00]]

Ansin11: Small adjustments

2024-01-24T09:27:54Z

Small adjustments

← Older revision		Revision as of 11:27, 24 January 2024
Line 42:		Line 42:
	\| {{GVI\|arma3\|2.10}}		\| {{GVI\|arma3\|2.10}}
	\| [[missionProfileNamespace]]		\| [[missionProfileNamespace]]
	\| This namespace is like [[profileNamespace]] but is also attached to a [[missionName]] or [[Description.ext#missionGroup \| missionGroup]]. Automatically loaded before 'init.sqf'.		\| This namespace is like [[profileNamespace]] but is also attached to a [[missionName]] or [[Description.ext#missionGroup\|missionGroup]]. Automatically loaded before [[Event Scripts#init.sqf\|init.sqf]].
	\| style="background-color: lightskyblue" \| [[Profile]] lifetime		\| style="background-color: lightskyblue" \| [[Profile]] lifetime
	\|}		\|}

Killzone Kid at 19:14, 2 April 2022

2022-04-02T19:14:09Z

← Older revision		Revision as of 21:14, 2 April 2022
Line 32:		Line 32:
	\| {{GVI\|arma3\|2.00}}		\| {{GVI\|arma3\|2.00}}
	\| [[localNamespace]]		\| [[localNamespace]]
	\| This namespace is like the [[missionNamespace]], except that its variables can not be ~~broadcasted~~ (e.g. with [[publicVariable]]) or serialized.		\| This namespace is like the [[missionNamespace]], except that its variables can not be sent over network (e.g. with [[publicVariable]]) or serialized.
	\| style="background-color: lightgreen" \| Mission duration		\| style="background-color: lightgreen" \| Mission duration
	\|-		\|-

Killzone Kid: /* Namespaces */

2022-03-23T08:34:39Z

Namespaces

← Older revision		Revision as of 10:34, 23 March 2022
Line 42:		Line 42:
	\| {{GVI\|arma3\|2.10}}		\| {{GVI\|arma3\|2.10}}
	\| [[missionProfileNamespace]]		\| [[missionProfileNamespace]]
	\| This namespace is like [[profileNamespace]] but is also attached to a [[missionName]] or 'missionGroup'. Automatically loaded before 'init.sqf'.		\| This namespace is like [[profileNamespace]] but is also attached to a [[missionName]] or [[Description.ext#missionGroup \| missionGroup]]. Automatically loaded before 'init.sqf'.
	\| style="background-color: lightskyblue" \| [[Profile]] lifetime		\| style="background-color: lightskyblue" \| [[Profile]] lifetime
	\|}		\|}

Killzone Kid: /* Namespaces */

2022-03-18T12:39:31Z

Namespaces

← Older revision		Revision as of 14:39, 18 March 2022
Line 39:		Line 39:
	\| The namespace used by [[ArmA: Armed Assault: Server Side Scripting\|Server Event Handlers]]. This namespace is only available on servers.		\| The namespace used by [[ArmA: Armed Assault: Server Side Scripting\|Server Event Handlers]]. This namespace is only available on servers.
	\| style="background-color: lightyellow" \| Game session		\| style="background-color: lightyellow" \| Game session
			\|-
			\| {{GVI\|arma3\|2.10}}
			\| [[missionProfileNamespace]]
			\| This namespace is like [[profileNamespace]] but is also attached to a [[missionName]] or 'missionGroup'. Automatically loaded before 'init.sqf'.
			\| style="background-color: lightskyblue" \| [[Profile]] lifetime
	\|}		\|}

R3vo: fixed typo and removed some empty lines

2022-02-26T16:45:49Z

fixed typo and removed some empty lines

← Older revision		Revision as of 18:45, 26 February 2022
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{GVI\|arma2\|1.00}}		{{GVI\|arma2\|1.00}}


	A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace.		A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace.

	The default namespace is the [[missionNamespace]].		The default namespace is the [[missionNamespace]].


	== Namespaces ==		== Namespaces ==
Line 34:		Line 32:
	\| {{GVI\|arma3\|2.00}}		\| {{GVI\|arma3\|2.00}}
	\| [[localNamespace]]		\| [[localNamespace]]
	\| This namespace is like the [[missionNamespace]], except that its variables can not be ~~broadcast~~ (e.g. with [[publicVariable]]) or serialized.		\| This namespace is like the [[missionNamespace]], except that its variables can not be broadcasted (e.g. with [[publicVariable]]) or serialized.
	\| style="background-color: lightgreen" \| Mission duration		\| style="background-color: lightgreen" \| Mission duration
	\|-		\|-
Line 42:		Line 40:
	\| style="background-color: lightyellow" \| Game session		\| style="background-color: lightyellow" \| Game session
	\|}		\|}


	== Namespace Serialization ==		== Namespace Serialization ==
	Only the [[missionNamespace]] is serialized, i.e. only the variables from this namespace are saved when the game is saved (e.g. with [[saveGame]]) and loaded when the game is loaded (e.g. with [[loadGame]]). This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]] - UI elements are temporary and therefore exempt from serialization by default.		Only the [[missionNamespace]] is serialized, i.e. only the variables from this namespace are saved when the game is saved (e.g. with [[saveGame]]) and loaded when the game is loaded (e.g. with [[loadGame]]). This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]] - UI elements are temporary and therefore exempt from serialization by default.


	== Scripting with Namespaces ==		== Scripting with Namespaces ==
Line 53:		Line 49:
	* The [[with]]-do-construct can be used to switch the context of an entire code block to another namespace.		* The [[with]]-do-construct can be used to switch the context of an entire code block to another namespace.
	* The [[currentNamespace]] command can be used to obtain the namespace which the calling script is running in.		* The [[currentNamespace]] command can be used to obtain the namespace which the calling script is running in.


	[[Category: Data Types]]		[[Category: Data Types]]
	[[Category: Introduced with Arma 2 version 1.00]]		[[Category: Introduced with Arma 2 version 1.00]]

Ansin11: Finished overhaul

2022-02-26T15:02:47Z

Finished overhaul

← Older revision		Revision as of 17:02, 26 February 2022
Line 3:		Line 3:


	A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace. The default namespace is the [[missionNamespace]].		A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace.

			The default namespace is the [[missionNamespace]].


	== Namespaces ==		== Namespaces ==

	~~The following commands return the [[Namespace]] type:~~

	{\| class="wikitable"		{\| class="wikitable"
	! Game !! ~~Command~~ !! Description		! Game !! Namespace !! Description !! Lifetime
	\|-
	~~\| {{GVI\|arma2\|1.00}} \|\| [[missionNamespace]] \|\| returns the global namespace attached to the mission~~
	\|-		\|-
	\| {{GVI\|arma2\|1.00}} \|\| [[~~parsingNamespace~~]] \|~~\| returns the~~ global namespace ~~attached to~~ the [[~~PreProcessor Commands\|Config Parser~~]]		\| {{GVI\|arma2\|1.00}}
			\| [[missionNamespace]]
			\| The global namespace of the mission. Every mission has its own [[missionNamespace]].
			\| style="background-color: lightgreen" \| Mission duration
	\|-		\|-
	\| {{GVI\|arma2\|1.00}} \|\| [[~~uiNamespace~~]] \|~~\| returns the~~ global namespace attached to the ~~user interface~~		\| {{GVI\|arma2\|1.00}}
			\| [[parsingNamespace]]
			\| The global namespace attached to the [[PreProcessor Commands\|Config Parser]].
			\| style="background-color: lightyellow" \| Game session
	\|-		\|-
	\| {{GVI\|~~tkoh~~\|1.00}} \|\| [[~~profileNamespace~~]] \|~~\| returns the~~ global namespace attached to the user ~~profile~~		\| {{GVI\|arma2\|1.00}}
			\| [[uiNamespace]]
			\| The global namespace attached to the user interface.
			\| style="background-color: lightyellow" \| Game session
	\|-		\|-
	\| {{GVI\|~~arma3~~\|1.48}} \|\| [[~~currentNamespace~~]] \|~~\| returns the~~ namespace ~~which~~ the ~~calling script is running in~~		\| {{GVI\|tkoh\|1.00}}
			\| [[profileNamespace]]
			\| The global namespace attached to the user profile.
			\| style="background-color: lightskyblue" \| [[Profile]] lifetime
	\|-		\|-
	\| {{GVI\|arma3\|2.00}} \|\| [[~~localNamespace~~]] \|\| ~~returns the local namespace~~		\| {{GVI\|arma3\|2.00}}
			\| [[localNamespace]]
			\| This namespace is like the [[missionNamespace]], except that its variables can not be broadcast (e.g. with [[publicVariable]]) or serialized.
			\| style="background-color: lightgreen" \| Mission duration
	\|-		\|-
	\| {{GVI\|arma3\|2.06}} \|\| [[serverNamespace]] \|\| ~~returns the server~~ namespace		\| {{GVI\|arma3\|2.06}}
			\| [[serverNamespace]]
			\| The namespace used by [[ArmA: Armed Assault: Server Side Scripting\|Server Event Handlers]]. This namespace is only available on servers.
			\| style="background-color: lightyellow" \| Game session
	\|}		\|}


	== ~~Get namespace data~~ == ~~<!-- Remove? -->~~		== Namespace Serialization ==
			Only the [[missionNamespace]] is serialized, i.e. only the variables from this namespace are saved when the game is saved (e.g. with [[saveGame]]) and loaded when the game is loaded (e.g. with [[loadGame]]). This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]] - UI elements are temporary and therefore exempt from serialization by default.
	~~You can use~~ the ~~above~~ with [[~~getVariable~~]] ~~to get data~~.


	~~== Set namespace data == <!-- Remove? -->~~

	~~To set data to a namespace, there're two methods to do:~~
	~~<code>'''namespace'''~~ [[~~setVariable~~]] [~~"variableName", ''value''~~]~~;</code>~~

	~~<code>~~[[~~with~~]] ~~'''namespace''' do {~~
	~~variableName = ''value'';~~
	~~};</code>~~

	~~[[missionNamespace]] is the default global namespace, so just {{ic\|VariableName {{=}} ''value'';}} will store data to [[missionNamespace]].~~


	~~== Namespace Lifetimes == <!-- TODO: Transform to a table -->~~

	~~=== missionNamespace ===~~

	The missionNamespace is the main default partition that exists for the duration of a mission. All variables defined in the missionNamespace will cease to exist when the mission ends. To make variables last longer than a mission, use different namespaces.

	~~=== uiNamespace and parsingNamespace ===~~

	~~These are two different namespaces which have similar scope. Variables defined in these namespaces exist for the duration of the game executable running and are lost when the game is shut down.~~

	~~=== profileNamespace ===~~

	This namespace holds variables for a very long time and is attached to the user profile. Different profiles will have own set of variables stored with them. The saving of the profileNamespace can be forced with the [[saveProfileNamespace]] command, but in {{arma3}} this command is executed by vanilla game scripts already, so saving is done automatically.

	~~=== localNamespace ===~~

	~~Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.~~


	~~== Namespace Serialization ==~~

	~~Only the~~ [[~~missionNamespace~~]] ~~is serialized. This means that all variables in this namespace will be saved when the game is saved~~ and ~~loaded when the game is loaded. This is also the reason the game will complain that one should use~~ [[~~disableSerialization~~]] ~~when storing UI~~ variables in [[~~missionNamespace~~]]. ~~UI elements are temporary and therefore exempt from serialization by default~~.		== Scripting with Namespaces ==
			Interacting with namespaces is not difficult:
			* The [[getVariable]] and [[setVariable]] commands can be used to work with variables from different namespaces.
			* The [[with]]-do-construct can be used to switch the context of an entire code block to another namespace.
			* The [[currentNamespace]] command can be used to obtain the namespace which the calling script is running in.


	[[Category: Data Types]]		[[Category: Data Types]]
	[[Category: Introduced with Arma 2 version 1.00]]		[[Category: Introduced with Arma 2 version 1.00]]

Ansin11: Added serverNamespace, overhauled a little bit

2022-02-25T11:23:47Z

Added serverNamespace, overhauled a little bit

← Older revision		Revision as of 13:23, 25 February 2022
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{~~Feature~~\|~~quote~~\|~~a namespace is a set of symbols that are used to organize objects of various kinds, so that these objects may be referred to by name~~. ~~A namespace ensures that all the identifiers within it have unique names so that they can be easily identified.\|Wikipedia\|https://en.wikipedia.org/wiki/Namespace~~}}		{{GVI\|arma2\|1.00}}

	~~Namespace - set of variables. Introduced with {{GVI\|arma2\|1.00}}.~~

			A [[Namespace]] is a container for [[Variables]]. Any [[Variables#Scopes\|global]] variable is always part of exactly one namespace - another namespace may contain a variable with the same [[Identifier]], but they remain two distinct independent variables. Scripts and functions are always executed in the context of some namespace. The default namespace is the [[missionNamespace]].

	~~== Get namespace ==~~

	~~These~~ commands return the "Namespace" type:		== Namespaces ==

			The following commands return the [[Namespace]] type:

	{\| class="wikitable"		{\| class="wikitable"
	! Game !! Command !! Description		! Game !! Command !! Description
Line 19:		Line 21:
	\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile		\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile
	\|-		\|-
	\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the ~~current~~ namespace~~. Can be compared with [[isEqualTo]] or [[==]] and [[!=]] (since Arma 3 v2.00).~~		\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the namespace which the calling script is running in
	\|-		\|-
	\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace.		\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace
			\|-
			\| {{GVI\|arma3\|2.06}} \|\| [[serverNamespace]] \|\| returns the server namespace
	\|}		\|}

	~~You can save values in this different Namespaces without overwriting the variables with the same name.~~

			== Get namespace data == <!-- Remove? -->
	== Get namespace data ==

	You can use the above with [[getVariable]] to get data.		You can use the above with [[getVariable]] to get data.


	== Set namespace data ==		== Set namespace data == <!-- Remove? -->

	To set data to a namespace, there're two methods to do:		To set data to a namespace, there're two methods to do:
Line 41:		Line 43:
	};</code>		};</code>

	[[missionNamespace]] is the default global namespace, so just ~~"variableName~~ = ''value'';" will store data to [[missionNamespace]].		[[missionNamespace]] is the default global namespace, so just {{ic\|VariableName {{=}} ''value'';}} will store data to [[missionNamespace]].


	== Namespace Lifetimes ==		== Namespace Lifetimes == <!-- TODO: Transform to a table -->

	=== missionNamespace ===		=== missionNamespace ===

	~~Mission namespace~~ is the main default partition that exists for the duration of a mission. All variables defined in ~~mission namespace~~ will cease to exist when mission ends. To make variables ~~lasting~~ longer than a mission, use different namespaces.		The missionNamespace is the main default partition that exists for the duration of a mission. All variables defined in the missionNamespace will cease to exist when the mission ends. To make variables last longer than a mission, use different namespaces.

	=== uiNamespace and parsingNamespace ===		=== uiNamespace and parsingNamespace ===

	These are 2 different namespaces, which have similar scope. Variables defined in these namespaces exist for the duration of the game ~~.exe~~ running and are lost when the game is shut down.		These are two different namespaces which have similar scope. Variables defined in these namespaces exist for the duration of the game executable running and are lost when the game is shut down.

	=== profileNamespace ===		=== profileNamespace ===

	This namespace ~~will hold~~ variables for a very long time and is attached to the user profile. Different profiles will have own set of variables stored with them. The saving of the ~~profile namespace is~~ forced with [[saveProfileNamespace]] command, but in ~~Arma 3~~ this command is executed by vanilla game scripts already, so saving is done automatically.		This namespace holds variables for a very long time and is attached to the user profile. Different profiles will have own set of variables stored with them. The saving of the profileNamespace can be forced with the [[saveProfileNamespace]] command, but in {{arma3}} this command is executed by vanilla game scripts already, so saving is done automatically.

	=== localNamespace ===		=== localNamespace ===

	~~Available since Arma 3 v2.00.~~ Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.		Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.


	== Namespace ~~serialization~~ ==		== Namespace Serialization ==

	Only [[missionNamespace]] is serialized. This means that all variables in this namespace will be saved when the game is saved and loaded when the game is loaded. This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]]. UI elements are temporary and therefore ~~are~~ exempt from serialization by default.		Only the [[missionNamespace]] is serialized. This means that all variables in this namespace will be saved when the game is saved and loaded when the game is loaded. This is also the reason the game will complain that one should use [[disableSerialization]] when storing UI variables in [[missionNamespace]]. UI elements are temporary and therefore exempt from serialization by default.


	[[Category: Data Types]]		[[Category: Data Types]]
	[[Category: Introduced with Arma 2 version 1.00]]		[[Category: Introduced with Arma 2 version 1.00]]

R3vo: Text replacement - "v1\.[9-9]{2}\.[0-9]{6}" to "v2.00"

2021-04-03T09:04:50Z

Text replacement - "v1\.[9-9]{2}\.[0-9]{6}" to "v2.00"

← Older revision		Revision as of 11:04, 3 April 2021
Line 19:		Line 19:
	\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile		\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile
	\|-		\|-
	\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the current namespace. Can be compared with [[isEqualTo]] or [[==]] and [[!=]] (since Arma 3 v1.~~99.146509~~).		\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the current namespace. Can be compared with [[isEqualTo]] or [[==]] and [[!=]] (since Arma 3 v2.00).
	\|-		\|-
	\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace.		\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace.
Line 60:		Line 60:
	=== localNamespace ===		=== localNamespace ===

	Available since Arma 3 v1.~~99.146509~~. Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.		Available since Arma 3 v2.00. Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.

	== Namespace serialization ==		== Namespace serialization ==

R3vo: Reverted edits by R3vo (talk) to last revision by Lou Montana

2021-04-03T08:19:33Z

Reverted edits by R3vo (talk) to last revision by Lou Montana

← Older revision		Revision as of 10:19, 3 April 2021
Line 19:		Line 19:
	\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile		\| {{GVI\|tkoh\|1.00}} \|\| [[profileNamespace]] \|\| returns the global namespace attached to the user profile
	\|-		\|-
	\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the current namespace. Can be compared with [[isEqualTo]] or [[==]] and [[!=]] (since Arma 3 v2.~~00146509~~).		\| {{GVI\|arma3\|1.48}} \|\| [[currentNamespace]] \|\| returns the current namespace. Can be compared with [[isEqualTo]] or [[==]] and [[!=]] (since Arma 3 v1.99.146509).
	\|-		\|-
	\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace.		\| {{GVI\|arma3\|2.00}} \|\| [[localNamespace]] \|\| returns the local namespace.
Line 60:		Line 60:
	=== localNamespace ===		=== localNamespace ===

	Available since Arma 3 v2.~~00146509~~. Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.		Available since Arma 3 v1.99.146509. Same lifetime as [[missionNamespace]] but variables cannot be broadcast or serialized.

	== Namespace serialization ==		== Namespace serialization ==