ID:1468871
 
Not a bug
BYOND Version:503
Operating System:Windows 7 Home Premium 64-bit
Web Browser:Firefox 26.0
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:
When ever I use an /obj reference to an overlay it will place the reference in a really weird offset position.




Numbered Steps to Reproduce Problem:

Code Snippet (if applicable) to Reproduce Problem:
mob
logging
Login()
client.perspective = EDGE_PERSPECTIVE
var/mob/player/p = new/mob/player()
p.key=src.key
del src


mob
player
Login()
spawn()
Players.Add(src)
src.icon='BaseT.dmi'
src.overlays+=/obj/Short_Hair
src.loc=locate(1,1,1)
src.save()
proc
save()
var/savefile/F = new/savefile("saves/[copytext(src.ckey,1,2)]/[src.ckey].sav")
F << src
F["Name"]<<src.name

obj
Short_Hair
icon='gaaraH.dmi'


Expected Results:
Icon works properly either way its coded weather I use an icon or a object reference
Actual Results:
Icon doesnt properly apply to overlays.
Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?

When does the problem NOT occur?

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:
mob
logging
Login()
client.perspective = EDGE_PERSPECTIVE
var/mob/player/p = new/mob/player()
p.key=src.key
del src


mob
player
Login()
spawn()
Players.Add(src)
src.icon='BaseT.dmi'
src.overlays+="gaaraH.dmi'
src.loc=locate(1,1,1)
src.save()
proc
save()
var/savefile/F = new/savefile("saves/[copytext(src.ckey,1,2)]/[src.ckey].sav")
F << src
F["Name"]<<src.name


Your images don't seem to work. Can you re-upload them to another image provider? imgur.com is a solid image uploading site, and can use your google profile for instant registration/login.

I'm also not able to reproduce this issue.

Is this occuring in 504.1225?
In response to Ter13
Updated the post with imageur.com. Also no I am using the current stable version 503.1244. I think?
Have you tried to reproduce this problem in a blank environment? I'm not getting this issue in any environment I test in.

I'm pretty sure this is not a bug, so if you can't provide a code snippet that reproduces this issue, I'm going to have to mark it as such.
In response to Ter13
Hmm yeah next time ill try to test it in a blank environment before assuming it was a bug. My bad. sorry for wasting your time
Not a waste at all. If you need help tracking down the cause of this one, you know the forum for that.
Ter13 resolved issue (Not a bug)