Arma 3: Time Trials - Revision history

Lou Montana: Text replacement - "↵\{\{ConfigPage\| [a-zA-Z]+ \}\}" to ""

2025-04-12T22:20:50Z

Text replacement - "↵\{\{ConfigPage\| *[a-zA-Z]+ *\}\}" to ""

← Older revision		Revision as of 00:20, 13 April 2025
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	~~{{ConfigPage\|abc}}~~

	This guide describes how to design and implement a custom Time Trial Challenge (similar to those available in the vanilla game).		This guide describes how to design and implement a custom Time Trial Challenge (similar to those available in the vanilla game).

Lou Montana: Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

2024-02-01T23:25:41Z

Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

← Older revision		Revision as of 01:25, 2 February 2024
Line 77:		Line 77:
	* Alternatively, 3D helpers can be used as CP objects (circles are commonly used for aerial trials).		* Alternatively, 3D helpers can be used as CP objects (circles are commonly used for aerial trials).

	{{Feature\|~~Informative~~\|<var>BIS_TT_Vehicle</var> needs to start inside <var>BIS_TT_CP1</var> in order for the time trial to work properly.}}		{{Feature\|informative\|<var>BIS_TT_Vehicle</var> needs to start inside <var>BIS_TT_CP1</var> in order for the time trial to work properly.}}
	</li>		</li>
	<li>Set up trial properties via [[Description.ext\|description.ext]] (see {{Link\|#Configuration}}).</li>		<li>Set up trial properties via [[Description.ext\|description.ext]] (see {{Link\|#Configuration}}).</li>
Line 127:		Line 127:
	</syntaxhighlight>		</syntaxhighlight>

	{{Feature\|~~Informative~~\|Not all properties in this sample config are needed for every trial; they are included to showcase all options.}}		{{Feature\|informative\|Not all properties in this sample config are needed for every trial; they are included to showcase all options.}}
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	// This primary trial configuration can also be implemented via a mod config, but doing so via description.ext is simplest in most cases.}}		// This primary trial configuration can also be implemented via a mod config, but doing so via description.ext is simplest in most cases.}}
Line 233:		Line 233:
	== CfgMissions ==		== CfgMissions ==

	{{Feature\|~~Informative~~\|This is only needed for trials configured via mod config (not via description.ext).}}		{{Feature\|informative\|This is only needed for trials configured via mod config (not via description.ext).}}
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	class CfgMissions		class CfgMissions
Line 314:		Line 314:
	= Run-Time Tools =		= Run-Time Tools =

	{{Feature\|~~Informative~~\|Some things are exposed and possible to change or use run-time, f.e. to make special unlocks or events happen.}}		{{Feature\|informative\|Some things are exposed and possible to change or use run-time, f.e. to make special unlocks or events happen.}}
	* ''BIS_TT_hasReset'': code which returns true when the trial has reset, ended, or is ending		* ''BIS_TT_hasReset'': code which returns true when the trial has reset, ended, or is ending
	* ''BIS_TT_phase'': 0 - trial pre-init / 1 - trial pre-start / 2 - trial started / 3 - trial terminated / -1 - trial restarting		* ''BIS_TT_phase'': 0 - trial pre-init / 1 - trial pre-start / 2 - trial started / 3 - trial terminated / -1 - trial restarting

Lou Montana: Text replacement - "[[3DEN|" to "[[:Category:Eden Editor|"

2023-07-09T12:29:39Z

Text replacement - "[[3DEN|" to "[[:Category:Eden Editor|"

← Older revision		Revision as of 14:29, 9 July 2023
Line 25:		Line 25:
	= Setup =		= Setup =
	<ol>		<ol>
	<li>Open the [[~~3DEN~~\|Eden Editor]] with the terrain of your choice loaded.</li>		<li>Open the [[:Category:Eden Editor\|Eden Editor]] with the terrain of your choice loaded.</li>
	<li>Place a player character named <var>BIS_TT_Competitor</var> (this is a fixed system name).</li>		<li>Place a player character named <var>BIS_TT_Competitor</var> (this is a fixed system name).</li>
	<li>Save the scenario with a name that is safe to reference as a config class (i.e. no spaces) - for example ''MyFirstTimeTrial''.		<li>Save the scenario with a name that is safe to reference as a config class (i.e. no spaces) - for example ''MyFirstTimeTrial''.

Lou Montana: Text replacement - "{{HashLink" to "{{Link"

2023-01-04T16:43:46Z

Text replacement - "{{HashLink" to "{{Link"

← Older revision		Revision as of 18:43, 4 January 2023
Line 57:		Line 57:
	# Reopen the scenario in the Eden Editor.		# Reopen the scenario in the Eden Editor.
	# Position the target near the finish CP (so that it is visible and accessible to drive to after finishing).		# Position the target near the finish CP (so that it is visible and accessible to drive to after finishing).
	# Enter the following in the target's ''Texture #0'' field: {{hl\|A3\modules_f_beta\data\FiringDrills\restart_orange_ca}} (other colors have corresponding textures - see {{~~HashLink~~\|#Colors}}).		# Enter the following in the target's ''Texture #0'' field: {{hl\|A3\modules_f_beta\data\FiringDrills\restart_orange_ca}} (other colors have corresponding textures - see {{Link\|#Colors}}).
	</li>		</li>
	<li>Place a trigger with default properties named <var>BIS_TT_restartSelector1</var> (this will be referenced later).		<li>Place a trigger with default properties named <var>BIS_TT_restartSelector1</var> (this will be referenced later).
Line 79:		Line 79:
	{{Feature\|Informative\|<var>BIS_TT_Vehicle</var> needs to start inside <var>BIS_TT_CP1</var> in order for the time trial to work properly.}}		{{Feature\|Informative\|<var>BIS_TT_Vehicle</var> needs to start inside <var>BIS_TT_CP1</var> in order for the time trial to work properly.}}
	</li>		</li>
	<li>Set up trial properties via [[Description.ext\|description.ext]] (see {{~~HashLink~~\|#Configuration}}).</li>		<li>Set up trial properties via [[Description.ext\|description.ext]] (see {{Link\|#Configuration}}).</li>
	<li>Configure the trial via [[Description.ext\|description.ext]] or via CfgTimeTrials and CfgMissions (see {{~~HashLink~~\|#Configuration}}).</li>		<li>Configure the trial via [[Description.ext\|description.ext]] or via CfgTimeTrials and CfgMissions (see {{Link\|#Configuration}}).</li>
	</ol>		</ol>

Lou Montana: Text replacement - "{{ExternalLink|" to "{{Link|"

2023-01-04T15:23:08Z

Text replacement - "{{ExternalLink|" to "{{Link|"

← Older revision		Revision as of 17:23, 4 January 2023
Line 303:		Line 303:
	= Steam Workshop =		= Steam Workshop =

	When a trial is self-contained (i.e. configured via [[Description.ext\|description.ext]]), it can be published to {{~~ExternalLink~~\|link= https://steamcommunity.com/workshop/browse/?appid=107410\|text= Steam Workshop}} as ''Scenario''. When players subscribe to such trial, it will be listed in their ''CHALLENGES'' menu.		When a trial is self-contained (i.e. configured via [[Description.ext\|description.ext]]), it can be published to {{Link\|link= https://steamcommunity.com/workshop/browse/?appid=107410\|text= Steam Workshop}} as ''Scenario''. When players subscribe to such trial, it will be listed in their ''CHALLENGES'' menu.

	* You need to manually add the ''TimeTrial'' tag while publishing to Workshop!		* You need to manually add the ''TimeTrial'' tag while publishing to Workshop!

Lou Montana: Some wiki formatting

2022-07-21T23:08:57Z

Some wiki formatting

← Older revision		Revision as of 01:08, 22 July 2022
Line 31:		Line 31:
	<li>Place an empty vehicle named <var>BIS_TT_Vehicle</var> (this is a fixed system name; not all types of vehicles have been tested, but cars, helicopters and tanks should work).		<li>Place an empty vehicle named <var>BIS_TT_Vehicle</var> (this is a fixed system name; not all types of vehicles have been tested, but cars, helicopters and tanks should work).
	</li>		</li>
	<li>If the competitor character is not placed inside the vehicle from the start, ensure that this is done upon trial start, for example via competitor init: ~~{{ic\|~~this [[moveInDriver]] BIS_TT_Vehicle;}}.		<li>If the competitor character is not placed inside the vehicle from the start, ensure that this is done upon trial start, for example via competitor init: <sqf inline>this moveInDriver BIS_TT_Vehicle;</sqf>.
	</li>		</li>
	<li>Place a unit of type {{hl\|C_Marshal_F}} named <var>BIS_rangeOfficer</var> (this is a fixed system name; place the unit in a separate group and at a reasonable distance in order to see the starter pistol firing).		<li>Place a unit of type {{hl\|C_Marshal_F}} named <var>BIS_rangeOfficer</var> (this is a fixed system name; place the unit in a separate group and at a reasonable distance in order to see the starter pistol firing).

	Enter the following in <var>BIS_rangeOfficer</var>'s init field:		Enter the following in <var>BIS_rangeOfficer</var>'s init field:
	<~~code~~>this [[disableAI]] "ANIM";		<sqf>
	BIS_TT_handle = this [[spawn]] {		this disableAI "ANIM";
	[[waitUntil]] {[[time]] > 0};		BIS_TT_handle = this spawn {
	_this [[switchMove]] "Acts_starterPistol_loop";		waitUntil {time > 0};
	};</~~code~~>		_this switchMove "Acts_starterPistol_loop";
			};
			</sqf>
	</li>		</li>
	<li>Place a ''Time Trial'' module ({{hl\|ModuleTimeTrial_F}}). [[File:arma3 tt cp start.jpg\|thumb\|250px\|right\|Start CP setup]]</li>		<li>Place a ''Time Trial'' module ({{hl\|ModuleTimeTrial_F}}). [[File:arma3 tt cp start.jpg\|thumb\|250px\|right\|Start CP setup]]</li>
Line 88:		Line 90:
	<li>Place a fake player competitor character who is supposedly controlling the drone. Do not name this (or any other) character <var>BIS_TT_Competitor</var>!</li>		<li>Place a fake player competitor character who is supposedly controlling the drone. Do not name this (or any other) character <var>BIS_TT_Competitor</var>!</li>
	<li>In the trial's init script, execute:		<li>In the trial's init script, execute:
	<~~code~~>[[enableTeamSwitch~~]] [[~~false]];		<sqf>
	BIS_TT_Competitor = [[driver]] BIS_TT_Vehicle;		enableTeamSwitch false;
	[[selectPlayer]] BIS_TT_Competitor;</~~code~~>		BIS_TT_Competitor = driver BIS_TT_Vehicle;
			selectPlayer BIS_TT_Competitor;
			</sqf>
	</li>		</li>
	</ol>		</ol>
Line 318:		Line 322:

	Please see the [[Arma_3_Firing_Drills#Colors\|Firing Drills documentation]] for this information.		Please see the [[Arma_3_Firing_Drills#Colors\|Firing Drills documentation]] for this information.
	* Vanilla tanks trials use a different shade of green ''color'': ~~{{ic\|~~__EVAL(173/255), __EVAL(191/255), __EVAL(131/255), 1}}		* Vanilla tanks trials use a different shade of green ''color'': <syntaxhighlight lang="cpp" inline>__EVAL(173/255), __EVAL(191/255), __EVAL(131/255), 1</syntaxhighlight>
	* Vanilla IDAP trials use a different shade of orange ''color'': ~~{{ic\|~~__EVAL(229/255), __EVAL(103/255), __EVAL(34/255), 1}}		* Vanilla IDAP trials use a different shade of orange ''color'': <syntaxhighlight lang="cpp" inline>__EVAL(229/255), __EVAL(103/255), __EVAL( 34/255), 1</syntaxhighlight>

Ansin11: Reformatted Setup section, incorporated information provided by Cholt on Discord

2022-01-30T11:22:26Z

Reformatted Setup section, incorporated information provided by Cholt on Discord

Show changes

Lou Montana: Add "BIS_TT_Vehicle must begin inside BIS_TT_CP1" step

2022-01-30T11:09:02Z

Add "BIS_TT_Vehicle must begin inside BIS_TT_CP1" step

← Older revision		Revision as of 13:09, 30 January 2022
Line 55:		Line 55:
	## It is important to orient most CPs well to determine the valid entry angles (for example by left mouse button + left Shift rotating and dragging the arrow in the direction of the next CP).		## It is important to orient most CPs well to determine the valid entry angles (for example by left mouse button + left Shift rotating and dragging the arrow in the direction of the next CP).
	## Alternatively, use 3D helpers directly as CP objects (circles are commonly used for aerial trials).		## Alternatively, use 3D helpers directly as CP objects (circles are commonly used for aerial trials).
			# BIS_TT_Vehicle must begin inside BIS_TT_CP1
	# Set up trial properties via [[Description.ext\|description.ext]] (see below).		# Set up trial properties via [[Description.ext\|description.ext]] (see below).
	# Configure your drill via [[Description.ext\|description.ext]] or via ''CfgTimeTrials'' and ''CfgMissions'' (see below).		# Configure your drill via [[Description.ext\|description.ext]] or via ''CfgTimeTrials'' and ''CfgMissions'' (see below).

Lou Montana: Fix FD → TT

2022-01-30T11:07:22Z

Fix FD → TT

← Older revision		Revision as of 13:07, 30 January 2022
Line 44:		Line 44:
	## Position this target near the finish CP (so that it is visible and accessible to drive to after finishing).		## Position this target near the finish CP (so that it is visible and accessible to drive to after finishing).
	## In the target's ''Texture #0'' field, enter: {{ic\|A3\modules_f_beta\data\FiringDrills\restart_orange_ca}} {{cc\|Other colors have corresponding textures - see below}}		## In the target's ''Texture #0'' field, enter: {{ic\|A3\modules_f_beta\data\FiringDrills\restart_orange_ca}} {{cc\|Other colors have corresponding textures - see below}}
	# Insert a trigger with default properties named {{ic\|~~BIS_FD_restartSelector1~~}} {{cc\|Referenced later}}		# Insert a trigger with default properties named {{ic\|BIS_TT_restartSelector1}} {{cc\|Referenced later}}
	## Re-size and orient the trigger so that it encompasses the target above and forms a suitable 'parking' spot for the chosen vehicle.		## Re-size and orient the trigger so that it encompasses the target above and forms a suitable 'parking' spot for the chosen vehicle.
	# Copy and paste the restart target.		# Copy and paste the restart target.
	## Position it near the first target, typically right from it (but spaced to comfortably allow your chosen vehicle type to access both).		## Position it near the first target, typically right from it (but spaced to comfortably allow your chosen vehicle type to access both).
	## In the target's ''Texture #0'' field, enter: {{ic\|A3\modules_f_beta\data\FiringDrills\quit_ca}} {{cc\|Fixed texture no matter the drill color}}		## In the target's ''Texture #0'' field, enter: {{ic\|A3\modules_f_beta\data\FiringDrills\quit_ca}} {{cc\|Fixed texture no matter the drill color}}
	# Insert a trigger with default properties named {{ic\|~~BIS_FD_quitSelector1~~}} {{cc\|Referenced later}}		# Insert a trigger with default properties named {{ic\|BIS_TT_quitSelector1}} {{cc\|Referenced later}}
	## Re-size and orient the trigger so that it encompasses the target above and forms a suitable 'parking' spot for the chosen vehicle. [[File:arma3 tt cp finish.jpg\|thumb\|250px\|right\|Finish CP setup]]		## Re-size and orient the trigger so that it encompasses the target above and forms a suitable 'parking' spot for the chosen vehicle. [[File:arma3 tt cp finish.jpg\|thumb\|250px\|right\|Finish CP setup]]
	# For each CP (including start and finish), insert a trigger with default properties named f.e. {{ic\|BIS_TT_CP1}} {{cc\|Referenced later}}		# For each CP (including start and finish), insert a trigger with default properties named f.e. {{ic\|BIS_TT_CP1}} {{cc\|Referenced later}}

Lou Montana: Text replacement - "description.ext" to "description.ext"

2021-08-18T09:58:08Z

Text replacement - "description.ext" to "description.ext"

← Older revision		Revision as of 11:58, 18 August 2021
Line 55:		Line 55:
	## It is important to orient most CPs well to determine the valid entry angles (for example by left mouse button + left Shift rotating and dragging the arrow in the direction of the next CP).		## It is important to orient most CPs well to determine the valid entry angles (for example by left mouse button + left Shift rotating and dragging the arrow in the direction of the next CP).
	## Alternatively, use 3D helpers directly as CP objects (circles are commonly used for aerial trials).		## Alternatively, use 3D helpers directly as CP objects (circles are commonly used for aerial trials).
	# Set up trial properties via [[description.ext]] (see below).		# Set up trial properties via [[Description.ext\|description.ext]] (see below).
	# Configure your drill via [[description.ext]] or via ''CfgTimeTrials'' and ''CfgMissions'' (see below).		# Configure your drill via [[Description.ext\|description.ext]] or via ''CfgTimeTrials'' and ''CfgMissions'' (see below).

	== Drones ==		== Drones ==
Line 274:		Line 274:
	= Steam Workshop =		= Steam Workshop =

	When a trial is self-contained (i.e. configured via [[description.ext]]), it can be published to {{ExternalLink\|link= https://steamcommunity.com/workshop/browse/?appid=107410\|text= Steam Workshop}} as ''Scenario''. When players subscribe to such trial, it will be listed in their ''CHALLENGES'' menu.		When a trial is self-contained (i.e. configured via [[Description.ext\|description.ext]]), it can be published to {{ExternalLink\|link= https://steamcommunity.com/workshop/browse/?appid=107410\|text= Steam Workshop}} as ''Scenario''. When players subscribe to such trial, it will be listed in their ''CHALLENGES'' menu.

	* You need to manually add the ''TimeTrial'' tag while publishing to Workshop!		* You need to manually add the ''TimeTrial'' tag while publishing to Workshop!