Sep 3 2011, 5:55 pm
I've been tinkering with the pixel movement system for a couple of hours now, and my only true issue with it seems to be the lack of a simple method to move an object an awkward amount of pixels in the x and y directions. step() is lacking because of its focus on the 8 major directions; taking 2 steps (one for x and one for y) can cause problems if you're not using a fairly high framerate, and even then, it only reduces the rate at which they occur (for example, if you're step()ing horizontally before vertically, you may bump an object to the west of you, rather than the object to the northwest). Using Move() is also fairly annoying because it involves handling a couple of different turf and position checks that one would expect to be handled internally.
Copyright © 2015 BYOND Software. All rights reserved.