Skip to content
lsl.devlsl.devLSL Dev

llGetParcelDetails

View as MarkdownThis page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page
function
Function syntax
list llGetParcelDetails(
  1. vector pos,// Position vector in region coordinates (only the X and Y components are used).
  2. list params// A list of PARCEL_DETAILS_* flags specifying the attributes to retrieve.
);
Returns
list
Energy
10

Both x and y components of pos are clamped to the range [0.0, 256.0], the z component is ignored.

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

How to use
list result = llGetParcelDetails(ZERO_VECTOR, []);

Specification

Section titled “Specification”
From the LSL definitions: ParcelDetailsParam (rule and request, then what it returns)
// Identity and ownershipPARCEL_DETAILS_NAME → string  // at most 63 charactersPARCEL_DETAILS_DESC → string  // at most 127 charactersPARCEL_DETAILS_OWNER → keyPARCEL_DETAILS_GROUP → keyPARCEL_DETAILS_ID → key  // the parcelPARCEL_DETAILS_AREA → integer  // square metres// SettingsPARCEL_DETAILS_FLAGS → integer  // PARCEL_FLAG_*, as llGetParcelFlagsPARCEL_DETAILS_SEE_AVATARS → integer  // booleanPARCEL_DETAILS_SCRIPT_DANGER → integer  // boolean; see llScriptDanger// Landing and teleport routingPARCEL_DETAILS_LANDING_POINT → vectorPARCEL_DETAILS_LANDING_LOOKAT → vectorPARCEL_DETAILS_TP_ROUTING → integer  // TP_ROUTING_*// Prim usagePARCEL_DETAILS_PRIM_CAPACITY → integer  // this and same-owner parcels, region-widePARCEL_DETAILS_PRIM_USED → integer  // this and same-owner parcels, region-wide
FlagMeaningMax LengthReturn
PARCEL_DETAILS_NAME0The name of the parcel.63 Charactersstring
PARCEL_DETAILS_DESC1The description of the parcel.127 Charactersstring
PARCEL_DETAILS_OWNER2The parcel owner’s key.(36 Characters)key
PARCEL_DETAILS_GROUP3The parcel group’s key.(36 Characters)key
PARCEL_DETAILS_AREA4The parcel’s area, in sqm.(5 Characters)integer
PARCEL_DETAILS_ID5The parcel’s key.(36 Characters)key
PARCEL_DETAILS_SEE_AVATARS6The parcel’s avatar visibility setting1(1 character)integer - boolean
PARCEL_DETAILS_PRIM_CAPACITY7The total prim capacity on this and all same-owner parcels, sim-wide. See llGetParcelMaxPrims for same-parcel-only and/or sim-wide reporting.integer
PARCEL_DETAILS_PRIM_USED8The total prim usage on this and all same-owner parcels, sim-wide. See llGetParcelPrimCount to get prim count by parcel owner, group, temp, etc. for same-parcel-only and/or sim-wide reporting.integer
PARCEL_DETAILS_LANDING_POINT9Landing point set for this parcel, if any.vector
PARCEL_DETAILS_LANDING_LOOKAT10Look at vector set for the landing point on this parcel, if any.vector
PARCEL_DETAILS_TP_ROUTING11

Teleport routing for this parcel.

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

integer
PARCEL_DETAILS_FLAGS12Parcel flags set for this parcel. See llGetParcelFlags for a listing of the flags and their meaning.integer
PARCEL_DETAILS_SCRIPT_DANGER13Is 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

Section titled “Caveats”
  • This cannot be used to get the parcel details of parcels in neighboring regions.

Examples

Section titled “Examples”
A very simple example to return the parcel name and description for the current parcel.
default
{
    touch_start(integer total_number)
    {
        list details = llGetParcelDetails(llGetPos(), [PARCEL_DETAILS_NAME, PARCEL_DETAILS_DESC]);


        llSay(0, "Local Parcel Name:" + llList2String(details ,0));
        llSay(0, "Local Parcel Desc:" + llList2String(details ,1));
    }
}

Known issues

Section titled “Known issues”

From the issue templates included by the wiki article:

  • SVC-4413 (fs): Please add a way to get the parcel “landing point” and “teleport routing” to llGetParcelDetails

See also

Section titled “See also”

Functions

Section titled “Functions”
Original wiki source

Some wiki templates and tables need their original context. View this article on the Second Life Wiki. Technical wording and examples are retained from the source; historical guidance may differ from current behavior.

Footnotes

Section titled “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. ↩