Something I came along,
I can proof that the normal client AND the mirror client both have this issue.
If you use localwalker(object) and when a new region loads, the place of object gets moved along with the region.
Keepign the same localX and localY.
but ofcourse this isn't correct ... since the localwalker will walk to the localX, localY in the new region.
Hope you understand what I mean ;)
I'll make a detailed bug report soon.
Thx for keepign us posted.
Khaleesi