ID:2347845
 
Resolved
Certain operations with vis_locs, such as reading its length, did not work correctly.
BYOND Version:512.1410
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 64.0.3282.167
Applies to:Dream Daemon
Status: Resolved (512.1411)

This issue has been resolved.
Descriptive Problem Summary:
vis_locs doesn't work
Numbered Steps to Reproduce Problem:
Add an object to something's vis_contents
Checking that object's vis_locs.len always results in 0
Code Snippet (if applicable) to Reproduce Problem:
CheckVisLocs()
var/obj/O = new
var/obj/N = new
O.vis_contents += N
world.log << "[N.vis_locs.len]"


Expected Results:
"If this atom is in any other atoms' visual contents, those parent atoms will appear in this list."
Actual Results:
0
Does the problem occur:
Every time? Or how often? Y
In other games? Y
In other user accounts? Y
On other computers? Y

When does the problem NOT occur?
Never
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.)
feature new to 512

Workarounds:
make your own variable to do the same thing
Lummox JR resolved issue with message:
Certain operations with vis_locs, such as reading its length, did not work correctly.