Yes indeed it is just a Warning for this case, but in other cases that Velocity actually gets in the way and needs workarounds. And I also like my Projects as Warning-free as possible! 
So a huge thanks once again for adding it to your list, it will help me and my OCD a lot 
However today I stumbled across a nastier bug: The entire Engine crashes when trying to cancel a passive Ability.
Here’s how to recreate the bug step-by-step from a new Project (with Engine v4.16.3, Able v1.70):
- Create a new Project. I’ll be creating a 3rd Person Blueprint Project but it should happen on any kind of project really.
- Enable Able Plugin and add an Ability Component to the Player Character (in my case: “ThirdPersonCharacter”).
- Make an Able Ability:
- Length 0.7s.
- 1 Task which is “Play Animation” and just choose the “ThirdPersonJump_Loop”.
- Finally activate “Is Looping” and set the Loop End to 0.7s.
- Add 2 Action Mappings to your Project: “ActivateAbility” and “CancelAbility”. I bound them to Keyboard 1 and 2.
- Set up your Action Mappings in your Player Character Blueprint to Activate / Cancel the Ability you created like so: https://puu.sh/xrIhB/fbc81d5f5c.png
- Go try your Setup. When pressing 1 your Character should start the Animation and loop it infinitely. When pressing 2 it cancels the whole thing as it should.
- Now go back to your Ability and enable “Is Passive” and hit “Play” again. The Engine will crash when pressing 2 so make sure you saved beforehand.
This not only occurs with the Ability having an Animation Task which is possibly not meant for passive Abilities. I encountered this with an Ability that only had a Particle Effect to play. Also, it even happens when removing the “Play Animation” Task (so even when the Ability does not have a single Task).
Edit: Forgot to include a Screenshot of the Crash so here it is 
https://puu.sh/xrJcN/b6ac1f33a4.png
