I approve, very annoying issue
The object gets loaded at the right local x and y values, but in the wrong region.
I have reported this 2 months ago while the localwalker was walking to wrong locations...
This bug happend in 95% cases while using localwalker to a certain position.
In emantime the client loads a new region, but the localwalker will walk to the wrong region (due the fact the object has been loaded in the wrong region in the first place
Khaleesi