An AI stack I just spotted in my game leads me to believe that UNIT_IMMIGRANT is seriously hurting the AI once it gets access to them.
For some reason they have a default AI of UNITAI_CITY_SPECIAL (which is fine), BUT also list UNITAI_SETTLE as a supported AI. The net result is that the AI is building them to satisfy requests for UNITAI_SETTLE, and then treating them like settlers...with the fatal flaw that when they get to the place they want to found a city...they can't found cities!
I suspect this is preventing the AI creating any new cities once it gets access to immigrants. As far as I can see having UNITAI_SETTLE on them I not really serving any purpose - just removing this and leaving them with their default AI (UNITAI_CITY_SPECIAL) should resolve the issue.
@DH - is there some special reason they have UNITAI_SETTLE on them?
For some reason they have a default AI of UNITAI_CITY_SPECIAL (which is fine), BUT also list UNITAI_SETTLE as a supported AI. The net result is that the AI is building them to satisfy requests for UNITAI_SETTLE, and then treating them like settlers...with the fatal flaw that when they get to the place they want to found a city...they can't found cities!
I suspect this is preventing the AI creating any new cities once it gets access to immigrants. As far as I can see having UNITAI_SETTLE on them I not really serving any purpose - just removing this and leaving them with their default AI (UNITAI_CITY_SPECIAL) should resolve the issue.
@DH - is there some special reason they have UNITAI_SETTLE on them?