Scripts

Mapping

Registers ordered team-mission lists containing up to fifty mission and argument pairs.

Format

Kind

Record

File

AI.INI, AIFS.INI, map file

Registered in

[ScriptTypes]

Section

[<Script ID>]

Record form

<slot>=<mission>,<argument>

Fields

#	Field	Accepted value	Required
1	Mission	Team mission index	Yes
2	Argument	Integer interpreted by the selected mission	Yes

[ScriptTypes] values name the Script sections to load. Each Script section accepts numbered mission lines 0 through 49.

OpenTS loads AI.INI, then AIFS.INI when Firestorm is enabled, then the map-local definitions.

AI.INI, AIFS.INI, or map file

[ScriptTypes]
0=MyAttackScript

[MyAttackScript]
Name=Attack nearest target
0=0,0

Lines load in slot order and pack together, so gaps in the numbered slots collapse. The selected team mission defines the meaning of its argument.

Accepted settings

Filter settings

1 of 1

Key	Description	Value	When omitted
Name[<ObjectType ID>]	The display name of a type definition, a scenario, a multiplayer map, or a musical score.	string	Computed

Related resources

• Attack...Team script mission
• Team executionFeature or system
• AI triggers and team productionFeature or system
• Change script...Team script mission

Source files

Linked at revision 59fae722af8c.

• code/script.cpp
• code/tmission.cpp
• code/init.cpp
• code/scenario.cpp

Page feedback

Report an error or missing detail. The issue includes this page and revision.

Open issueSource revision 59fae722af8c