When you set atom.loc, the atom will glide into their new location when you're running the web client. It should not glide into place, it should just appear at the new location.
This happens when using setting atom.loc to an object directly and when using locate() to return the object.
BYOND V508.1295.
ID:1916482
![]() Aug 12 2015, 6:43 pm
|
|||||||||||||
Resolved
| |||||||||||||
Lummox JR wrote:
Gliding to the new location is desirable if it's one tile away. Are you saying it happens when more than one tile away? Yeah, it seems to glide even if it's more than one tile away. It's as simple as: src.loc=locate(src.x, src.y+2, src.z) I can provide a test case if you need one, although I figured it would be pretty straight forward to reproduce. |
Lummox JR resolved issue with message:
Atom gliding had some irregularities, and also caused movement icons to appear incorrectly in non-gliding games. |
Gliding to the new location is desirable if it's one tile away. Are you saying it happens when more than one tile away?