TaskForces - Revision history

MarkJFox: 7 revisions imported

2025-03-31T20:06:10Z

7 revisions imported

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

en>Crimsonum: Important note

2022-11-23T15:48:50Z

Important note

← Older revision		Revision as of 17:48, 23 November 2022
Line 29:		Line 29:
	*This section is read from {{Ini\|ai}} and the current map file.		*This section is read from {{Ini\|ai}} and the current map file.
	*Unlike [[AITriggerTypes]], there is no known difference on where a task force is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.		*Unlike [[AITriggerTypes]], there is no known difference on where a task force is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.
	*The hexadecimal prefix of a task force's ID is used in pointer remapping during saving and loading. It should not be lower than {{tt\|0x01000000}} to avoid conflicts with real pointers.		*{{W}} The hexadecimal prefix of a task force's ID (e.g. {{tt\|0832C3F0}}) is used in pointer remapping during saving and loading. It should not be lower than {{tt\|0x01000000}} to avoid conflicts with real pointers. In addition, it should be unique, i.e. it should not be shared across local and global task forces, or by any [[Tags\|Tag]], else they will remap to the same pointer.
	*The {{Tt\|-G}} suffix in a task force's ID is used to distinguish global ({{Ini\|ai}}) task forces from local (map) ones (which have no suffix).		*The {{Tt\|-G}} suffix in a task force's ID is used to distinguish global ({{Ini\|ai}}) task forces from local (map) ones (which have no suffix).

en>Crimsonum at 17:09, 20 June 2022

2022-06-20T17:09:25Z

← Older revision		Revision as of 19:09, 20 June 2022
Line 2:		Line 2:
	{{AIBar}}{{clr}}		{{AIBar}}{{clr}}
	{{MappingBar}}		{{MappingBar}}
	In {{ts}} through {{yr}}, this section defines a list of all AI ~~TaskForces~~ in the game. A ~~TaskForce~~ is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each ~~TaskForce~~ listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the ~~TaskForce~~'s units does care about its ordering - ~~it reads~~ the lines ~~indexed~~ from 0 to 5 in ascending order. The game also reads a flag named {{f\|Group\|link}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as ~~FinalAlert 2 or~~ [[AI Editor V2]] usually can use as well.		In {{ts}} through {{yr}}, this section defines a list of all AI task forces in the game. A task force is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each task force listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the task force's units ''does'' care about its ordering - the lines are read from index 0 to 5 in ascending order. The game also reads a flag named {{f\|Group\|link}} from each such section. It is common practice to add flags like {{f\|Name\|link}} for your own reference, which third party tools such as [[C&C AI Editor]] or [[Matze's_tools#FinalAlert\|FinalAlert 2]] usually can use as well.

	== Format ==		== Format ==
	[TaskForces]		<pre style="overflow: auto; white-space: pre">
	0 = 0638CD41-G		[TaskForces]
	1 = 0638CD42-G		0 = 0638CD41-G
			1 = 0638CD42-G
	[0638CD41-G]
	Index = count,unittype		[0638CD41-G]
	Index = count,unittype		Index = count,unittype
	Group = -1		Index = count,unittype
			Group = -1
	[0638CD42-G]
	Index = count,unittype		[0638CD42-G]
	Index = count,unittype		Index = count,unittype
	Group = -2		Index = count,unittype
			Group = -2
			</pre>

	Here, {{Tt\|count}} stands for the amount of this unit to recruit, and {{Tt\|unittype}} stands for the ID of the unit in question. [[AircraftTypes]], [[InfantryTypes]] and [[VehicleTypes]] are accepted here.		Here, {{Tt\|count}} stands for the amount of this unit to recruit, and {{Tt\|unittype}} stands for the ID of the unit in question. [[AircraftTypes]], [[InfantryTypes]] and [[VehicleTypes]] are accepted here.
Line 25:		Line 27:
	== Additional information ==		== Additional information ==

	*This section is read from {{Ini\|ai}} and the current map file.		*This section is read from {{Ini\|ai}} and the current map file.
	* Unlike [[AITriggerTypes]], there is no known difference on where a ~~TaskForce~~ is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.		*Unlike [[AITriggerTypes]], there is no known difference on where a task force is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.
	*The ~~infamous~~ {{Tt\|-G}} suffix is used to distinguish global ({{Ini\|ai}}) ~~TaskForces~~ from local (map) ones (which have no suffix)~~. It has no effect however.~~		*The hexadecimal prefix of a task force's ID is used in pointer remapping during saving and loading. It should not be lower than {{tt\|0x01000000}} to avoid conflicts with real pointers.
	*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.		*The {{Tt\|-G}} suffix in a task force's ID is used to distinguish global ({{Ini\|ai}}) task forces from local (map) ones (which have no suffix).

en>Crimsonum: Made a slight correction regarding the -G suffix.

2018-09-02T08:35:19Z

Made a slight correction regarding the -G suffix.

← Older revision		Revision as of 10:35, 2 September 2018
Line 27:		Line 27:
	*This section is read from {{Ini\|ai}} and the current map file.		*This section is read from {{Ini\|ai}} and the current map file.
	* Unlike [[AITriggerTypes]], there is no known difference on where a TaskForce is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.		* Unlike [[AITriggerTypes]], there is no known difference on where a TaskForce is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.
	*The infamous {{Tt\|-G}} suffix has no ~~meaning whatsoever~~.		*The infamous {{Tt\|-G}} suffix is used to distinguish global ({{Ini\|ai}}) TaskForces from local (map) ones (which have no suffix). It has no effect however.
	*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.		*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.

en>EvilRenegade: Replacing Template:TTL with Template:F.

2009-11-27T08:38:02Z

Replacing Template:TTL with Template:F.

← Older revision		Revision as of 10:38, 27 November 2009
Line 2:		Line 2:
	{{AIBar}}{{clr}}		{{AIBar}}{{clr}}
	{{MappingBar}}		{{MappingBar}}
	In {{ts}} through {{yr}}, this section defines a list of all AI TaskForces in the game. A TaskForce is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each TaskForce listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the TaskForce's units does care about its ordering - it reads the lines indexed from 0 to 5 in ascending order. The game also reads a flag named {{~~TTL~~\|Group}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as FinalAlert 2 or [[AI Editor V2]] usually can use as well.		In {{ts}} through {{yr}}, this section defines a list of all AI TaskForces in the game. A TaskForce is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each TaskForce listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the TaskForce's units does care about its ordering - it reads the lines indexed from 0 to 5 in ascending order. The game also reads a flag named {{f\|Group\|link}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as FinalAlert 2 or [[AI Editor V2]] usually can use as well.

	== Format ==		== Format ==

en>DCoder: Updating with new sidebar

2008-06-23T15:12:04Z

Updating with new sidebar

← Older revision		Revision as of 17:12, 23 June 2008
Line 1:		Line 1:
	{{WrongTitle\|[TaskForces]}}		{{WrongTitle\|[TaskForces]}}
	{{~~SideBar\|[[AI programming]]\|Template:AI~~}}		{{AIBar}}{{clr}}
			{{MappingBar}}
	In {{ts}} through {{yr}}, this section defines a list of all AI TaskForces in the game. A TaskForce is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each TaskForce listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the TaskForce's units does care about its ordering - it reads the lines indexed from 0 to 5 in ascending order. The game also reads a flag named {{TTL\|Group}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as FinalAlert 2 or [[AI Editor V2]] usually can use as well.		In {{ts}} through {{yr}}, this section defines a list of all AI TaskForces in the game. A TaskForce is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each TaskForce listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the TaskForce's units does care about its ordering - it reads the lines indexed from 0 to 5 in ascending order. The game also reads a flag named {{TTL\|Group}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as FinalAlert 2 or [[AI Editor V2]] usually can use as well.

Line 28:		Line 29:
	*The infamous {{Tt\|-G}} suffix has no meaning whatsoever.		*The infamous {{Tt\|-G}} suffix has no meaning whatsoever.
	*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.		*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.

	~~[[Category:AI(md).ini Sections]]~~
	~~[[Category:Maps Sections]]~~

en>DCoder: retracting defined vs declared... stupid code

2008-06-17T18:47:50Z

retracting defined vs declared... stupid code

← Older revision		Revision as of 20:47, 17 June 2008
Line 25:		Line 25:

	*This section is read from {{Ini\|ai}} and the current map file.		*This section is read from {{Ini\|ai}} and the current map file.
	* Unlike [[AITriggerTypes]], there is no known difference on where a TaskForce is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source ~~file. The TaskForce does have to be defined in the same file as it was declared, however, and cannot be overriden by redefining it in the latter~~ file.		* Unlike [[AITriggerTypes]], there is no known difference on where a TaskForce is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file.
	*The infamous {{Tt\|-G}} suffix has no meaning whatsoever.		*The infamous {{Tt\|-G}} suffix has no meaning whatsoever.
	*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.		*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.

en>DCoder: Creating

2008-06-17T16:38:29Z

Creating

New page

{{WrongTitle|[TaskForces]}}
{{SideBar|[[AI programming]]|Template:AI}}
In {{ts}} through {{yr}}, this section defines a list of all AI TaskForces in the game. A TaskForce is, like its name says, a group of units that gets recruited by the AI to perform a specific task. Each TaskForce listed in this section needs its own section in the file. In that section, up to six unittypes can be defined. Unlike most other object lists, the list containing the TaskForce's units does care about its ordering - it reads the lines indexed from 0 to 5 in ascending order. The game also reads a flag named {{TTL|Group}} from each such section. It is common practice to add flags like Name= for your own reference, which third party tools such as FinalAlert 2 or [[AI Editor V2]] usually can use as well.

== Format ==
[TaskForces]
0 = 0638CD41-G
1 = 0638CD42-G

[0638CD41-G]
Index = count,unittype
Index = count,unittype
Group = -1

[0638CD42-G]
Index = count,unittype
Index = count,unittype
Group = -2

Here, {{Tt|count}} stands for the amount of this unit to recruit, and {{Tt|unittype}} stands for the ID of the unit in question. [[AircraftTypes]], [[InfantryTypes]] and [[VehicleTypes]] are accepted here.

'''Note''' again: {{Tt|Index}} is read from {{Tt|0}} to {{Tt|5}} inclusive in ascending order, unlike other object lists which read the contained items without paying attention to the keys on the left side.

== Additional information ==

*This section is read from {{Ini|ai}} and the current map file.
* Unlike [[AITriggerTypes]], there is no known difference on where a TaskForce is declared, they are compiled into a single list after reading both files. The game does keep track of which ones were declared in the "global" scope (ai(md).ini) and which - in the "local" scope (map itself), but the only usage of that seems to be the unused functions to save them back to the source file. The TaskForce does have to be defined in the same file as it was declared, however, and cannot be overriden by redefining it in the latter file.
*The infamous {{Tt|-G}} suffix has no meaning whatsoever.
*There is an unknown effect attached to the hexadecimal prefix of a TaskForce's ID.

[[Category:AI(md).ini Sections]]
[[Category:Maps Sections]]