Pixel Movement

After having an issue with moving an obj in runtime (See: http://www.byond.com/forum/?post=1059248), I would like to formally suggest that if a new version of the Pixel Movement library is ever released, that it changes all the movement related procs from mob-only procs to atom/movable procs.

Any mob-exclusive calls could always be done in an overridden version. The problem is that because there's no proc for it, when moving something like objs the programmer might be trying to modify only a few of the required variables (Like I was), resulting in issues. In the end, the result to solve the issue was to just copy set_pos() for objs, which is silly, especially because from what I can tell, mob and obj set_pos() are exactly the same proc, so there's no reason it cannot be an atom proc.