Using step_towards() in pixel movement seems to miscalculate the direction at close proximity in certain situations, possibly based on the target's location (when both objects are in the same tile?), instead of their actual position. This can lead to some flunky looking results, like an object walking up and down repeatedly next to a target, instead of taking that final step into them.
Using step(src,get_dir(src,target)) seems to provide a simple workaround for the time being
ID:122696
Jan 9 2012, 7:51 am
|
|||||||||||||
Resolved
| |||||||||||||
Jan 9 2012, 5:59 pm
|
|
I think step/walk_to/towards was only changed to include the speed argument... They probably haven't been changed to be pixel-precise in how they line up with the target, like matching the x and/or y of the bounding boxes' centers. I think the procs fail when the ref enters a turf in the target's locs.
|