New gsFunction - gsGetLocation

[dazedwolf]

Is your feature request related to a problem? Please describe.
We currently use Zones to prevent people from trading or performing RP actions in OOC zones.
When this action is done, it flags their account for staff review. Sometimes people will claim "Oh I wasn't there" and we can't verify that.

Describe the solution you'd like
A new gsFunction would collect their location when the HUD was triggered and output it as a String.
Ex.:

Function: gsGetLocation()
String Output: XXX,YYY,ZZZ

Describe alternatives you've considered
There are none currently.

Additional context
This would be a very nice tool for our moderation team.

[iprice]

Is this problem with the person who is running the script, or someone they target?

There isn't currently HUD support for getting the location ; more so that second life appends the region and x,y,z into every HTTP request an item sends out, and my application just internalises that while handling that single request.

So options I'm considering are

1. Just inject these as preset variables into the script environment, i.e. add a CALLER_REGION CALLER_X /y/z into the known variables when the script starts up, but would need special attention to update the position after blocking (i.e. HUD / user input) actions, and would have to check which user responded (like if you call out to a target player, its their hud that generates a request-response with their location info, not the original caller).
2. gsAudit, for scripts to log audit messages, which log the origin of the audit request so would again either be the person who ran the script, at the time gsAudit was hit, or if the script reaches out to a target player may end up auditing against their HUD as the originator of the request.

I guess the question is wether any of this suffices or there's a need to real time (and blocking operation since it has to contact a HUD) get the co-ordinates or if one of the above is likely to work ; it depends on how complex your script is up until the point of the check potentially, or who you want to check ; if you need more than one characters locations in near real-time then I'll have to add a function to get location (which might be kinda fun for maps or something, though probably gross to spam that many requests, and maybe I'd think more about having the region server send per second mass updates of locations and actually record those)