Kull
Posts: 2625
Joined: 7/3/2007 From: El Paso, TX Status: offline
|
This is an edited version of a post in the "Glug, glug, glug, in the Aleutians AAR" thread. In two recent cases, I saw a sub with 20 sys damage refuel in port and then return to Patrol while elsewhere a sub on Patrol took some pretty heavy damage from an ASW attack and also stayed on Patrol. I know these are issues involving subs (which is bad enough), but don't know for sure if the same problems affect surface vessels (although it seems likely, unless the issue of "damage awareness" is being altered by the Patrol Algorithm) Sending a sub out on Patrol with 20 sys damage is not a good idea, IMO, and if the AI is also doing this (which I'm certain it is), the long term effect on their naval asets is going to be quite detrimental. You can fix low levels of damage fairly quickly, but the larger it gets, the more likely it is to cause OTHER categories of damage that will take a lot longer to repair. And in the case of submarines, it will make them much more susceptible to ASW attacks. If the sub is ALREADY at 30+ damage, the number of hits required to sink it would only damage a healthier vessel. And why do I say "30+" damage? Well, take a look at this sub which survived an ASW assault three turns ago and yet still remains on Patrol! I don't know what level of Damage is considered to be "enough" to mandate a return to Port for repairs, but if surface vessels are also continuing to operate "normally" with damage of 37 sys and 32 float, that's going to give the human player an enormous advantage over the long term, since by definition those vessels can withstand much less punishment in combat. Initially the AI may have an advantage insofar as they'll have more operational assets early in the game (i.e the AI's ships are still out there "working" instead of repairing in port), but that is going to shift quickly and dramatically in the other direction. I would urge the Devs to take a harder look at the issue of "acceptable" operational damage.
|