EvilChicken!
2010-07-27 20:56:54
(Title says all.)
I'm actually baffled there doesn't exists such an element in the TUser record already, the closest thing I can get is the .Loc string. But, it makes so much more sense to have a 'Status' string in addition to the .Loc string and use both the mentioned string separately instead of having to make the location string store all the data, like I've seen many (if not most) people do.
Simply put, "Players[X].Status" suits a lot of different occasions where "Players[X].Loc" either simply may be inappropriate or inadequate to use; the .Loc variable might even already be in use.
Just wondering, would this be a useful add?
I feel it's slightly pointless to make an entire thread about such a small change, but I don't want to spam SRL with useless things. And besides, while I'm at it, I might as well do some shameless self-promotion: check out this, it's a sort of screenshot & debugging-combined thingy.
I'm actually baffled there doesn't exists such an element in the TUser record already, the closest thing I can get is the .Loc string. But, it makes so much more sense to have a 'Status' string in addition to the .Loc string and use both the mentioned string separately instead of having to make the location string store all the data, like I've seen many (if not most) people do.
Simply put, "Players[X].Status" suits a lot of different occasions where "Players[X].Loc" either simply may be inappropriate or inadequate to use; the .Loc variable might even already be in use.
Just wondering, would this be a useful add?
I feel it's slightly pointless to make an entire thread about such a small change, but I don't want to spam SRL with useless things. And besides, while I'm at it, I might as well do some shameless self-promotion: check out this, it's a sort of screenshot & debugging-combined thingy.