ID:2394299
 
Resolved
The locs value was incorrect in cases where an atom's step offsets had not yet been "normalized".
BYOND Version:512.1447
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 68.0.3440.106
Applies to:Dream Daemon
Status: Resolved (512.1448)

This issue has been resolved.
Descriptive Problem Summary:

A regression caused by the recent movement updates caused the locs variable to contain less than it was supposed to.

Numbered Steps to Reproduce Problem:

1) Set an object's bounds to cover multiple tiles.
2) Create the object, the locs var will contain roughly half of the turfs it should.
3) step() the object
4) locs is fine.

Code Snippet (if applicable) to Reproduce Problem:
obj
big
bounds = "1,1 to 64,64"
New()
..()
world << "Locs: [locs.len]"
step(src,EAST)
world << "Locs: [locs.len]"


Expected Results:

locs to contain all tiles the object is covering on creation.

Actual Results:

locs contains around half of the tiles the object is covering until it moves.

Does the problem occur:
Every time? Or how often? Very time
In other games? Yep
In other user accounts? Yep
On other computers? Yep

When does the problem NOT occur?

512 versions prior to the movement overhaul.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Not sure exactly what 512 this popped up in, but it's definitely the result of the movement overhaul.

Workarounds:

Patiently wait for 1448 :)
Lummox JR resolved issue with message:
The locs value was incorrect in cases where an atom's step offsets had not yet been "normalized".