Units keep moving towards skipped order if there are no further orders in queue

[glass plover]

We somewhat recently got "skip next order" added to gridkeys keyset (default key N).

If a unit only has 1 order, and you skip that order, the unit will keep going towards the waypoint of that order until it reaches it.

Expected behavior would be for the unit to stop when it does not have any orders.

I guess there needs to be a check for any further orders when a "skip next order" command is issued, and if there are no further orders, stop the unit.

For testing purposes, I tried setting a unit to hold fire and fight-moved it towards an enemy unit. Skipping the order made my unit ignore the enemy unit, so the fight-move was successfully cancelled, however my unit kept moving towards its former waypoint.

[craggy basin]

Engine level issue.

When a command can be issued, if needed a "move goal" is set by the engine, and the unit starts moving towards that goal location.

Canceling the command does not always cancel the "move goal" that was set by that command.

A similar kind of error also happens when you give an attack command, and the target dies before you get in range, so you walk up to the corpse of the target instead of stopping when the corpse is in range of your weapon.