View Issue Details

IDProjectCategoryLast Update
0019296AI War 2[All Projects] Gameplay IssueNov 17, 2017 7:34 pm
ReporterBadgerBadgerAssigned Tokeith.lamothe 
Status resolvedResolutionfixed 
Product Version0.604 
Fixed in Version0.607 
Summary0019296: Threat taking inefficient path on retreat
DescriptionThere's a gameplay issue with the Retreat code in LongRangePlanning for the Threat Fleet. When it's choosing to retreat from a planet due to suddenly arrived human reinforcements, it seems to choose an AI planet at random to retreat to. In one example caused the Threat fleet to walk right past my arrived reinforcements and all die, instead of flying directly away from my reinforcements to a wormhole to a different AI planet. I think this code needs to be aware of where the forces on the planet are (or at least privilege the closest wormhole to retreat to, if figuring out where the human forces are in relation to the AI ships is too much effort for now).
TagsNo tags attached.



Nov 17, 2017 7:34 pm

administrator   ~0046606

For 0.607:

* Rewrote the logic for selecting which planet an AI threat force retreats to; previously it was just a mode of the "send threat on raid" logic, which prioritized the ease of being at the destination over the ease of getting there.
** Now it broadly prefers neighbors with a favorable ratio of friendly forces to hostile forces.
** And other than that, it picks the wormhole closest to the average center of the AI force.
*** This means that some ships will likely bypass easier escape routes, but it's better to take the risk of higher losses in exchange for avoiding the certainty of a divided force that can be more easily defeated in detail later.
*** Note that this is all in external logic, so if a modder wants to make an AI type whose ships always retreat to the nearest wormhole, that's quite doable.

Issue History

Date Modified Username Field Change
Nov 15, 2017 12:08 am BadgerBadger New Issue
Nov 17, 2017 7:34 pm keith.lamothe Assigned To => keith.lamothe
Nov 17, 2017 7:34 pm keith.lamothe Status new => resolved
Nov 17, 2017 7:34 pm keith.lamothe Resolution open => fixed
Nov 17, 2017 7:34 pm keith.lamothe Fixed in Version => 0.607
Nov 17, 2017 7:34 pm keith.lamothe Note Added: 0046606