I'll take a look at it. But keep in mind that the moving is used as movement route so naturally when you change the page, it's gone.
EDIT: Fixed it. Nvm about the page changing, the character should still continue on its path because either way with dyn_request the path is recalculated after every step.
EDIT: Actually wait, dyn_find seems broken.
EDIT: Alright, I fixed it all. One of the problems was caused by the recent "fix" due to passability, but now it doesn't work in the opposite scenario when you want to get closer to a non-passable position so I have included an optional parameter after RANGE to determine whether the next neighbor has to be passable or not when using RANGE.