The Civ4SpecialUnitInfos file defines various properties for unit groups that are carried by other units such as fighters, great people, and missiles; it is referred to by the <SpecialCargo> tag from Civ4UnitInfos.
All tags must be opened and closed; the first is the "open", the second the "close" tag. If nothing goes inside a "list tag", then it should just be the opening tag with a "/" before the closing bracket. The following tables contain all available tags, as well as their purpose and accepted values.
These tags typically bracket other tags, sometimes the entire file, and are generally used to specify more than one piece of data.
|Civ4SpecialUnitInfos||This begins and ends the file. Everything must go in between these two, or it will not work.|
|SpecialUnitInfo||Each different unit type's data is enclosed in a separate tag like this.|
|Type||The name of the unit; which must be unique.|
|Description||The TXT_KEY that is displayed as the name of the carried unit; ex. "Carries Fighters" means the TXT_KEY is the word "Fighters".|
All of these can either be 1 (on, or true) or 0 (off, or false). Be careful, as you can wind up with a double-negative, which the game will interpret as "True".
|bCityLoad||If 1, the unit cannot directly rebase to a valid carrier-unit; rather it must be loaded onto carrier-units when both units are in the same city.
Used in vanilla Civ4 for missile units.
All List tags consist of an opening/closing tag, which is shown here, and then each entry within it is another tag with the same name as the parent tag, minus the "s" (i.e. singular, rather than plural).
|CarrierUnitAIs||List containing CarrierUnitAI tags.|
|CarrierUnitAI||A UNITAI definition that determines how a unit carrying this unit will behave when controlled by the AI.|
|ProductionTraits||Traits which impact on the speed at which this unit is produced.|
In the following example of code, please note that there is a specific order of all of the tags. You must list the tags in this order for the game to properly interpret your file.
<SpecialUnitInfos> <SpecialUnitInfo> <Type>SPECIALUNIT_FIGHTER</Type> <Description>TXT_KEY_SPECIALUNIT_FIGHTER</Description> <bValid>1</bValid> <bCityLoad>0</bCityLoad> <CarrierUnitAIs> <CarrierUnitAI> <UnitAIType>UNITAI_CARRIER_SEA</UnitAIType> <bUnitAI>1</bUnitAI> </CarrierUnitAI> </CarrierUnitAIs> <ProductionTraits/> </SpecialUnitInfo> </SpecialUnitInfos>