View Issue Details

IDProjectCategoryLast Update
0023589AI War 2SuggestionAug 29, 2020 4:18 pm
ReporterChthonic One Assigned ToChris_McElligottPark  
Status closedResolutionnot fixable 
Product Version2.127 Cranky AI Exceptions 
Summary0023589: Fire team AI Improvement
DescriptionThere's a series of algorithms I know and can put together that can help improve the AI of fire teams to avoid overwhelming force on the way to their target.

***This is incomplete*** I will flesh this out with the full response tomorrow when I'm better rested and I can fully explain and outline the algorithms to use.

Problem as suggested by Badger^3:
"If a fireteam is on a planet A. It wants to attack X, but Y is between A and X (so A -> Y -> X). Y has a lot of things that would kill the fireteam. Right now fireteams don't do a good job of taking the strength of Y into account when deciding whether to attack X"

This means that if a fire team decides to attack a target, it does not take into account what is in the way of it attacking, it simply charges through and likely gets killed.

Observation:
It would be better if the AI of Fire teams would pick a better route to it's target that avoids overwhelming force if possible, or returns no route if no feasible safe route is available.

Solution:
Form a strength map of the universe. (Should be somewhat easy, as it's already done)
Perform "All start all destinations shortest path length" search with path length being relative strength between player and AI. This is an X^3 search, but some optimizations can be made, for example, saving the search so it's only possibly done once every few seconds at most.
Take all paths to the destination judged to be "survivable" and determine shortest path to the destination if there are any. If there are not, the mission is a bust.
Finally, force the AI to take the path chosen, rather than taking the literal shortest path.

Outline of the algorithms mentioned above will be inserted here later:
TagsNo tags attached.

Activities

BadgerBadger

Aug 27, 2020 10:54 am

manager   ~0058198

I would recommend looking through the code before trying to figure out what improvements might be made.

Issue History

Date Modified Username Field Change
Aug 27, 2020 3:50 am Chthonic One New Issue
Aug 27, 2020 10:54 am BadgerBadger Note Added: 0058198
Aug 29, 2020 4:18 pm Chris_McElligottPark Assigned To => Chris_McElligottPark
Aug 29, 2020 4:18 pm Chris_McElligottPark Status new => closed
Aug 29, 2020 4:18 pm Chris_McElligottPark Resolution open => not fixable