saveMissionProfileNamespace - Revision history

Killzone Kid at 11:29, 18 March 2024

2024-03-18T11:29:33Z

← Older revision		Revision as of 13:29, 18 March 2024
Line 21:		Line 21:
	\|s1= [[saveMissionProfileNamespace]]		\|s1= [[saveMissionProfileNamespace]]

	\|r1= [[Boolean]] - [[true]] in case of success, [[false]] otherwise (e.g trying to save in [[:Category:Eden Editor\|Eden Editor]])		\|r1= [[Boolean]] - [[true]] in case of success, [[false]] otherwise (e.g trying to save in [[:Category:Eden Editor\|Eden Editor]] or trying to save into existing save file but the file wasn't loaded yet)

	\|x1= <sqf>saveMissionProfileNamespace;</sqf>		\|x1= <sqf>saveMissionProfileNamespace;</sqf>

Lou Montana: Fix return value

2024-03-17T19:46:00Z

Fix return value

← Older revision		Revision as of 21:46, 17 March 2024
Line 11:		Line 11:
	\|gr2= Variables		\|gr2= Variables

	\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into {{hl\|''[[missionName]]''.vars}} file into current ~~soldier~~ [[profileName]] folder. Next time when the same mission is loaded by the client with the same ~~soldier~~ profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and ~~soldier~~ profile specific~~. This is default behaviour~~. The file is only created when save operation is invoked with this command.<br><br>		\|descr= [[missionProfileNamespace]] provides long-term storage solution for mission variables.
	It is also possible to share the same mission profile variables between several missions. To override default behaviour ~~one needs to~~ create ~~an entry~~ {{hl\|1= missionGroup}} in [[Description.ext#missionGroup \| Description.ext]], for example ~~{{hl\|1~~= missionGroup = "~~MyMissionCollectionName~~";}}. This will create {{hl\|~~MyMissionCollectionName~~.vars}} file instead of default one, which would be loaded into every mission with matching {{hl\|missionGroup}} entry.		When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into {{hl\|''[[missionName]]''.vars}} file into the current player's [[profileName]] folder.
			Next time when the same mission is loaded by the client with the same player profile, the saved variables can be read normally with [[getVariable]] command.
			This way each mission maker can create persistent data that is both mission and player profile specific. The file is only created when the save operation is invoked with this command.<br><br>
			It is also possible to share the same mission profile variables between several missions.
			To override the default behaviour, create a {{hl\|missionGroup}} entry in [[Description.ext#missionGroup\|Description.ext]], for example <syntaxhighlight lang="cpp" inline>missionGroup = "TAG_MyMissionCollectionName";</syntaxhighlight>.
			This will create {{hl\|TAG_MyMissionCollectionName.vars}} file instead of the default-named one, which would be loaded into every mission with a matching {{hl\|missionGroup}} entry.

	\|s1= [[saveMissionProfileNamespace]]		\|s1= [[saveMissionProfileNamespace]]

	\|r1= [[~~Nothing~~]]		\|r1= [[Boolean]] - [[true]] in case of success, [[false]] otherwise (e.g trying to save in [[:Category:Eden Editor\|Eden Editor]])

	\|x1= <sqf>saveMissionProfileNamespace;</sqf>		\|x1= <sqf>saveMissionProfileNamespace;</sqf>

Killzone Kid at 17:19, 20 December 2023

2023-12-20T17:19:03Z

← Older revision		Revision as of 19:19, 20 December 2023
Line 20:		Line 20:
	\|x1= <sqf>saveMissionProfileNamespace;</sqf>		\|x1= <sqf>saveMissionProfileNamespace;</sqf>

	\|seealso= [[missionProfileNamespace]] [[isMissionProfileNamespaceLoaded]] [[saveProfileNamespace]]		\|seealso= [[missionProfileNamespace]] [[isMissionProfileNamespaceLoaded]] [[saveProfileNamespace]] [[save3DENPreferences]]
	}}		}}

Lou Montana: Text replacement - "\|branch= *dev " to ""

2022-08-23T12:23:40Z

Text replacement - "\|branch= *dev " to ""

← Older revision		Revision as of 14:23, 23 August 2022
Line 4:		Line 4:
	\|version1= 2.10		\|version1= 2.10

	~~\|branch= dev~~

	\|eff= local		\|eff= local

Killzone Kid at 22:00, 9 May 2022

2022-05-09T22:00:42Z

← Older revision		Revision as of 00:00, 10 May 2022
Line 13:		Line 13:

	\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into {{hl\|''[[missionName]]''.vars}} file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.<br><br>		\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into {{hl\|''[[missionName]]''.vars}} file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.<br><br>
	It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry {{hl\|1= missionGroup ~~= "MyMissionCollectionName";~~}} in [[Description.ext#missionGroup \| Description.ext]]. This will create {{hl\|MyMissionCollectionName.vars}} file ~~for example,~~ instead of default one, which would be loaded into every mission with matching {{hl\|missionGroup}} entry.		It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry {{hl\|1= missionGroup}} in [[Description.ext#missionGroup \| Description.ext]], for example {{hl\|1= missionGroup = "MyMissionCollectionName";}}. This will create {{hl\|MyMissionCollectionName.vars}} file instead of default one, which would be loaded into every mission with matching {{hl\|missionGroup}} entry.

	\|s1= [[saveMissionProfileNamespace]]		\|s1= [[saveMissionProfileNamespace]]

Lou Montana: Some wiki formatting

2022-03-20T10:21:42Z

Some wiki formatting

← Older revision		Revision as of 12:21, 20 March 2022
Line 4:		Line 4:
	\|version1= 2.10		\|version1= 2.10

	\|~~arg~~=		\|branch= dev

	\|eff= local		\|eff= local

	\|~~serverExec~~=		\|gr1= Namespaces

	\|~~branch~~= ~~dev~~		\|gr2= Variables

	\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into ~~<tt><~~[[missionName]]>.vars~~</tt>~~ file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.		\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into {{hl\|''[[missionName]]''.vars}} file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.<br><br>
	<br><br>		It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry {{hl\|1= missionGroup = "MyMissionCollectionName";}} in [[Description.ext#missionGroup \| Description.ext]]. This will create {{hl\|MyMissionCollectionName.vars}} file for example, instead of default one, which would be loaded into every mission with matching {{hl\|missionGroup}} entry.
	It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry ~~<tt>~~missionGroup = "MyMissionCollectionName";~~</tt>~~ in ~~the~~ [[Description.ext#missionGroup \| ~~description~~.ext]]. This will create ~~<tt>~~MyMissionCollectionName.vars~~</tt>~~ file for example, instead of default one, which would be loaded into every mission with matching ~~<tt>~~missionGroup~~</tt>~~ entry.

	~~\|gr1= Namespaces~~
	~~\|gr2= Variables~~

	\|s1= [[saveMissionProfileNamespace]]		\|s1= [[saveMissionProfileNamespace]]

Ansin11: Added command group Namespaces

2022-03-18T15:58:49Z

Added command group Namespaces

← Older revision		Revision as of 17:58, 18 March 2022
Line 16:		Line 16:
	It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[Description.ext#missionGroup \| description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry.		It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[Description.ext#missionGroup \| description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry.

	\|gr1= Variables		\|gr1= Namespaces
			\|gr2= Variables

	\|s1= [[saveMissionProfileNamespace]]		\|s1= [[saveMissionProfileNamespace]]

Killzone Kid at 14:00, 18 March 2022

2022-03-18T14:00:18Z

← Older revision		Revision as of 16:00, 18 March 2022
Line 14:		Line 14:
	\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into <tt><[[missionName]]>.vars</tt> file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.		\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into <tt><[[missionName]]>.vars</tt> file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.
	<br><br>		<br><br>
	It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry.		It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[Description.ext#missionGroup \| description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry.

	\|gr1= Variables		\|gr1= Variables

Killzone Kid at 13:57, 18 March 2022

2022-03-18T13:57:28Z

← Older revision		Revision as of 15:57, 18 March 2022
Line 14:		Line 14:
	\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into <tt><[[missionName]]>.vars</tt> file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.		\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into <tt><[[missionName]]>.vars</tt> file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.
	<br><br>		<br><br>
	It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching 'missionGroup' entry.		It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry.

	\|gr1= Variables		\|gr1= Variables

Killzone Kid at 13:48, 18 March 2022

2022-03-18T13:48:39Z

← Older revision		Revision as of 15:48, 18 March 2022
Line 6:		Line 6:
	\|arg=		\|arg=

	\|eff=		\|eff= local

	\|serverExec=		\|serverExec=
Line 12:		Line 12:
	\|branch= dev		\|branch= dev

	\|descr= ~~Description~~		\|descr= [[missionProfileNamespace]] provides long term storage solution for mission variables. When this namespace has variables set with [[setVariable]] and is saved, the variables are saved into <tt><[[missionName]]>.vars</tt> file into current soldier [[profileName]] folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with [[getVariable]] command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.
			<br><br>
			It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching 'missionGroup' entry.

	\|gr1= Variables		\|gr1= Variables