I found that the issue was to do with the stopAttack trigger, but instead I reset the trigger after we set it in the Cancel() method, as I figured that this is when we would be finished with the stopAttack trigger. It seems to do the trick, although I will change it to match Rick’s solution in case there are other things in future that may rely on the code being in those specific places.
My personal preference is always just before setting the trigger. This guarantees that whenever you call it, it will fire.
1 Like
That approach makes perfect sense, I’ll bear that in mind in the future, thanks Brian!