Skip to content
lsl.devlsl.devLSL Dev

llSetObjectDesc

View as MarkdownThis page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page
function
Function syntax
llSetObjectDesc(
  1. string description// New description string (up to 127 characters).
);
Energy
10

Sets the description of the prim containing the script to description (limited to 127 characters).

Sets the prims description

How to use
llSetObjectDesc("");

Caveats

Section titled “Caveats”
  • Changing the object description does not trigger a changed event.

Examples

Section titled “Examples”
Set this prim’s descriptionSet the root prim’s description
default
{
    state_entry()
    {
        llSetObjectDesc("NEW PRIM DESCRIPTION");
    }
}
default
{
    state_entry()
    {
        llSetLinkPrimitiveParamsFast(LINK_ROOT,
            [PRIM_DESC, "NEW ROOT PRIM DESCRIPTION"]);
    }
}

Notes

Section titled “Notes”
  • Object descriptions are often used to store data that needs to be protected from script resets (see, for example, Prim Attribute Overloading). However, descriptions are not immutable and can be tampered with by users or other scripts, either intentionally or accidentally, so this method should only be considered a last resort for data storage.
  • llLinksetDataWrite and associated functions are generally better suited for this purpose, because they allow for significantly more data storage and are much more secure against tampering.

Known issues

Section titled “Known issues”

From the issue templates included by the wiki article:

  • VWR-437 (bug): llSetObjectDesc and editor panel have different description string length limits
  • SVC-3429 (bug): Name or description change, of an attached object, is rolled back when object is detached
  • VWR-8761 (bug): Cannot delete object description.

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.