Arma 3: Mission Parameters - Revision history

Lou Montana: Fix category

2022-06-24T21:21:59Z

Fix category

← Older revision		Revision as of 23:21, 24 June 2022
Line 1:		Line 1:
	#~~redirect~~ [[Mission Parameters]]		#REDIRECT [[Mission Parameters]]

	~~[[Category:Mission Editing~~]]

R3vo: redirected to Mission Parameters

2021-02-04T13:32:57Z

redirected to Mission Parameters

Show changes

R3vo: category

2021-02-01T13:19:24Z

R3vo: merge request

2021-01-29T16:48:10Z

merge request

← Older revision		Revision as of 18:48, 29 January 2021
Line 2:		Line 2:

	Important limitation. In an MP environment, the Paramsarray is not available on the client until some time after preinit. but before postinit so any code called upon the client should take this into consideration		Important limitation. In an MP environment, the Paramsarray is not available on the client until some time after preinit. but before postinit so any code called upon the client should take this into consideration
			{{Merge\|Mission Parameters}}

	== Manual Params ==		== Manual Params ==

Lou Montana: Text replacement - "\[\[[Cc]ategory:[ _]?Arma[ _]3:[ _]([^|])[ _]?\|.\]\]" to "{{GameCategory|arma3|$1}}"

2021-01-05T09:34:12Z

Text replacement - "\[\[[Cc]ategory:[ _]?Arma[ _]3:[ _]([^|]*)[ _]?\|.*\]\]" to "{{GameCategory|arma3|$1}}"

← Older revision		Revision as of 11:34, 5 January 2021
Line 201:		Line 201:


	~~[[Category:Arma 3:~~ Editing~~\|Mission Parameters]]~~		{{GameCategory\|arma3\|Editing}}

Lou Montana: Text replacement - "\{\{ ?warning" to "{{Warning"

2021-01-05T00:38:30Z

Text replacement - "\{\{ ?warning" to "{{Warning"

← Older revision		Revision as of 02:38, 5 January 2021
Line 68:		Line 68:

	Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].		Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].
	{{~~warning~~ \| Make sure that include path to a3 mod has leading backslash:		{{Warning \| Make sure that include path to a3 mod has leading backslash:
	<code>#include "a3\functions_f\Params\paramCountdown.hpp" // bad</code>		<code>#include "a3\functions_f\Params\paramCountdown.hpp" // bad</code>
	<code>#include "\a3\functions_f\Params\paramCountdown.hpp" // good</code>		<code>#include "\a3\functions_f\Params\paramCountdown.hpp" // good</code>

Lou Montana: Lou Montana moved page Arma 3 Mission Parameters to Arma 3: Mission Parameters: Text replacement - "^Arma 3 " to "Arma 3: "

2020-12-29T23:55:42Z

Lou Montana moved page Arma 3 Mission Parameters to Arma 3: Mission Parameters: Text replacement - "^Arma 3 " to "Arma 3: "

← Older revision	Revision as of 01:55, 30 December 2020
(No difference)

Lou Montana: Some wiki formatting

2020-08-23T18:19:57Z

Some wiki formatting

← Older revision		Revision as of 20:19, 23 August 2020
Line 1:		Line 1:
	~~[[Category:Arma 3: Editing\|Mission Parameters]]~~

	Server admin / host can customize multiplayer missions in ROLE ASSIGNMENT menu using parameters prepared by the mission designer.		Server admin / host can customize multiplayer missions in ROLE ASSIGNMENT menu using parameters prepared by the mission designer.

	Important limitation. In an MP environment, the Paramsarray is not available on the client until some time after preinit. but before postinit so any code called upon the client should take this into consideration		Important limitation. In an MP environment, the Paramsarray is not available on the client until some time after preinit. but before postinit so any code called upon the client should take this into consideration


	== Manual Params ==		== Manual Params ==

	=== Config ===		=== Config ===

	[[File:Arma3 Mission Parameters.png\|thumb\|Mission Parameters selection]]		[[File:Arma3 Mission Parameters.png\|thumb\|Mission Parameters selection]]
	Params are defined in [[~~description~~.ext]].		Params are defined in [[Description.ext]].
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	class Params		class Params
Line 35:		Line 36:
	// When 'texts' are missing, values will be displayed directly instead		// When 'texts' are missing, values will be displayed directly instead
	default = 1000;		default = 1000;
	file = "setViewDistance.sqf"; // (Optional) Script ~~[[call]]ed~~ when player joins, selected value is passed as an argument		file = "setViewDistance.sqf"; // (Optional) Script called when player joins, selected value is passed as an argument
	};		};
	};		};
Line 57:		Line 58:

	=== Functions ===		=== Functions ===

	<u>It is highly recommended</u> that you use [[BIS_fnc_getParamValue]] instead of paramsArray to get value of a param with given class name. It is fast and secure and globally available on any connected PC as well as JIP.		<u>It is highly recommended</u> that you use [[BIS_fnc_getParamValue]] instead of paramsArray to get value of a param with given class name. It is fast and secure and globally available on any connected PC as well as JIP.

	<code>_viewDistance = "ViewDistance" [[call]] [[BIS_fnc_getParamValue]];		<code>_viewDistance = "ViewDistance" [[call]] [[BIS_fnc_getParamValue]];
	_viewDistance = ["ViewDistance", 500] [[call]] [[BIS_fnc_getParamValue]];</code>		_viewDistance = ["ViewDistance", 500] [[call]] [[BIS_fnc_getParamValue]];</code>


	== Predefined Params ==		== Predefined Params ==

	Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].		Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].
	{{warning \| Make sure that include path to a3 mod has leading backslash:		{{warning \| Make sure that include path to a3 mod has leading backslash:
Line 68:		Line 72:
	<code>#include "\a3\functions_f\Params\paramCountdown.hpp" // good</code>		<code>#include "\a3\functions_f\Params\paramCountdown.hpp" // good</code>
	}}		}}
	<syntaxhighlight lang=cpp>		<syntaxhighlight lang="cpp">

	class Params		class Params
Line 131:		Line 135:
	\| Set starting hour, options are represented by whole hours		\| Set starting hour, options are represented by whole hours
	\|		\|
	{{~~codecomment~~\| //Can be any integer between 0 and 23}}		{{cc\|Can be any integer between 0 and 23}}
	#define DAYTIMEHOUR_DEFAULT 19		#define DAYTIMEHOUR_DEFAULT 19

Line 138:		Line 142:
	\| Set starting hour, options are described by words		\| Set starting hour, options are described by words
	\|		\|
	{{~~codecomment~~\| //Can be 0, 6, 12 or 18}}		{{cc\|Can be 0, 6, 12 or 18}}
	#define DAYTIMEPERIOD_DEFAULT 12		#define DAYTIMEPERIOD_DEFAULT 12

Line 145:		Line 149:
	\| Allow [[Mission_Editor:_Debug_Console_(Arma_3)\|debug console]] for server host or logged in admin		\| Allow [[Mission_Editor:_Debug_Console_(Arma_3)\|debug console]] for server host or logged in admin
	\|		\|
	{{~~codecomment~~\| //0 (disabled) or 1 (enabled)}}		{{cc\|0 (disabled) or 1 (enabled)}}
	#define DEBUGCONSOLE_DEFAULT 1		#define DEBUGCONSOLE_DEFAULT 1

Line 152:		Line 156:
	\| Set to whom will [[independent]] side be friendly		\| Set to whom will [[independent]] side be friendly
	\|		\|
	{{~~codecomment~~\| //Can be any -1 (Nobody}, 0 (OPFOR), 1 (BLUFOR) or 2 (Everybody)}}		{{cc\|Can be any -1 (Nobody}, 0 (OPFOR), 1 (BLUFOR) or 2 (Everybody)}}
	#define GUERFRIENDLY_DEFAULT -1		#define GUERFRIENDLY_DEFAULT -1

Line 159:		Line 163:
	\| Set respawn tickets for all sides<br>The "NoDisabled" version has no "disabled" option, and will pick the middle option by default.		\| Set respawn tickets for all sides<br>The "NoDisabled" version has no "disabled" option, and will pick the middle option by default.
	\|		\|
	#define TICKETS_MIN 100		#define TICKETS_MIN 100
	#define TICKETS_MAX 1100		#define TICKETS_MAX 1100
	#define TICKETS_DEFAULT -1		#define TICKETS_DEFAULT -1

Line 167:		Line 171:
	\| Set default weather		\| Set default weather
	\|		\|
	{{~~codecomment~~\| //Can be 0 (sunny), 25, 50, 75 or 100 (storm))}}		{{cc\|Can be 0 (sunny), 25, 50, 75 or 100 (storm))}}
	#define WEATHER_DEFAULT 75		#define WEATHER_DEFAULT 75

Line 174:		Line 178:
	\| Sets a time multiplier for in-game time. See [[setTimeMultiplier\|setTimeMultiplier]]		\| Sets a time multiplier for in-game time. See [[setTimeMultiplier\|setTimeMultiplier]]
	\|		\|
	{{~~codecomment~~\| //Can be x1, x2, x5, x10 or x20}}		{{cc\|Can be x1, x2, x5, x10 or x20}}
	#define TIMEACCELERATION_DEFAULT 10		#define TIMEACCELERATION_DEFAULT 10

Line 181:		Line 185:
	\| Set rendering distance, in meters. See [[setViewDistance\|setViewDistance]]		\| Set rendering distance, in meters. See [[setViewDistance\|setViewDistance]]
	\|		\|
	#define VIEW_DISTANCE_MIN 1500		#define VIEW_DISTANCE_MIN 1500
	#define VIEW_DISTANCE_MAX 4000		#define VIEW_DISTANCE_MAX 4000
	#define VIEW_DISTANCE_DEFAULT 2000		#define VIEW_DISTANCE_DEFAULT 2000
	\|-		\|-
Line 189:		Line 193:
	\|		\|
	\|}		\|}


	== See Also ==		== See Also ==

	* [[Mission Parameters]]		* [[Mission Parameters]]
	* [[Description.ext#Mission_parameters\|Description.ext]]		* [[Description.ext#Mission_parameters\|Description.ext]]


			[[Category:Arma 3: Editing\|Mission Parameters]]

Lou Montana: Remove dupe

2020-07-02T10:01:21Z

Remove dupe

← Older revision		Revision as of 12:01, 2 July 2020
Line 9:		Line 9:
	[[File:Arma3 Mission Parameters.png\|thumb\|Mission Parameters selection]]		[[File:Arma3 Mission Parameters.png\|thumb\|Mission Parameters selection]]
	Params are defined in [[description.ext]].		Params are defined in [[description.ext]].
	<syntaxhighlight lang=cpp>		<syntaxhighlight lang="cpp">
	class Params		class Params
	{		{
Line 188:		Line 188:
	\| Set various revive related options [[Arma 3 Revive]]		\| Set various revive related options [[Arma 3 Revive]]
	\|		\|
	\|-
	~~\| <code>"\a3\Functions_F_Heli\Params\paramViewDistance.hpp"</code>~~
	~~\| Change view distances~~
	\|
	~~#define VIEW_DISTANCE_MIN 1500~~
	~~#define VIEW_DISTANCE_MAX 4000~~
	~~#define VIEW_DISTANCE_DEFAULT 2000~~
	\|}		\|}

Killzone Kid: /* Predefined Params */

2020-03-31T10:06:34Z

Predefined Params

← Older revision		Revision as of 12:06, 31 March 2020
Line 64:		Line 64:
	== Predefined Params ==		== Predefined Params ==
	Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].		Arma 3 introduces a framework for defining commonly used params (e.g., time of the day or mission duration), which can be shared across multiple missions. Once included to description.ext, they will initialize automatically. Some of them can be further customized using specific [[PreProcessor_Commands\|macros]].
			{{warning \| Make sure that include path to a3 mod has leading backslash:
			<code>#include "a3\functions_f\Params\paramCountdown.hpp" // bad</code>
			<code>#include "\a3\functions_f\Params\paramCountdown.hpp" // good</code>
			}}
	<syntaxhighlight lang=cpp>		<syntaxhighlight lang=cpp>

	class Params		class Params
	{		{

← Older revision		Revision as of 15:19, 1 February 2021
Line 201:		Line 201:


	~~{{GameCategory\|arma3\|~~Editing}}		[[Category:Mission Editing]]