You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
It would be nice if llGetParcelDetails() could see at least 32m into neighboring regions like llGetObjectDetails(). I know now that both methods are completely different.
Why is this feature important to you? How would it benefit the community?
If llGetParcelDetails() were allowed to see into the next region, it would allow things like vehicles, path-finding characters, and other scripted content make more informed decisions about how they should behave when they're about to cross a region into a parcel that is incompatible with their ability to function. For instance no scripts run, or out of prims. ( Also see feature request: https://jira.secondlife.com/browse/BUG-230935 )
The current iteration of llGetParcelDetails() does not return accurate data if made for a call outside of the region boundaries. In fact I believe it returns parcel information for whichever parcel is at <0,0,0>.
Allow llGetParcelDetails() to see parcels in a neighboring region.
Type
New Feature Request
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
NeoBokrug Elytis (neobokrug.elytis)
Created at
2021-07-07T01:59:18Z
Updated at
2021-07-09T17:04:03Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2021-07-07T13:01:57.947-0500',
'How would you like the feature to work?': 'It would be nice if llGetParcelDetails() could see at least 32m into neighboring regions like llGetObjectDetails(). I know now that both methods are completely different.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': "If llGetParcelDetails() were allowed to see into the next region, it would allow things like vehicles, path-finding characters, and other scripted content make more informed decisions about how they should behave when they're about to cross a region into a parcel that is incompatible with their ability to function. For instance no scripts run, or out of prims. ( Also see feature request: https://jira.secondlife.com/browse/BUG-230935 )\r\n\r\nThe current iteration of llGetParcelDetails() does not return accurate data if made for a call outside of the region boundaries. In fact I believe it returns parcel information for whichever parcel is at <0,0,0>.",
}
The text was updated successfully, but these errors were encountered:
How would you like the feature to work?
It would be nice if llGetParcelDetails() could see at least 32m into neighboring regions like llGetObjectDetails(). I know now that both methods are completely different.
Why is this feature important to you? How would it benefit the community?
If llGetParcelDetails() were allowed to see into the next region, it would allow things like vehicles, path-finding characters, and other scripted content make more informed decisions about how they should behave when they're about to cross a region into a parcel that is incompatible with their ability to function. For instance no scripts run, or out of prims. ( Also see feature request: https://jira.secondlife.com/browse/BUG-230935 )
The current iteration of llGetParcelDetails() does not return accurate data if made for a call outside of the region boundaries. In fact I believe it returns parcel information for whichever parcel is at <0,0,0>.
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: