
When moving an article via MoveToLocation, the result seems to be always clamped to the gameplay plane, even if the target location is not. While this is probably a good thing in most cases to avoid accidents/headaches, maybe the modder explicitly wants the object to not be in the gameplay plane - for example, maybe an article is following a bone of its owner, which will almost certainly not be flush with gameplay at all times.
It would be much appreciated for MoveToLocation (and similar functions) to have an optional parameter something like “project2DPlane” that defaults to true, and when set to false the full 3D position is unlocked.

The newly-created #52 would cover the “follow an owner’s bone” use case.
