ID:1916482
 
Resolved
Atom gliding had some irregularities, and also caused movement icons to appear incorrectly in non-gliding games.
BYOND Version:508
Operating System:Windows 10 Preview
Web Browser:Firefox 39.0
Applies to:Webclient
Status: Resolved (508.1296)

This issue has been resolved.
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.
I'm not entirely sure I follow; can you clarify for me, or provide a test case?

Gliding to the new location is desirable if it's one tile away. Are you saying it happens when more than one tile away?
In response to Lummox JR
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.
Okay, good to know. I'll get that fixed.
Thanks, keep up the good work.
Lummox JR resolved issue with message:
Atom gliding had some irregularities, and also caused movement icons to appear incorrectly in non-gliding games.
(I giggled a few times testing this bug, being so used to it not gliding in those cases made seeing this feel really strange.)