llGetParcelDetails

From Second Life Wiki
Revision as of 13:14, 6 April 2010 by Adicted Waco (talk | contribs) (PARCEL_DETAILS_ID Covers SVC-1638)
Jump to navigation Jump to search

Summary

Function: list llGetParcelDetails( vector pos, list params );

Returns a list that is the parcel details specified in params (in the same order) for the parcel at pos.

• vector pos only x and y are important and to be given in region coordinates
• list params a list of PARCEL_DETAILS_* flags.

Flag Meaning Max Length Return
PARCEL_DETAILS_NAME 0 The name of the parcel. 63 Characters string
PARCEL_DETAILS_DESC 1 The description of the parcel. 127 Characters string
PARCEL_DETAILS_OWNER 2 The parcel owner's key. (36 Characters) key
PARCEL_DETAILS_GROUP 3 The parcel group's key. (36 Characters) key
PARCEL_DETAILS_AREA 4 The parcel's area, in sqm. (5 Characters) integer
PARCEL_DETAILS_ID 5 The parcel's key. (36 Characters) key
PARCEL_DETAILS_SEE_AVATARS 6 The parcel's avatar visibility setting[1] (1 character) integer - boolean
PARCEL_DETAILS_PRIM_CAPACITY 7 This parcel's prim capacity. integer
PARCEL_DETAILS_PRIM_USED 8 The prim usage on this parcel. integer
PARCEL_DETAILS_LANDING_POINT 9 Landing point set for this parcel, if any. vector
PARCEL_DETAILS_LANDING_LOOKAT 10 Look at vector set for the landing point on this parcel, if any. vector
PARCEL_DETAILS_TP_ROUTING 11 Teleport routing for this parcel.
  • 0 = TP_ROUTING_BLOCKED
  • 1 = TP_ROUTING_LANDINGP
  • 2 = TP_ROUTING_FREE

Note that routing rules are only enforced if the landing point is set.

integer
PARCEL_DETAILS_FLAGS 12 Parcel flags set for this parcel.

See llGetParcelFlags for a listing of the flags and their meaning.

integer
PARCEL_DETAILS_SCRIPT_DANGER 13 Is the script in danger in the indicated parcel.

See llScriptDanger for a discussion of script danger.

integer - boolean
Max Lengths in parentheses represent how many characters required when it is typecast to a string.

Caveats

  • There is also no PARCEL_DETAILS_LANDING_POINT or PARCEL_DETAILS_TELEPORT_ROUTING. SVC-4413
  • Does not detect across region boundaries using over range vector.
All Issues ~ Search JIRA for related Bugs

Examples

A very simple example to return the parcel details for the current parcel. Note the use of llGetPos() as opposed to llGetRegionCorner(). Using the latter will return simulator details.

<lsl>list landinforeqd = [PARCEL_DETAILS_NAME, PARCEL_DETAILS_DESC]; vector regionbase; default {

   state_entry()
   {
       regionbase = llGetPos();  // llGetRegionCorner();
   }
   touch_start(integer total_number)
   {
       list details = llGetParcelDetails(regionbase,landinforeqd);
       
       llSay(0, "Local Parcel Name:" + llList2String(details ,0));
       llSay(0, "Local Parcel Desc:" + llList2String(details ,1));
   }
}</lsl>

See Also

Deep Notes

All Issues

~ Search JIRA for related Issues
   Please add a way to get the parcel "landing point" and "teleport routing" to llGetParcelDetails

Footnotes

  1. ^ The parcel avatar visibility setting is used to hide avatars, their chat, and objects they sit on when they are in other parcels.

Signature

function list llGetParcelDetails( vector pos, list params );