Triggers - Revision history

JYWLuca8269: Updated look.

2020-11-24T15:33:10Z

Updated look.

AlphonsoHornibro: /* Var */

2018-02-22T11:11:21Z

Var

← Older revision		Revision as of 11:11, 22 February 2018
Line 99:		Line 99:
	*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''		*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''

	This is useful if you want to make capturing 4 regions or killing 4 AI players do something, but only when all of them have been done at the same time. However, you have to be careful in the case of capturing all 4 regions that it doesn't get messed up by if the AI captures the region back. This is where conditional triggers ~~can be useful~~.		This is useful if you want to make capturing 4 regions or killing 4 AI players do something, but only when all of them have been done at the same time. However, you have to be careful in the case of capturing all 4 regions that it doesn't get messed up by if the AI captures the region back. This is where conditional triggers are essential.

	=== [[ZoneCapture_Trigger\|ZoneCapture]] ===		=== [[ZoneCapture_Trigger\|ZoneCapture]] ===

AlphonsoHornibro: /* Var */

2018-02-22T11:11:07Z

Var

← Older revision		Revision as of 11:11, 22 February 2018
Line 97:		Line 97:
	*'''Operator''' - What logical operator to use when evaluating the variable (equal to, less than, etc) '''[ == \| >= \| <= \| > \| < \| != ]'''		*'''Operator''' - What logical operator to use when evaluating the variable (equal to, less than, etc) '''[ == \| >= \| <= \| > \| < \| != ]'''
	*'''Value''' - The (integer) value to compare the variable against		*'''Value''' - The (integer) value to compare the variable against
	*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''		*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''

			This is useful if you want to make capturing 4 regions or killing 4 AI players do something, but only when all of them have been done at the same time. However, you have to be careful in the case of capturing all 4 regions that it doesn't get messed up by if the AI captures the region back. This is where conditional triggers can be useful.

	=== [[ZoneCapture_Trigger\|ZoneCapture]] ===		=== [[ZoneCapture_Trigger\|ZoneCapture]] ===

AlphonsoHornibro: /* Conditional Triggers */

2018-02-22T11:09:06Z

Conditional Triggers

← Older revision		Revision as of 11:09, 22 February 2018
Line 25:		Line 25:
	<Trigger>		<Trigger>

	In this case, the NotOtherTrigger means do not run the unit spawn trigger if the SpawnSuppression Trigger has been activated, (a certain region has been captured.) NotOtherTrigger="Difficulty4" means don't run the trigger if the player is playing on Expert.		In this case, the NotOtherTrigger means do not run the unit spawn trigger if the SpawnSuppression Trigger has been activated, (a certain region has been captured.) Another example is NotOtherTrigger="Difficulty4" means don't run the trigger if the player is playing on Expert.

	== Common Trigger Arguments ==		== Common Trigger Arguments ==

AlphonsoHornibro: /* Conditional Triggers */

2018-02-22T11:08:48Z

Conditional Triggers

← Older revision		Revision as of 11:08, 22 February 2018
Line 14:		Line 14:
	== Conditional Triggers ==		== Conditional Triggers ==

	Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game. However, you can't stack multiple Conditional Triggers.		Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game. However, you can't stack multiple Conditional Triggers. To word it another way, OtherTrigger="Triggername" means only run the Trigger if this Trigger has happened, while NotOtherTrigger means only run the Trigger if this other Trigger hasn't happened.

	There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.		There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.

			Here's what that may look like:

			<Trigger Name="tNE_Spawn1" Type="Var" Var="vNE_Spawn" Operator="==" Value="1" NotOtherTrigger="tNE_SpawnSuppress" >
			<SpawnUnit Name="uNE_Leader1" Template="PHC_2_Zeus" Player="5" Position="-9344,-8064" /><Trigger Name="tNE_Spawn1" Type="Var" Var="vNE_Spawn" Operator="==" Value="1" NotOtherTrigger="tNE_SpawnSuppress" >
			<SpawnUnit Name="uNE_Leader1" Template="PHC_2_Zeus" Player="5" Position="-9344,-8064" />
			<Trigger>

			In this case, the NotOtherTrigger means do not run the unit spawn trigger if the SpawnSuppression Trigger has been activated, (a certain region has been captured.) NotOtherTrigger="Difficulty4" means don't run the trigger if the player is playing on Expert.

	== Common Trigger Arguments ==		== Common Trigger Arguments ==

AlphonsoHornibro: /* Conditional Triggers */

2018-02-22T10:44:06Z

Conditional Triggers

← Older revision		Revision as of 10:44, 22 February 2018
Line 14:		Line 14:
	== Conditional Triggers ==		== Conditional Triggers ==

	Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game.		Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game. However, you can't stack multiple Conditional Triggers.

	There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.		There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.

Patiobattle04 at 20:14, 18 January 2017

2017-01-18T20:14:25Z

← Older revision		Revision as of 20:14, 18 January 2017
Line 1:		Line 1:
			[[Category:Modding]]
	'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.		'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.

Patiobattle04 at 23:31, 17 January 2017

2017-01-17T23:31:21Z

← Older revision		Revision as of 23:31, 17 January 2017
Line 2:		Line 2:
	'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.		'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.

	==Active vs Inactive==		== Active vs Inactive ==

	Triggers are "active" by default, meaning they will fire whenever their condition is met. They can be set to Inactive manually in the script.		Triggers are "active" by default, meaning they will fire whenever their condition is met. They can be set to Inactive manually in the script.

	Triggers set themselves to Inactive when they fire. This means that if you want something to be repeatable, you need to reactivate it somewhere in the script.		Triggers set themselves to Inactive when they fire. This means that if you want something to be repeatable, you need to reactivate it somewhere in the script.

	==Repeating Triggers==		== Repeating Triggers ==

	Using <ActivateTrigger="triggername"/> to tell a trigger to activate itself will make it repeatable (if you want something to happen every time the player builds a Dreadnought, for example, or waves of enemies to spawn and attack every 15 seconds).		Using <ActivateTrigger="triggername"/> to tell a trigger to activate itself will make it repeatable (if you want something to happen every time the player builds a Dreadnought, for example, or waves of enemies to spawn and attack every 15 seconds).

	==Conditional Triggers==		== Conditional Triggers ==

	Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game.		Using the OtherTrigger and NotOtherTrigger arguments is a way to gate your scenario's logic. For purposes of those arguments, a trigger 'counts' '''if it has been activated at least once''' during the game.

	There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.		There is currently no way to "un-activate" a trigger, as far as OtherTrigger and NotOtherTrigger are concerned.

Patiobattle04 at 23:30, 17 January 2017

2017-01-17T23:30:39Z

@@ Line 1: / Line 1: @@
 '''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.
 == Common Trigger Arguments ==
 All triggers share some attributes in common:

Patiobattle04 at 22:34, 17 January 2017

2017-01-17T22:34:42Z

← Older revision		Revision as of 22:34, 17 January 2017
Line 1:		Line 1:
			'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.

	'''Triggers''' are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers ~~which activate off of different events, but they all~~ share some attributes in common:		== Common Trigger Arguments ==
			All triggers share some attributes in common:

	*'''Name''' - Name of the trigger. Required.		*'''Name''' - Name of the trigger. Required.
Line 12:		Line 14:
	These are the types of triggers you can use in a script, and any specific arguments they support.		These are the types of triggers you can use in a script, and any specific arguments they support.

	===[[Area_Trigger\|Area]]===		=== [[Area_Trigger\|Area]] ===

	Fires when the human player moves a unit into the area.		Fires when the human player moves a unit into the area.

Line 19:		Line 22:
	*'''Template''' - Template name of the unit that can trigger this. If you want it to fire if any unit enters the area, do not specify a Template argument.		*'''Template''' - Template name of the unit that can trigger this. If you want it to fire if any unit enters the area, do not specify a Template argument.

	===[[Build_Trigger\|Build]]===		=== [[Build_Trigger\|Build]] ===

	Fires when a human player builds structures or units.		Fires when a human player builds structures or units.

Line 26:		Line 30:
	*'''Count''' - How many of the target template must be built to fire the trigger (default 1)		*'''Count''' - How many of the target template must be built to fire the trigger (default 1)

	===[[Destruction_Trigger\|Destruction]]===		=== [[Destruction_Trigger\|Destruction]] ===

	Fires when something specific dies.		Fires when something specific dies.

Line 32:		Line 37:
	*'''Target''' - Name of the script-spawned unit or building.		*'''Target''' - Name of the script-spawned unit or building.

	===[[Difficulty_Trigger\|Difficulty]]===		=== [[Difficulty_Trigger\|Difficulty]] ===

	Fires at the beginning of a scenario if the given difficulty was chosen		Fires at the beginning of a scenario if the given difficulty was chosen

	*'''Difficulty''' - The given difficulty (0 for Much Easier, up to 4 for Much Harder)		*'''Difficulty''' - The given difficulty (0 for Much Easier, up to 4 for Much Harder)

			=== [[NamedCreate_Trigger\|NamedCreate]] ===

	~~===[[NamedCreate_Trigger\|NamedCreate]]===~~
	Fires when a specific unit or building is spawned via a script.		Fires when a specific unit or building is spawned via a script.

Line 44:		Line 50:
	*'''IsBuilding''' - If this is a building (if not it refers to a unit).		*'''IsBuilding''' - If this is a building (if not it refers to a unit).

	===[[Research_Trigger\|Research]]===		=== [[Research_Trigger\|Research]] ===

	Fires when a player researches a Quantum Upgrade		Fires when a player researches a Quantum Upgrade

Line 50:		Line 57:
	*'''Target''' - The name of the tech		*'''Target''' - The name of the tech

	===[[Timer_Trigger\|Timer]]===		=== [[Timer_Trigger\|Timer]] ===

	Fires after a delay.		Fires after a delay.

	*'''Time -''' Time in seconds after this gets triggered that it takes place.		*'''Time -''' Time in seconds after this gets triggered that it takes place.

	===[[Var_Trigger\|Var]]===		=== [[Var_Trigger\|Var]] ===

	Fires if a variable meets given criteria		Fires if a variable meets given criteria

Line 63:		Line 72:
	*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''		*''Example: <Trigger Name="tWeasleyDead" Type="Var" Var="vWeasleyDead" Operator="==" Value="1" > - this fires when the "vWeasleyDead" variable is equal to 1''

	===[[ZoneCapture_Trigger\|ZoneCapture]]===		=== [[ZoneCapture_Trigger\|ZoneCapture]] ===

	Fires when a region is captured.		Fires when a region is captured.

	*'''Owner''' - Player who must capture this region to fire the trigger.		*'''Owner''' - Player who must capture this region to fire the trigger.
	*'''Position''' - Map coordinates of the generator/Nexus.		*'''Position''' - Map coordinates of the generator/Nexus.