Information

At the advent of scripted teleport functions working again without breaking scripts I felt this needed another look since the original issue SVC-4413 was filed in 2009 and was never acknowledged.

llGetParcelDetails() proposed constants & syntax:

|Flag|Value|Description|
|
|-|-|-|-|
|PARCEL_DETAILS_LANDING_POINT|7|Returns a vector for parcel's landing point.|
|
|PARCEL_DETAILS_LANDING_LOOKAT|8|Returns either a vector or a float for parcel's landing lookat vector or degree value.|
|
|PARCEL_DETAILS_TP_ROUTING|9|Returns an integer that is the parcel's teleport routing setting.|



Having this information will allow scripted teleport applications to let their users know if they will work correctly over the parcel at the target pos as well as let users know if the teleport routing of the parcel they are over allows double click teleporting or not.



Thanks in advance for any consideration.



# Additional Information



Flags 7 & 8 are already used but not exposed.

Currently they are returning the same data as llGetParcelMaxPrims(vector pos,TRUE) and llGetParcelPrimCount(vector pos,PARCEL_COUNT_TOTAL,TRUE).

These flags can be replaced.|

{
  'Business Unit': ['Platform'],
  'How would you like the feature to work?': 'idk',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': 'idk',
}