Exavier Macbeth at GpG BlackOps forum...
Basically the way the AI works in the game is that there are two things that are needed to make it work.
There is the core AI coding that deals mostly with timing & stratagy. This was what Sorian originally started modding and a few others as well. Very few coders however would touch this because its almost as badly coded as several of the UI commands. Its also why AI mods are overwrite mods rather than Mod Manager Mods.
There is the build template files that control all the platoon, Upgrade, and build order information used by the AI. These files are huge but its what I had to hook to get the AI to build the BO:ACUs upgrades. Before sorian came along the only way to get custom units to be built would be to add your unit into this file and modify the hundreads of groupings... The downside is that alot of time mods would overwrite eachothers changes.
When sorian created his AI mods he added in calls that looked for a custom unit template within the mod folders. This way we modders just have to build a template file for our mods and his code would handle the integration/hooking. From what it sounds like this is where FAF is having issues because if those calls got broke then none of our custom units will be loaded. Especially since this template file is automatically ignored by the game unless something specifically calls it. It is also the only true "AI Support" that any Blackops project (and most unit projects) offer.
Also for the record... When we set up the templates for Blackops we purposefully left specific units out of the templates because they featured more complex functionality to use than the AI can understand. Hydrocarbons are one of the things that fall under this because we didn't want to write a 2nd upgrade hook like I did for BO:ACUs (was a pain in the butt).
---
Basically you might want to relay that information to the FAF team so they can look at their implementation of Sorians Mod. From my understanding FAF was suppose to be GPGnet on steroids and allow them to make any mod or component plug & play. Chances are when they converted the Sorian AI over to their system they broike a linkage in one of the scripts. He does have alot of things hard coded in his code which is why BO:ACU still has slightly twitchy commander usage by the AI (He tries to force build an upgrade that doesn't exist on my commanders)... But things like file lookup paths would probobly need to be corrected if FAF is not running sorians files from the proper installation area.
Hope it helps. Unfortunatly going through another modders code is a pain in the butt at the best of times just due to coding & thought process differences. Especially for areas we don't normally play with. Most of us who are still arround don't have the time or skill to make the corrections properly. And I haven't looked at FAF closely enough to have a starting point on what needs to changed if I had the time
@aeoncleanse: Here you go. Will poke hawk about the main links.
ZIP:
http://www.hyperimpact.net/downloads/Bl ... v52zip.zip
SCD:
http://www.hyperimpact.net/downloads/Bl ... v52scd.zip