llGetDisplayName

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/fr Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

GetDisplayName

llGetDisplayName

	Security Warning!
	It is a terrible idea to tie any security measures to display names; they are not unique and can easily be changed.

	Data Execution Warning!
	Display names can contain quotes and some punctuation. While this is not a problem for LSL, remember to escape strings being passed to command line scripts, sql queries, etc. See: XKCD: Exploits of a Mom

Summary

1 Bug

Function: string llGetDisplayName( key id );

0.0	Forced Delay
10.0	Energy

Returns a string that is the non-unique display name of the avatar specified by id.

• key

id

–

avatar UUID that is in the same region or is otherwise known to the region

id must specify a valid avatar key, present in or otherwise known to the sim in which the script is running, otherwise an empty string is returned. This function will still return a valid display name if the avatar is a child agent of the sim (i.e., in an adjacent sim, but presently able to see into the one the script is in), or for a short period after the avatar leaves the sim (specifically, when the client completely disconnects from the sim, either as a main or child agent).

Caveats

• To get around the "avatar must be present" limitation, you can use the llRequestDisplayName function and the dataserver event to obtain the avatar's display name from a key.
• There is no opposite function (llDisplayName2Key) available since display names are non-unique
• Either of "???" or "" is returned if the region is unable to return display names. This can happen even if display names are enabled on the region, especially the first time a given key is checked. At least one retry may be advisable. Do not rely on this function to verify avatar presence.
  • Do not retry failed attempts indefinitely in a loop. In a few cases, a display name or username will not be returned for as long as the avatar is in the region.
• If you merely wish to show avatar name information in the viewer window, it may be more straightforward to use Viewer URI Name Space, e.g.:<lsl>llSay(0, "secondlife:///app/agent/" + (string)id + "/displayname");</lsl>

Examples

<lsl>// Best viewed in Chat History (ctrl-h) default {

   collision_start(integer a)//Announce who collided
   {
       llSay(0, "llGetDisplayName: " + llGetDisplayName(llDetectedKey(0)) +
              "\nllDetectedName: " + llDetectedName(0));
   }
   touch_start(integer a)
   {
       llSay(0,"llGetDisplayName: " + llGetDisplayName(llDetectedKey(0)) +
              "\nllDetectedName: " + llDetectedName(0));
   }

}</lsl>

See Also

Functions

•	llGetUsername
•	llRequestDisplayName	–	Uses the dataserver to request avatar information

Deep Notes

Signature
function string llGetDisplayName( key id );