AI ships not subject to range restrictions?

from GalCiv2 Forums


That Altarian ship and all the others around it for that matter (excluding the troop transports) is clearly excceding the 0.7 range figure listed in its stats. Sometimes my ships have been in this situation where they stop moving while in out-of-range-space, but I can't get them to do anything like attack other ships. These Altarian are attacking ships despite being out of range. They should have to sit completely still with no attack ability or move back into range.
8,809 views 10 replies
Reply #1 from Stardock Forums Top
Well, I am not sure about your screenshot: If I see it correctly, you have selected the altarian battleship. In that case, the range limit, as shown by the white line near the Torian influence zone is the range limit for the selected battleship. In that case the battleship is clearly in its range.

Don't forget that range limits is based on planets and starbase, and not on influence zone
Reply #2 from Stardock Forums Top
I have indeed selected the Altarian battleship, howerver...

Take a closer look at the map dude The Altarian space is all to the east and south of the camera. There are no Altarian owned bases or planets near to that battleship's location. You can clearly see this in the screenshot. If you can show me an Altarian base or planet within 0.7 of that ship's location I'll give you a cookie.

As to the grey range line... That is a bug, or maybe not. When you select a rival civ's unit on the main map, the range lines will adjust as if the unit were your own, taking into considering the placement of your own bases and colonies. The lines will not adjust to the rival civ's placement of colonies and bases.

Also note the minimap. The lighter purple area is supposed to represent the range of the selected unit. However for some reason one of my starbases (shown in the screenshot - middle right)
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top
Well, if the AI considers that one of your starbase extends its range, then you have definitely a bug. Have you send a copy of the savegame to [email protected] with this screenshot? They will be surely interested.
Reply #4 from Stardock Forums Top

Sounds like a bug.  That whole part of the AI has been rewritten though so hopefully that sort of thing won't happen.

In fact, last night I spent an hour trackign down a "bug" where the AI wasn't attacking this starbase near Earth.  Turned out the starbase was just a couple tiles outside the AI's range.

Reply #5 from GalCiv2 Forums Top

BTW, another thing in the new internal AI is the issue of whether the AI could even SEE your ship.  In your version of the AI, if the ship travels into explored space by the AI it "sees" the ship.  This was done based on 2003 specs (per player sensor scanning very CPU expensive so a heuristic algorithm was used that approximates the same sensor range).  Now literlaly the AI has to "see" your ship to go after it.

Reply #6 from Stardock Forums Top
Take a closer look at the map dude The Altarian space is all to the east and south of the camera.


And as was pointed out, cultural influence has nothing to do with it. Look at the minimap. The minimap shows SOMETHING in the current main map window is providing a base for range, though I can't find it. So the bug may be that a destroyed starbase is still being allowed to provide range, or something else that shouldn't be allowed to provide range is. Might be related to that time I saw a minor who's own home planet wasn't providing range for its colony ships, but something else was.

And here I thought this was going to be about the troop transports the Korx had in the early game in my current game with a range of 7.1 (!).
Reply #7 from Stardock Forums Top
I've seen that too, and constructors with a speed of 6 pc/wk.
Reply #8 from Stardock Forums Top
Might be related to that time I saw a minor who's own home planet wasn't providing range for its colony ships, but something else was



I can tell you what it is, in that specific instance: minor races, in the Beta5 version currently up, base their range off of another 'random' AI's planets. (Most likely it's not actually random, I just can't identify a pattern from what I see. I might be able to figure it out if I pulled up a good debugger, but I'm not going to try that, for several reasons.)

Major AI ranges are always correct, but minors usually aren't.
Reply #9 from Stardock Forums Top
Major AI ranges are always correct, but minors usually aren't.


Well that explains how in my last game (in a large galaxy) the Carinoids were able to colonize more planets than any two of the majors combined.
Reply #10 from Stardock Forums Top
As I understand it, the minor AIs are still a work in progress.