1.2 bug report : upgrading mini freighters

from GalCiv2 Forums
Well, it isn't the first time I have spotted this : The upgrade of mini-freighter (that are in a trade route) doesn't seems to work correctly: you are able to upgrade them if you plan to upgrade all freighter of this class. You are correctly charged for this, but your mini freighters don't seem to be changed to the upgraded version. It looks like the mini-freighters are counted when determineing the number of ship in a specific class but upgrade is disabled for them since there are always moving. Do anybody has seen the same behavior?
8,748 views 5 replies
Reply #2 from GalCiv2 Forums Top
Mini freighters will always have a movement of 1. They are symbols for the trade route and act as targets. They are not manuevaerable ships. Did they ever have more than 1 defense point?
WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from GalCiv2 Forums Top
The implementation could be better though. I often have a half dozenish designs cluttering up my shipyard by tyhe end of the game as newer faster ships are built with higher trade levels or to replace ones destroyed as a result of combat. Since cargo and large hull types can be cross upgraded the clutter increases the risk of a fatfinger accident misupgrading battleships into trashhaulers.
Reply #4 from GalCiv2 Forums Top
Mini freighters will always have a movement of 1.

Sure. But being able to upgrade them with some offense and defense could be useful
But if they aren't subject to be upgrade (which is possible), they shouldn't be taken in account when upgrading a whole class of ships.
Reply #5 from GalCiv2 Forums Top
I've noticed that in the 1.2 Beta, that if you obsolete the original freighter (or whatever freighter you created trade routes with, and choose to decommission any current ships of the same design, then the mini-freighter counts as 1 and though you get the decommission payment, it also disbands the trade route itself, which is silly IMHO.

Not sure if this was fixed in 1.2 final though.