Sprint and drift - hard coding the only option?

[MarkShot]

Well, thanks.

I suppose if I do any serious scenario development, I will do it for DW, since most of the community has moved on.

That certainly should make the escort problem much easier to manage and if I can do zig and a zag with every other drift to clear baffles that should work very well.

Now, since this is during a TRANSIT SEARCH, once the AI detects a contact will it forgo any further sprinting and prosecute the contact until it is confirmed safe?

[To be]

Originally Posted by MarkShot

Well, thanks.

I suppose if I do any serious scenario development, I will do it for DW, since most of the community has moved on.

That certainly should make the escort problem much easier to manage and if I can do zig and a zag with every other drift to clear baffles that should work very well.

Now, since this is during a TRANSIT SEARCH, once the AI detects a contact will it forgo any further sprinting and prosecute the contact until it is confirmed safe?

Once the sub detects something, it takes over, and will ignore the speed settings until it loses the contact or kills it. (with LWAMI at least)

[MarkShot]

If I go with DW instead of SC so that I can write scripts. Then, can I use anything from doctrine language in those scripts?

So, could I also make my script to retrieve the base course for the PIM (current leg). And then say randomly between 8-15 minutes and randomly for 10-30 degrees zig-zag? (Since I see that there a lots of good doctrine coding examples which I can utlize in the doctrine directory for SC/SCX/DW/LWAMI.)

Thanks.