Auto-Colonize ignores immediate threats.

from Sins Forums
This is I'm sure another well documented item, but regarding the Auto-Cast Colonization ability, the colonizer in question seems to prioritize colonization over being shot at.

In an engagement of a few light frigates, my battleship would take one down with ease, then immediately start steaming forwards for the colonizable planet regardless of the wash of firey-hot-death spitting from the remaining frigates.

Manually targetted the next, dispatched it, then AGAIN the fate of this new planet outweighs the immediate pummelling from the remaining frigates. Rinse, wash, repeat. I'd prefer not to have to take Auto-Colonize off when I'm going into a known combat operation. I had hoped that the AI dealing with any lethal force would take precedence compared to more strategic goals when Auto-Cast Colonization is enabled.

Thoughts?

3,149 views 7 replies
Reply #1 from Sins Forums Top
Yeah, I noticed that when I was playing. My ship just flew in to colonize, I had to tell it to fight each ship individually. Auto Colonize should be a secondary thing, attack should be first.
Reply #2 from Sins Forums Top
agreed... Auto colonize should be postponed at least until all enemy ships that can harm the colony are destroyed. if you've got nothing left but some little ships that can't attack planets, then fine... colonize away... but doing it when the system is full of siege units etc is silly.
SoundPackager - Customize the Windows sound scheme
Reply #3 from Sins Forums Top
Agreed here as well. I have a similar problem with the siege frigate's diving right in to bomb a hostile planet with total disregard to enemy forces in the area. I know they aren't designed for fighting but as it is they charge past their protective fleet (who stop to shoot at stuff) right into the enemies defenses. This, along with the enemy AI prioritizing them as targets, tends to get them killed rather quickly. I'd prefer that they be a little more hesitant to charge in and auto-bomb the planet.
Reply #4 from Sins Forums Top
Yeah, I noticed that when I was playing. My ship just flew in to colonize, I had to tell it to fight each ship individually. Auto Colonize should be a secondary thing, attack should be first.


Why not do what players online do , and send your forces in first THEN send your colony frigate in when its safe to do so.

And you did not just say colony frigates should be fighting rather then colonising right?   
Reply #5 from Sins Forums Top
Not the colny ship; the colonising capital ship shares the same behaviour.
Reply #6 from Sins Forums Top

Yeah, I noticed that when I was playing. My ship just flew in to colonize, I had to tell it to fight each ship individually. Auto Colonize should be a secondary thing, attack should be first.


Why not do what players online do , and send your forces in first THEN send your colony frigate in when its safe to do so.

And you did not just say colony frigates should be fighting rather then colonising right?   


He's probably talking about the Akkan with colonize set on autocast.

As an advice, first thing you need to do with every capital ship is to disable autocast on all abilities. Those scripts just suck.
Reply #7 from Sins Forums Top


Yeah, I noticed that when I was playing. My ship just flew in to colonize, I had to tell it to fight each ship individually. Auto Colonize should be a secondary thing, attack should be first.


Why not do what players online do , and send your forces in first THEN send your colony frigate in when its safe to do so.

And you did not just say colony frigates should be fighting rather then colonising right?   


He's probably talking about the Akkan with colonize set on autocast.

As an advice, first thing you need to do with every capital ship is to disable autocast on all abilities. Those scripts just suck.


Ah I see , hmmm. Yea I tend to switch off the autocast for the Akkan. I know that whenever I need something colonising , ill BE THERE to do it , so offcourse I dont need this been automatic for me.