[IPAndrews]

At this point about half of the people here will be saying to themselves "So what?". Sound like an easy thing to do? it ain't. This is how I did it. I made a friendly cruiser called "Target". Told the capship to chase down "Target". Created an every-time event which calculated the differences in X,Y, and Z, co-ordinates between the capship and Alpha 1. Imagine it as the length in X,Y and Z the capship would need to travel to get to Alpha 1. The every-time event then added those lengths to the current X,Y, and Z co-ords of alpha 1 and positioned the target cruiser there. Essentially putting the target cruiser behind Alpha 1. Oh I multiplied up all the lengths by 10,000 as well. So that the target cruiser would be a long way away.

End result, cruiser is always headed for a target which from it's pespective is behind Alpha 1. ie: the capship ends up headed straight at Alpha 1.    Oh yes. Let the bullying of much smaller ships commence. 

[Colonol Dekker]

Strange and intruiging, Two thumbs up 

[NGTM-1R]

I kinda wanted to do this for a campaign once, something along the lines of "They really don't like you, Alpha 1."

[Prophet]

There's math involved, isn't there? I always just shut down and start drooling like an imbecil when there's math involved. So I have no idea how you did it.

Sounds cool though

[Black Wolf]

Clever, but using these tablesYou could just have given the cruiser Chase Alpha 1 orders.

[Shade]

From the description, it looks to me more like "follow Alpha 1" than "chase Alpha 1". Chase has always been fairly simple, as the attack/ai-chase AI goal for capships is already allowed to take fighters as an argument. Follow, though... now that will be exquisitely useful, opens up a lot of options for mission design. Very good work coming up with this

Would you mind if I add this to the FRED Examples section of the wiki? It's certainly clever enough to warrant being there.

[Black Wolf]

Oh... follow.

Erm, wouldn't it be simpler to use every-time and the set-object-position sexp to put a waypoint at get-position-x/y/z for Alpha 1, then give the capship waypoint-once orders? If it got too close you could clear its orders, and then trigger the waypoint order again when the player got further away.

[IPAndrews]

Clever, but using these tables you could just have given the cruiser Chase Alpha 1 orders.

Haven't tried that feature yet. Would be lovely to assign a chase Alpha 1 order to a capship in see it actually move in the direction of Alpha 1, rather than just sitting there like a lemon. I didn't want to override the default tables in this case though. Since it's just for a campaign.

[IPAndrews]

wouldn't it be simpler to use every-time and the set-object-position sexp to put a waypoint at get-position-x/y/z for Alpha 1.

Didn't work. The waypoint move seemed to work the first time but not subsequent times.

[karajorma]

Didn't work. The waypoint move seemed to work the first time but not subsequent times.

Moving a waypoint more than once may not work properly. I remember trying to use a moving waypoint in a cutscene and having it crap out on me very quickly. Since I was only moving it very slowly I never bothered to investigate whether it had worked the first time or simply not worked at all.

I'll take a look at the issue if I get a chance though cause this is something I want to see working. (It's more likely to get done if someone sticks it in Mantis though *subtle hint*).

[IPAndrews]

(It's more likely to get done if someone sticks it in Mantis though *subtle hint*).

Oh okay then. Since it's you asking and I owe you.

[PotzUK]

Can you show us what the Event tree looks like? 

[Goober5000]

I thought I responded to this back when it was first posted.

Anyway, waypoints were never movable before now, and part of the game still thinks they're unmovable.  Including the path system:  the AI only computes the waypoint path when it first starts following the waypoints.

I'm not sure what it would take to make the path continuously update.  In the meantime, what you might be able to do is repeatedly do clear-goals and ai-waypoints-once so it's forced to keep recomputing the path.