Our design normally allows for that, by implementing an IPlayerMover interface and casting the skill at the positions passed to your MoveTowards implementation. Then, you can set the PlayerMover field in Navigator.
However, since we had to just change Input stuff, this won't work as expected for you, because a non-overridable BasicPlayerMover is currently being used in MoveToCoroutine. Anywhere that is used in the bot, would not use your own mover, which right now, is everywhere but movement called from the CR.
There's a lot of design changes we need to do now to get the bot back to supporting such customization again, but for now, that's how it's currently setup.
