Quote:
|
Originally Posted by OKO
as I told you sooner in this thread => why going from track to avoid ? (track is to force an AI to follow an ALREADY DETECTED other platform)
There is no need at all to do that.
|
I thought the point was to have said AI platform detect and follow the human player first - THEN the ping and avoidance.
(What keeps a player from starting the mission with a ping, btw?)
I think however that this is one of the many limitations we do face in the mission editor. The best we can do is use a script to assign it a course which will, in theory, lead it away from the player sub.
I believe the only way to achieve this is to modify the doctrine files - but that's not something I recommend. (It would be anidea to allow us to include a custom doctrine file for some platforms in a mission, overriding the default doctrine. However, then improvements in the 'base' script would not apply to that platform in that mission.)