Special thanks goes out to Lige and Fugsnarf, who both have reported minor bugs in the demo.
Fugsnarf pointed out correctly that the movement loop made it possible for two movements to occur in the same frame.
Lige pointed out correctly that I had forgotten to account for bound_x and bound_y in the locatecorner function.
This update should fix offset bounding boxes, and keep the double-movement issue from occurring.
ID:1479786
Jan 24 2014, 1:26 pm
|
|
Edit: I put sleep(world.tick_lag) before the loop begins and it's fine now.