Issues with MoveToAction node and components

[agent-q1]

Investigating the move_to behavior node

When trying to use the move_to behavior node in TutorialPathfinding , there were a couple of issues I came across that led to unexpected behavior.

Related to Terasology/MetalRenegades#70

Scenario 1:

Once the entity was spawned, it would just stay still at the spawn location even when MoveToAction was being called and a CharacterMoveInputEvent was being sent. In this scenario, both the location component of the entity and the target field of the MinionMoveComponent would point to the right places, but the entity would just not move. The CharacterMoveInputEvent would have the right fields but the character would not move.

Scenario 2:

The spawned entity starts moving in the direction of the target block but fails to stop at the target position. It would continue moving in a straight line indefinitely. Sometimes, the location component would point to the initial spawn point and would not get updated but the target field of the MinionMoveComponent would point to the right place.

Scenario 3:

Some times, the target would point to the spawn position itself and the entity would remain stuck at that position thinking it had reached its final position even though it hadn't.