Difference between revisions of "PARCEL DETAILS GROUP"

From Second Life Wiki
Jump to navigation Jump to search
Line 6: Line 6:
|examples
|examples
|functions={{LSL DefineRow||[[llGetParcelDetails]]}}
|functions={{LSL DefineRow||[[llGetParcelDetails]]}}
|constants=<table class="sortable" {{Prettytable}}>
|constants={{!}}{{LSL_Constants/Parcel_Details}}
<tr {{Hl2}}>
<th> Detail </th>
<th title="Value"></th>
<th class="unsortable"> Meaning </th>
<th> Max Length </th>
<th> Return Type </th>
</tr>
<tr>
<td>{{LSL Const|PARCEL_DETAILS_NAME|integer|0|c=The name of the parcel.}}</td>
<td>{{#var:value}}</td>
<td>{{#var:comment}}</td>
<td>63 Characters</td>
<td>[[string]]</td>
</tr>
<tr>
<td>{{LSL Const|PARCEL_DETAILS_DESC|integer|1|c=The description of the parcel.}}</td>
<td>{{#var:value}}</td>
<td>{{#var:comment}}</td>
<td>127 Characters</td>
<td>[[string]]</td>
</tr>
<tr>
<td>{{LSL Const|PARCEL_DETAILS_OWNER|integer|2|c=The parcel owner's key.}}</td>
<td>{{#var:value}}</td>
<td>{{#var:comment}}</td>
<td>(36 Characters)</td>
<td>[[key]]</td>
</tr>
<tr>
<td>{{LSL Const|PARCEL_DETAILS_GROUP|integer|3|c=The parcel group's key.}}</td>
<td>{{#var:value}}</td>
<td>{{#var:comment}}</td>
<td>(36 Characters)</td>
<td>[[key]]</td>
</tr>
<tr>
<td>{{LSL Const|PARCEL_DETAILS_AREA|integer|4|c=The parcel's area, in sqm.}}</td>
<td>{{#var:value}}</td>
<td>{{#var:comment}}</td>
<td>(5 Characters)</td>
<td>[[integer]]</td>
</tr>
</table>
Max Lengths in parentheses represent how many characters required when it is [[typecast]] to a string.
|events
|events
|cat1=Parcel
|cat1=Parcel

Revision as of 08:44, 30 August 2007

Description

Constant: integer PARCEL_DETAILS_GROUP = 3;

The integer constant PARCEL_DETAILS_GROUP has the value 3

This is a flag used with llGetParcelDetails to check if the parcel has access restricted to a group.

Caveats


Related Articles

Constants

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.

Functions

•  llGetParcelDetails

Deep Notes

Search JIRA for related Issues

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

integer PARCEL_DETAILS_GROUP = 3;