Is there a reason we still use MoveTo in the fighter script instead of StartMoveAction? wouldn’t this make the CancelCurrentAction in the Cinematic Control Disabler work as inteaded and not need to put Mover cancel in the Fighter Cancel?
If we use StartMoveAction() in the Fighter script, then Mover will declare itself to be the current action, and Fighter will automatically Cancel, clearing the target.
I thought that too but tested and still worked, I think it still works because as soon as the enemy gets in range of the player it breaks the Agro threshold and retargets again.
Try clicking on an enemy and then taking your hand off of the mouse. I think you’ll find that the player goes where you clicked on the enemy, and then will stand there and let the enemy pummel him. This is because the Player’s fighter will no longer have a target to attack when StartMoveAction is called on Mover.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.