doMove move observations - feedback

[Mr.Peanut]

I've noticed some odd behaviour with the move and doMove commands. On a large map (Trinity) place in one corner a west inf unit named w1.  As far away as possible place an east inf unit named e1.
Close to w1 put a few empty objects and name them, say, o1,o2,o3 and o4.

1) The doMove command will override a previous move command, but the opposite is not true.

2) Both move and doMove may have distance limitations.
I was a west inf unit near w1 but not grouped.  In ECP Spec Debug if I type m1 doMove getpos e1 it works.  m1 sets off across the map. However, if I type e1 doMove getpos m1 or e1 doMove getpos o1 the eastern unit does not budge. Using the move fares no better.

Any comments or insights about this?

[macguba]

A distance limitation seems likely.   I've encountered it in other contexts, for example distances between waypoints with choppers.

doMove countermanding move but not the other way around is logical.    doMove is an individual command: you want a specific loon to go somewhere.    He is already, by definition, detached from his group.   So therefore it is right that, in general, if the group goes somewhere else he continues on his lone task.    I appreciate this doens't make sense if the loon is in a group of one.