Spawning AI with triggers - Revision history

Jester2138 at 20:53, 21 July 2018

2018-07-21T20:53:53Z

← Older revision		Revision as of 20:53, 21 July 2018
Line 1:		Line 1:
	There is a little-documented but easy method to spawn AI in complex arrangements without scripting a bunch of stuff.		There is a little-documented but easy method to spawn AI in complex arrangements without scripting a bunch of stuff.

	If you use this method, be sure to note how it gets activated in the notes accompanying your ~~missions~~ submission so QA can test it.		If you use this method, be sure to note how it gets activated in the notes accompanying your mission submission so QA can test it.

	Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8		Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8

Jester2138 at 20:53, 21 July 2018

2018-07-21T20:53:41Z

← Older revision		Revision as of 20:53, 21 July 2018
Line 1:		Line 1:
	There is a little-documented but easy method to spawn AI in complex arrangements without scripting a bunch of stuff.		There is a little-documented but easy method to spawn AI in complex arrangements without scripting a bunch of stuff.

			If you use this method, be sure to note how it gets activated in the notes accompanying your missions submission so QA can test it.

	Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8		Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8

Jester2138 at 23:01, 18 April 2018

2018-04-18T23:01:23Z

← Older revision		Revision as of 23:01, 18 April 2018
Line 42:		Line 42:
	*''Server Only:'' checked		*''Server Only:'' checked
	*''Condition:''		*''Condition:''
	<nowiki>this;</nowiki>		<nowiki>
			this;
			</nowiki>
	*''On Activation:''		*''On Activation:''
	<nowiki>		<nowiki>

Jester2138 at 23:01, 18 April 2018

2018-04-18T23:01:07Z

← Older revision		Revision as of 23:01, 18 April 2018
Line 41:		Line 41:
	*''Repeatable:'' unchecked		*''Repeatable:'' unchecked
	*''Server Only:'' checked		*''Server Only:'' checked
	*''Condition:'' this;		*''Condition:''
			<nowiki>this;</nowiki>
	*''On Activation:''		*''On Activation:''
	<nowiki>		<nowiki>

Jester2138 at 23:00, 18 April 2018

2018-04-18T23:00:37Z

← Older revision		Revision as of 23:00, 18 April 2018
Line 33:		Line 33:
	'''In the trigger that waits for a condition to be met and then loads the scene:'''		'''In the trigger that waits for a condition to be met and then loads the scene:'''

	You can set it up however you want depending on how you want to activate the trigger~~, but the "On Activation" field must contain the command below~~. Here's how to do it so that when a Blufor unit enters the area, the scene loads:		You can set it up however you want depending on how you want to activate the trigger. Here's how to do it so that when a Blufor unit enters the area, the scene loads:

	*''Variable Name:'' whatever you want, e.g. "loadScene"		*''Variable Name:'' whatever you want, e.g. "loadScene"

Jester2138 at 22:59, 18 April 2018

2018-04-18T22:59:51Z

← Older revision		Revision as of 22:59, 18 April 2018
Line 27:		Line 27:
	<nowiki>		<nowiki>
	[thisTrigger, "Scene"] call mytag_fnc_savescene;		[thisTrigger, "Scene"] call mytag_fnc_savescene;
	["Scene", false] call mytag_fnc_deletescene		["Scene", false] call mytag_fnc_deletescene;
	</nowiki>		</nowiki>
	*''On Deactivation:'' leave blank		*''On Deactivation:'' leave blank
Line 33:		Line 33:
	'''In the trigger that waits for a condition to be met and then loads the scene:'''		'''In the trigger that waits for a condition to be met and then loads the scene:'''

	You can set it up however you want depending on how you want to activate the trigger, but the "On Activation" field must contain the command below. Here's how to do it so that when a Blufor ~~player (and only a player, not an AI. Thus is "player in thisList" condition)~~ enters the area, the scene loads:		You can set it up however you want depending on how you want to activate the trigger, but the "On Activation" field must contain the command below. Here's how to do it so that when a Blufor unit enters the area, the scene loads:

	*''Variable Name:'' whatever you want, e.g. "loadScene"		*''Variable Name:'' whatever you want, e.g. "loadScene"
Line 41:		Line 41:
	*''Repeatable:'' unchecked		*''Repeatable:'' unchecked
	*''Server Only:'' checked		*''Server Only:'' checked
	*''Condition:'' ~~vehicle player in thisList~~		*''Condition:'' this;
	*''On Activation:''		*''On Activation:''
	<nowiki>		<nowiki>
	["Scene", false] call mytag_fnc_loadscene;		["Scene", false] call mytag_fnc_loadscene;
	["Scene2", false] call mytag_fnc_loadscene		["Scene2", false] call mytag_fnc_loadscene;
	</nowiki>		</nowiki>
	*''On Deactivation:'' leave blank		*''On Deactivation:'' leave blank

Jester2138 at 22:16, 18 April 2018

2018-04-18T22:16:36Z

← Older revision		Revision as of 22:16, 18 April 2018
Line 7:		Line 7:
	In the editor, you'll see all the AI placed as well as two triggers. The first trigger looks at all the AI in its area, saves their locations and waypoints, and immediately deletes them. The second trigger loads what was saved in the first when the player walks onto the bridge. Load the mission '''in MP''' and you'll see that when you walk onto the bridge a few AI spawn in front of you with cycling waypoints. It must be loaded in MP because the triggers will only run on the server.		In the editor, you'll see all the AI placed as well as two triggers. The first trigger looks at all the AI in its area, saves their locations and waypoints, and immediately deletes them. The second trigger loads what was saved in the first when the player walks onto the bridge. Load the mission '''in MP''' and you'll see that when you walk onto the bridge a few AI spawn in front of you with cycling waypoints. It must be loaded in MP because the triggers will only run on the server.

	Note: for cycling waypoints to work, you must place the "Cycle" waypoint such that a line is automatically drawn between it and the first "Move" waypoint. This is because the function does not save which waypoint is currently active, and if the final "Cycle" is not connected to the first "Move," the AI will only go through the list once and then stop. If this doesn't make sense, look at the example mission and note how the waypoints are placed.		Note: for cycling waypoints to work, you must place the "Cycle" waypoint such that a line is automatically drawn between it and the first "Move" waypoint. This is because the function does not save which waypoint is currently active, and if the final "Cycle" is not connected to the first "Move," the AI will only go through the list once and then stop. If this doesn't make sense, look at the example mission and note how the waypoints are placed. NOTE: waypoints do NOT have to be in the trigger area, only the group to which they are assigned does.

	'''There are three steps to making this work in your mission:'''		'''There are three steps to making this work in your mission:'''

Jester2138 at 22:15, 18 April 2018

2018-04-18T22:15:14Z

← Older revision		Revision as of 22:15, 18 April 2018
Line 3:		Line 3:
	Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8		Here is an example vanilla-Arma mission on Jester's Google Drive: https://drive.google.com/open?id=1mn49T-tMc3TO4rG5V-fD-S32tCghy8I8

	This works great for loading objective areas only as they're needed for performance reasons, or for spawning specific ambushes, or any number of things.		This works great for loading objective areas only as they're needed for performance reasons, or for spawning specific ambushes, or any number of things that are normally only easily done with a Zeus.

	In the editor, you'll see all the AI placed as well as two triggers. The first trigger looks at all the AI in its area, saves their locations and waypoints, and immediately deletes them. The second trigger loads what was saved in the first when the player walks onto the bridge. Load the mission '''in MP''' and you'll see that when you walk onto the bridge a few AI spawn in front of you with cycling waypoints. It must be loaded in MP because the triggers will only run on the server.		In the editor, you'll see all the AI placed as well as two triggers. The first trigger looks at all the AI in its area, saves their locations and waypoints, and immediately deletes them. The second trigger loads what was saved in the first when the player walks onto the bridge. Load the mission '''in MP''' and you'll see that when you walk onto the bridge a few AI spawn in front of you with cycling waypoints. It must be loaded in MP because the triggers will only run on the server.

Jester2138 at 22:09, 18 April 2018

2018-04-18T22:09:30Z

← Older revision		Revision as of 22:09, 18 April 2018
Line 41:		Line 41:
	*''Repeatable:'' unchecked		*''Repeatable:'' unchecked
	*''Server Only:'' checked		*''Server Only:'' checked
	*''Condition:'' player in thisList		*''Condition:'' vehicle player in thisList
	*''On Activation:''		*''On Activation:''
	<nowiki>		<nowiki>

Jehmimah at 07:53, 16 April 2018

2018-04-16T07:53:38Z

← Older revision		Revision as of 07:53, 16 April 2018
Line 72:		Line 72:
	</nowiki>		</nowiki>

	It should look like this: [[File:Notepad++ 2018-04-16 00-51-41.png]]		It should look like this:

			[[File:Notepad++ 2018-04-16 00-51-41.png]]