Better definition of base defense perimeter

Currently the AI is not protecting it's base properly. We are currently working with some range circle around start point which is not sufficient. On mountain trail for example the three nearest points to a base are outside this circle and the AI won't defend them.

Result : AI happily attacks deep in enemy territory while ALL its points are taken and just returns when enemy enters base defense circle. Too late, gg.

I already reintroduced IsBaseBeingAttacked() for DoWpro. If a point near startpoint is threatened by sufficient force it will trigger defense mode immediatly. Since Arkhan is recoding most of my ideas to his likings I don't post my changes and wait for his solution.

Edited by LarkinVB, 13 May 2006 - 10:59 AM.

Currently the AI is not protecting it's base properly. We are currently working with some range circle around start point which is not sufficient. On mountain trail for example the three nearest points to a base are outside this circle and the AI won't defend them.

Result : AI happily attacks deep in enemy territory while ALL its points are taken and just returns when enemy enters base defense circle. Too late, gg.

Valid point! Seems like the home radius should be also dependent on the distance of a min count of LPs around it. I'll try something for the next beta...

Or can't the function take into account the nearest listening points as part of their base? usually they are anyway - and so the function with the "radius around start point" could be "radius around start point + some smaller raduis' around the nearest LP's"

I know no one here likes using the buggy Relic functions that is...

I just use a modified IsBaseBeingAttacked() of bases near start position, sort them by priority and use them as defense trigger. It does work fine. Using this will even protect allied buildings in my base.
Arkhan shows great displeasure with this function.
I do not agree, it's usefull for me.

Edited by LarkinVB, 15 May 2006 - 06:15 AM.