Client Screen Object Offsets

by EnvyAttraction
Irritated that offsets like pixel_x/y/z don't work properly on clients screens? Then this library is for you!

About Client Screen Object Offsets

ID:1493060
 
Feb 8 2014, 9:00 pm
Basically this library includes a proc that dissects the screen location of and object and alters its location to include your offsets without systematically knowing where it already is to provide the correct offset that you want.

This is an alternative to using pixel_x/y for on_screen objects which isn't compatible for client.screen.
Feb 14 2014, 2:40 am
I understand your point in releasing this, but the pixel_x,y and z are not involved in the clients screen.

However, screen_loc is and in your notes, you have a misguiding comment where you said you are cheating BYOND's system but in reality you are just using screen_loc how BYOND intended it to be.

Overall: Pretty redundant but do as you please. :)
Feb 14 2014, 6:17 am
I myself just store HUD elements inside of a list that need altering.

//#Example

/mob/var/tmp/list/HUD=list()

/HUD
    parent_type=/obj
    New(client/C,Loc)
        screen_loc = "[Loc]"
        C.screen+=src

/mob/verb/Test()
    HUD["Health"] |= new/HUD(client,"5,5")
    var/HUD/H = HUD["Health"]
    H.screen_loc = "5:15,5"