So, yeah, this is a fun bug and could probably stand to be reported properly. From what I remember, moving an object works the same way as placing a new one: you have a silhouette that you’re trying to place, and the code is checking if you’re allowed to place it there.

Unfortunately, the implementation is a little too lazy: for objects with special restrictions, the original that you’re trying to move still counts as being in the world. For example, when you’re trying to move a thrall, the game won’t let you place it “too close” to its original position, because it acts as if you’re placing a new thrall and counts the original as “too close”.

I believe the same thing is happening in this case, which is weird, because Funcom usually doesn’t let you move placeables that have restrictions like that (e.g. altars), but maybe they relaxed that since I stopped playing or maybe they missed something.

At any rate, that behavior is technically a bug, but usually not a big deal. Here, however, it’s coupled with the restrictions on how far you can move a placeable, which makes it much more annoying.

3 Likes