Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks for the questions. = )
The newer naming scheme for AIP files is: [AIPName][CPURace]_[AIPType]
so, for instance: instead of having both BT_difficult_ff1.aip and BT_difficult_fi1.aip, you'd only have: BT_difficult_f_1.aip
This also means that if you decide to add races (Or someone else's mod adds races and wants to use your map pack), your AIPs will work against those added races without problem. (assuming they use the proper provideName entries in their ODFs)
[NormalView]
DiffuseColor = "255 255 255"
SpecularColor = "10 10 10"
SpecularPower = 1024.0
Most noticeable difference is the Specular texture's effect.
Ive created one IA map and released on Steam.
My understanding is that maps do have to be created as MODs.
Add-ons are more for things like custom UI skins, cross hairs and functions which can be used at the same time as the maps/mods.
However, theres something that has to be done with the folder structure to ensure that IA and MPI versions are created (in the mod).
Probably worth asking Aegeis, he helped me out.
This was produced as a Mod and not at asset, so I am sure that has something to do with it.
Over time, I will work on that.