ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
Ai.ini
From ModEnc
Revision as of 13:17, 22 July 2008 by Dutchygamer (talk | contribs) (→Tips: I've seen the AI deploy Siege Choppers in several games. It is very rare, I must admit though. For the sake of truthness I added it. Undo if you think it ain't necisary to tell...)
This INI file contains the AI unit controls - it specifies what units the AI should use, when, and how. It does not control AI structure placement.
File locations
- TS version is in tibsun.mix -> local.mix, the patches add a different version to patch.mix.
- FS version (named aifs.ini) is in expand01.mix. (This mix file also contains ai.ini, which introduces the generic gameplay changes to plain TS as well.)
- RA2 version is in ra2.mix -> local.mix.
- YR version (named aimd.ini) is in ra2md.mix -> localmd.mix.
Tips
- AI wont deploy the Siege Chopper.
If you want to make the AI use it, you must make it fire from air and use normal attacking script. In very rare cases the AI does deploy the Siege Chopper, but this is only their Warfactory. - If you have a transport in your TaskForce, you can have ONLY 1 with transporting scripts.
If you have more, the AI will get stuck with it. Also, other units must exactly fit to the transport, so:0 = 1 , HTK 1 = 4 , IVAN -or 6
doesnt work, but 5 does as [IVAN] has Template:TTL and [HTK] has Template:TTL
You can have max of 2 transports by using TeamType 2 in the trigger.
- If you use both teamtypes 1+2 to double your TaskForce, check the Template:TTL of them if AI builds only one.
