Follow/Leader

[Avenger]

Leader(Point) - Works more or less like MoveToPoint(Point) - actually uses the latter internally

 

Follow(Point) - Works more or less like MoveToPointNoRecticle(Point) - uses the latter internally.

An additional restriction seems to be that the actor needs to be also selected (which pretty much restricts it to a controllable party member).

[devSin]

I think I posted about these years ago. They roughly work according to the follow formation type in terms of how the actors are moved IIRC. Functionally useless.

 

EDIT: That is to say, it's MoveToPointNoReticle() to the point calculated by the Follow algorithm, not P:Point (P:Point should be the PC in front of you). Leader() doesn't matter because it's just right where you click anyway (with the formation). Or something (maybe it was that if you pass in the same point to both, it lines everybody up correctly, but when used singly, it's undefined? I don't remember).

[Avenger]

I didn't recognize any formation

The only useful difference is that these are not blocking.

I implemented them by stuffing a MoveToPoint[NoRecticle] action on the queue's end.

As far as i understood the original does the same.

So:

Leader( [x.y])
SetGlobal("var","global",1)

Will set the variable, while

MoveToPoint([x.y])
SetGlobal("var","global",1)

May not.

 

But i admittedly didn't understand the code in depth

[devSin]

It should work the way I say. Make sure to pass the same point into Leader() and to pass multiple people to the same point but with Follow(). They should line up IIRC (unlike MoveToPoint(), they won't fight for the same point but will line up spaced nicely according to the Follow formation algorithm).

 

If you can find the old posts, I should have detailed any limitations (or not; nobody cares), but I know that I looked at it and determined how to make it work correctly (e.g., as the script interface to Follow formation).

[Avenger]

It should work the way I say. Make sure to pass the same point into Leader() and to pass multiple people to the same point but with Follow(). They should line up IIRC (unlike MoveToPoint(), they won't fight for the same point but will line up spaced nicely according to the Follow formation algorithm).

 

If you can find the old posts, I should have detailed any limitations (or not; nobody cares), but I know that I looked at it and determined how to make it work correctly (e.g., as the script interface to Follow formation).

 

Yeah, that was my point (hehe, pun not intended), they fought for the same point in my test. (Same destination at least, during walk, they lined up, maybe i should test this with other formations).

[devSin]

Fine, fine. I performed the search for you. :-)

 

Since I was so explicit there, this probably isn't anything I'll ever look into again. It wasn't ever used, so I think you can get away with whatever you want in GemRB.

[Avenger]

Umm yeah

The 'something' Follow appears to do is MoveToPointNoRecticle.

 

The difference in Leader and MoveToPoint is that the Leader constructs a MoveToPoint action, pushes it on the queue, then finishes (not blocking action).

The difference in Follow and MoveToPointNoRecticle is that it creates the MoveToPointNoRecticle action if the actor is selected. (And yeah, at this point, the selection could be used to modify the target point, based on the preset formation).

All in all, the selection requirement makes Follow unreliable.

That was the point of my note

 

Also, you don't have to use Leader before a Follow.

[devSin]

And the point of my note was that the moves are performed in accordance with the Follow formation if you call them correctly. Which is the whole point of those actions.