ID:1491191
 
Not a bug
BYOND Version:503
Operating System:Windows 7 Home Premium
Web Browser:Chrome 32.0.1700.107
Applies to:Dream Maker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
Basically pixel_x/pixel_y/pixel_z seem to not be visually represented on a clients screen.
Numbered Steps to Reproduce Problem:
1. Make an icon and program an object for it.
2. Define the object and its screen_loc and add it to client.screen.
3. Attempt to use animate to alter its offsets, or just attempt to set them.

Code Snippet (if applicable) to Reproduce Problem:
obj

test
icon='Test.dmi'

mob/Login()
usr.loc=locate(1,1,1)
var/obj/test/blah=new
blah.screen_loc="5,5"
usr.client.screen+=blah
spawn animate(blah,pixel_y=20,time=10)
blah.pixel_x=20

mob/verb/Debug()
for(var/obj/q in usr.client.screen)
usr<<"[q]: [q.pixel_x] / [q.pixel_y]"


Expected Results:
For the object to appear at its expected offset.
Actual Results:
When trying to set an offset(pixel_y=blah) nothing happens visually but mechanically that is its variable.

When using animate in the attempt to alter it- it DOES animate- but when the animate's time is up and the offset reaches it goal- visually the object goes back to where it was.

Does the problem occur:
Every time? Or how often? Every time and every attempt at a run around has failed.
In other games? N/A
In other user accounts? N/A
On other computers? N/A

When does the problem NOT occur?
It always occurs.
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.)

Workarounds:
None as of anything I've tried.
This isn't a bug. pixel_x and pixel_y are intended to be used on the map, not on the screen. Look up the reference for screen_loc - it has more parameters than just x,y. You use colons to add pixel offsets.

screen_loc = "5:16,5:-16"
Lummox JR resolved issue (Not a bug)