ScriptTypes/ScriptActions - Revision history

Crimsonum: Note on Do This mission types.

2025-06-01T19:14:26Z

Note on Do This mission types.

← Older revision		Revision as of 21:14, 1 June 2025
Line 153:		Line 153:

	Not all of the available mission types are applicable to teams; those that are, such as {{tt\|Sleep}}, {{tt\|Sticky}}, {{tt\|Guard}}, {{tt\|Area Guard}}, {{tt\|Hunt}}, are perpetual by nature so once assigned to a team, the units in the team will remain in that mission until those units are destroyed, the team is dissolved, or the units are recruited into another team and given a different mission. Because the missions are never-ending, this script action can't finish and move to the next script action. Thus, this script action is best given as the last script action in the script.		Not all of the available mission types are applicable to teams; those that are, such as {{tt\|Sleep}}, {{tt\|Sticky}}, {{tt\|Guard}}, {{tt\|Area Guard}}, {{tt\|Hunt}}, are perpetual by nature so once assigned to a team, the units in the team will remain in that mission until those units are destroyed, the team is dissolved, or the units are recruited into another team and given a different mission. Because the missions are never-ending, this script action can't finish and move to the next script action. Thus, this script action is best given as the last script action in the script.

			Note that unlike some of the other team missions, teams in these missions do not respond to attacks in a coordinated manner. That is, if one member of the team is attacked by an enemy, it will not provoke the other members of the team to respond unless they themselves are attacked.

	The following are valid settings for the second parameter:		The following are valid settings for the second parameter:

Crimsonum: Note on various guard missions

2025-05-31T19:47:04Z

Note on various guard missions

← Older revision		Revision as of 21:47, 31 May 2025
Line 102:		Line 102:
	\|style="text-align: center;"\|Time{{fnl\|3}}		\|style="text-align: center;"\|Time{{fnl\|3}}
	\|'''Guard Area'''		\|'''Guard Area'''
	This instructs the team to put the task force into Guard ~~Mode~~ for the amount of time specified. ~~Units~~ will ~~move to~~ attack enemy units that fall within their range. After guarding for the amount of time specified, the team will move on to execute its next script action.		This instructs the team to put the task force into Guard mode for the amount of time specified. The team members will attack enemy units that fall within their weapon range, but they will not pursue enemies even when provoked. After guarding for the amount of time specified, the team will move on to execute its next script action.
	\|-		\|-
	\|style="text-align: center;"\|6		\|style="text-align: center;"\|6
Line 185:		Line 185:
	\|5		\|5
	\|Guard		\|Guard
	\|object sits around and will engage an enemy that falls within its weapon range		\|object sits around and will engage and pursue an enemy that falls within its weapon range or attacks it
	\|-		\|-
	\|6		\|6

MarkJFox: 16 revisions imported

2025-03-31T20:04:03Z

16 revisions imported

← Older revision	Revision as of 22:04, 31 March 2025
(No difference)

en>Crimsonum: More information on Hunt and Attack: Anything

2024-09-13T15:25:54Z

More information on Hunt and Attack: Anything

← Older revision		Revision as of 17:25, 13 September 2024
Line 31:		Line 31:
	\|1		\|1
	\|Anything		\|Anything
	\|Enemy [[TechnoTypes\|vehicle, aircraft, infantry or building]]. ~~Works~~ the same as "Hunt" (see action {{tt\|11}} below).		\|Enemy [[TechnoTypes\|vehicle, aircraft, infantry or building]]. Target selection works the same as in the "Hunt" mission (see action {{tt\|11}} below). However, unlike in Hunt, if the team is attacked, it will retaliate and pursue the attackers, provided that the team has {{f\|Suicide\|no\|link}}.
	\|-		\|-
	\|2		\|2
Line 221:		Line 221:
	\|14		\|14
	\|Hunt		\|Hunt
	\|scan for and attack enemies wherever they may be on the map. Chooses the target based on threat or first built. See [[TargetDistanceCoefficientDefault]] for more information.		\|scan for and attack enemies wherever they may be on the map. Chooses the target based on threat or first built. See [[TargetDistanceCoefficientDefault]] for more information. Will not retaliate if attacked.
	\|-		\|-
	\|15		\|15

en>Crimsonum: Note about Hunt

2024-09-13T15:09:06Z

Note about Hunt

← Older revision		Revision as of 17:09, 13 September 2024
Line 31:		Line 31:
	\|1		\|1
	\|Anything		\|Anything
	\|Enemy [[TechnoTypes\|vehicle, aircraft, infantry or building]]		\|Enemy [[TechnoTypes\|vehicle, aircraft, infantry or building]]. Works the same as "Hunt" (see action {{tt\|11}} below).
	\|-		\|-
	\|2		\|2
Line 221:		Line 221:
	\|14		\|14
	\|Hunt		\|Hunt
	\|scan for and attack enemies wherever they may be on the map		\|scan for and attack enemies wherever they may be on the map. Chooses the target based on threat or first built. See [[TargetDistanceCoefficientDefault]] for more information.
	\|-		\|-
	\|15		\|15

en>Crimsonum at 13:49, 24 June 2024

2024-06-24T13:49:43Z

← Older revision		Revision as of 15:49, 24 June 2024
Line 83:		Line 83:
	\|style="text-align: center;"\|2		\|style="text-align: center;"\|2
	\|style="text-align: center;"\|0		\|style="text-align: center;"\|0
	\|'''~~Do Nothing~~'''		\|'''Go Berzerk'''
	~~With no associated~~ action ~~perform~~, the team moves on to the next action in the script, if present.		{{obsolete\|{{ts}} to {{yr}}\|Go Berzerk}}
			Would have caused [[cyborg]] infantry in the team to go [[BerzerkAllowed\|berserk]]. This action is obsolete, so the team simply moves on to the next action in the script, if present.
	\|-		\|-
	\|style="text-align: center;"\|3		\|style="text-align: center;"\|3

en>Crimsonum: Updated

2024-06-23T10:55:28Z

Updated

← Older revision		Revision as of 12:55, 23 June 2024
Line 38:		Line 38:
	\|-		\|-
	\|3		\|3
	\|Harvesters/Ore Miners		\|Harvesters, Refineries, and Silos /<br/>Ore Miners
	\|Enemy vehicle with {{f\|Harvester\|yes\|link}} set		\|Enemy vehicle with {{f\|Harvester\|yes\|link}} set.<br/>In Tiberian Sun, this quarry also includes enemy Tiberium Refineries and Silos.
	\|-		\|-
	\|4		\|4

en>Crimsonum: Minor adjustment.

2024-06-19T10:26:59Z

Minor adjustment.

← Older revision		Revision as of 12:26, 19 June 2024
Line 15:		Line 15:
	This instructs the team to approach and attack a target that fits the [[QuarryTypes\|quarry type]] (target category){{fnl\|1}} specified by the second parameter. Target selection from this category is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes\|technotype]] override of [[TargetDistanceCoefficient]].		This instructs the team to approach and attack a target that fits the [[QuarryTypes\|quarry type]] (target category){{fnl\|1}} specified by the second parameter. Target selection from this category is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes\|technotype]] override of [[TargetDistanceCoefficient]].

	These attack missions are inherently self-repeating. For example, when executing script action {{tt\|0,2}} ("attack building"), the task force will attack the next [[BuildingTypes\|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack, the script action is complete and the task force moves on to execute the next script action, if any.		These attack missions are inherently self-repeating. For example, when executing script action {{tt\|0,2}} ("attack building"), the task force will attack the next [[BuildingTypes\|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack (either destroyed or inaccessible), the script action is complete and the task force moves on to execute the next script action, if any.

	Note that the completion of this script action can get cut short in case the task force gets destroyed or runs out of ammo.		Note that the completion of this script action can get cut short in case the task force gets destroyed or runs out of ammo.

en>Crimsonum: Added a warning about changing teams, and note about changing scripts

2024-02-04T20:44:00Z

Added a warning about changing teams, and note about changing scripts

← Older revision		Revision as of 22:44, 4 February 2024
Line 425:		Line 425:
	\|style="text-align: center;"\|Script#{{fnl\|2}}		\|style="text-align: center;"\|Script#{{fnl\|2}}
	\|'''Change Script'''		\|'''Change Script'''
			{{obsolete\|{{ts}}\|Change Script}}
	Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes\|script type]] to execute as listed in the {{tt\|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).		Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes\|script type]] to execute as listed in the {{tt\|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).

			Appears not to work, at least in Tiberian Sun.
	\|-		\|-
	\|style="text-align: center;"\|18		\|style="text-align: center;"\|18
	\|style="text-align: center;"\|Team#{{fnl\|2}}		\|style="text-align: center;"\|Team#{{fnl\|2}}
	\|'''Change Team'''		\|'''Change Team'''
	This instructs the task force to ~~join~~ another team. The second parameter specifies the number of the [[TeamTypes\|team type]] to ~~join~~ as listed in the {{tt\|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).		This instructs the task force to switch to another team. The second parameter specifies the number of the [[TeamTypes\|team type]] to switch to as listed in the {{tt\|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).

			{{W}} '''Note:''' The game loads team types from {{ini\|ai}} first, then [[aifs.ini]] second ([[RequiredAddOn\|if applicable]]), and the current map last. Because this action refers to a team by its index, it's prone to break as the index will change whenever you add or remove teams from any of the AI [[INIs]]. Therefore it is ''not'' recommended to use this action. A much more reliable method is to use [[Actions_(maps)\|trigger actions]] to recruit the units to a new team, as triggers refer to teams by their names, not indexes.
	\|-		\|-
	\|style="text-align: center;"\|19		\|style="text-align: center;"\|19

en>E1 Elite: Script actions 0 and 57 update.

2023-06-17T15:51:57Z

Script actions 0 and 57 update.

← Older revision		Revision as of 17:51, 17 June 2023
Line 13:		Line 13:
	\|style="text-align: center;"\|Quarry Type#{{fnl\|1}}{{fnl\|2}}		\|style="text-align: center;"\|Quarry Type#{{fnl\|1}}{{fnl\|2}}
	\|'''Attack Quarry Type'''		\|'''Attack Quarry Type'''
	This instructs the team ~~to use the task force~~ to approach and attack a target that fits the [[QuarryTypes\|quarry type]] (target category){{fnl\|1}} specified by the second parameter. ~~The target is selected~~ from this category based on ~~distance,~~ [[~~TechnoTypes\|object type~~]]~~, and/~~or [[~~SpecialThreatValue~~\|~~threat posed~~]]~~. See~~ [[~~the Threat System]] and specifically [[TargetDistanceCoefficientDefault~~]] ~~for more information~~.		This instructs the team to approach and attack a target that fits the [[QuarryTypes\|quarry type]] (target category){{fnl\|1}} specified by the second parameter. Target selection from this category is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes\|technotype]] override of [[TargetDistanceCoefficient]].

	These attack missions are inherently self-repeating. For example, when executing script action {{tt\|0,2}} ("attack building"), the task force will attack the next [[BuildingTypes\|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack, the script action is complete and the task force moves on to execute the next script action, if any.		These attack missions are inherently self-repeating. For example, when executing script action {{tt\|0,2}} ("attack building"), the task force will attack the next [[BuildingTypes\|building]] when the current building being attacked is destroyed and will continue to destroy enemy buildings until there are no more left. When no more targets are left to attack, the script action is complete and the task force moves on to execute the next script action, if any.
Line 31:		Line 31:
	\|1		\|1
	\|Anything		\|Anything
	\|~~Any enemy~~ [[TechnoTypes\|vehicle~~, infantry~~, aircraft, or building]]		\|Enemy [[TechnoTypes\|vehicle, aircraft, infantry or building]]
	\|-		\|-
	\|2		\|2
	\|Structures		\|Structures
	\|~~Any enemy~~ [[BuildingTypes\|building]]		\|Enemy [[BuildingTypes\|building]]
	\|-		\|-
	\|3		\|3
	\|Harvesters/Ore Miners		\|Harvesters/Ore Miners
	\|~~Any enemy~~ vehicle with {{f\|Harvester\|yes\|link}} set		\|Enemy vehicle with {{f\|Harvester\|yes\|link}} set
	\|-		\|-
	\|4		\|4
	\|Infantry		\|Infantry
	\|~~Any enemy~~ [[InfantryTypes\|infantry]]		\|Enemy [[InfantryTypes\|infantry]]
	\|-		\|-
	\|5		\|5
	\|Vehicles		\|Vehicles
	\|~~Any enemy~~ [[VehicleTypes\|vehicle]]		\|Enemy [[VehicleTypes\|vehicle]]
	\|-		\|-
	\|6		\|6
	\|Factories		\|Factories
	\|~~Any enemy~~ building with {{f\|Factory\|link}} set		\|Enemy building with {{f\|Factory\|link}} set
	\|-		\|-
	\|7		\|7
	\|Base Defenses		\|Base Defenses
	\|~~Any enemy~~ building with {{f\|IsBaseDefense\|yes\|link}} set		\|Enemy building with {{f\|IsBaseDefense\|yes\|link}} set
	\|-		\|-
	\|8		\|8
	\|Base Threats		\|Base Threats
	\|~~Any enemy~~ [[UnitTypes\|unit]] approaching (or already in) its base and which are in an attack mission		\|Enemy [[UnitTypes\|unit]] approaching (or already in) its base and which are in an attack mission
	\|-		\|-
	\|9		\|9
	\|Power Plants		\|Power Plants
	\|~~Any enemy~~ building with a positive {{f\|Power\|link}} value set		\|Enemy building with a positive {{f\|Power\|link}} value set
	\|-		\|-
	!colspan="3"\|{{Ra2}} additions		!colspan="3"\|{{Ra2}} additions
Line 69:		Line 69:
	\|10		\|10
	\|Occupiable		\|Occupiable
	\|~~Any building~~ with {{f\|CanBeOccupied\|yes\|link}} set (usually neutral structures)		\|Building with {{f\|CanBeOccupied\|yes\|link}} set (usually neutral structures)
	\|-		\|-
	\|11		\|11
	\|Tech Buildings		\|Tech Buildings
	\|~~Any building~~ with {{f\|NeedsEngineer\|yes\|link}} set (usually [[NeutralTechBuildings\|neutral tech buildings]])		\|Building with {{f\|NeedsEngineer\|yes\|link}} set (usually [[NeutralTechBuildings\|neutral tech buildings]])
	\|}		\|}
	\|-		\|-
Line 683:		Line 683:
	\|style="text-align: center;"\|Quarry Type#{{fnl\|2}}		\|style="text-align: center;"\|Quarry Type#{{fnl\|2}}
	\|'''Chronoshift Task Force to a target type'''		\|'''Chronoshift Task Force to a target type'''
	If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to a target that fits the [[QuarryTypes\|quarry type]] (target category) specified by the second parameter ~~(exact target being what game determines to be the greatest threat)~~, before moving on to the next script action. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f\|AIMinorSuperReadyPercent\|link}} statement in RULES.INI.		If the owner of the task force to which this script is attached also has the Chronosphere fully charged then it will be used on the task force to transport it to a target that fits the [[QuarryTypes\|quarry type]] (target category) specified by the second parameter, before moving on to the next script action. Target selection is based on nearest/first built depending on the scan range defined by [[TargetDistanceCoefficientDefault]] or its [[TechnoTypes\|technotype]] override of [[TargetDistanceCoefficient]]. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into its actions as defined by the {{f\|AIMinorSuperReadyPercent\|link}} statement in RULES.INI.
	\|-		\|-
	\|style="text-align: center;"\|58		\|style="text-align: center;"\|58

← Older revision		Revision as of 22:44, 4 February 2024
Line 425:		Line 425:
	\|style="text-align: center;"\|Script#{{fnl\|2}}		\|style="text-align: center;"\|Script#{{fnl\|2}}
	\|'''Change Script'''		\|'''Change Script'''
			{{obsolete\|{{ts}}\|Change Script}}
	Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes\|script type]] to execute as listed in the {{tt\|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).		Very handy and under utilized - this instructs the task force to execute another script. The second parameter specifies the number of the [[ScriptTypes\|script type]] to execute as listed in the {{tt\|[ScriptTypes]}} table (consider the table as being numbered starting at 0 for this purpose).

			Appears not to work, at least in Tiberian Sun.
	\|-		\|-
	\|style="text-align: center;"\|18		\|style="text-align: center;"\|18
	\|style="text-align: center;"\|Team#{{fnl\|2}}		\|style="text-align: center;"\|Team#{{fnl\|2}}
	\|'''Change Team'''		\|'''Change Team'''
	This instructs the task force to ~~join~~ another team. The second parameter specifies the number of the [[TeamTypes\|team type]] to ~~join~~ as listed in the {{tt\|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).		This instructs the task force to switch to another team. The second parameter specifies the number of the [[TeamTypes\|team type]] to switch to as listed in the {{tt\|[TeamTypes]}} table (consider the table as being numbered starting at 0 for this purpose).

			{{W}} '''Note:''' The game loads team types from {{ini\|ai}} first, then [[aifs.ini]] second ([[RequiredAddOn\|if applicable]]), and the current map last. Because this action refers to a team by its index, it's prone to break as the index will change whenever you add or remove teams from any of the AI [[INIs]]. Therefore it is ''not'' recommended to use this action. A much more reliable method is to use [[Actions_(maps)\|trigger actions]] to recruit the units to a new team, as triggers refer to teams by their names, not indexes.
	\|-		\|-
	\|style="text-align: center;"\|19		\|style="text-align: center;"\|19