Hey,
You have access to the complete engine code. Or you can simply override whatever class implements the problem behavior, and implement your own.
Implement your own Movement component, or your own PathFollowingComponent, and just… do it. Or find where in the engine code it sets vel to 0, and remove that. Although then you’ll complain that Velocity is in the wrong direction, I suspect.
Please don’t argue emotionally. It add nothing to the discussion.
I create tool (plugin for marketplace) and cannot modify engine for my plugin needs (Epic does not allow).
As I told before: I can write the whole MovementComponent. Write several thousand lines of code. Or ask epic to change few lines of code.
The next thing is compatibility with other parts of engine. With my own movement component will be a problem. My main direction in plugin development is to achieve maximum compatibility with current tool - because my tool extend engine should extend functionality - not to replace them.
eblade if you do not have anything constructive to say, please don’t insult me and tell me to program everything myself because I might as well create my projects in pure assembler.
I know there is possibility to write by myself Movement Component, but for me is NOT a good solution.