llKey2Name

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el 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

Key2Name

llKey2Name

Summary

1/3 Bugs

Function: string llKey2Name( key id );

0.0	Forced Delay
10.0	Energy

Returns a string that is the legacy name of the prim or avatar specified by id.

• key

id

–

group, avatar or prim UUID that is in the same region

id must specify a valid rezzed prim or avatar key, present in or otherwise known to the sim in which the script is running, otherwise an empty string is returned. In the case of an avatar, this function will still return a valid 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).

Keys of inventory items will not work; in the case of these, use llGetInventoryName instead.

Caveats

• It is difficult to tell the difference between a prim that has a name that is an empty string and a prim that is not in the sim, or because an invalid key was specified. Use llGetObjectDetails to avoid this problem.
• To get around the "avatar must be present" limitation, you can use the llRequestAgentData function and the dataserver event to obtain the avatar's name from a key.
• There is no opposite function (llName2Key) available. However, there are third-party websites which can be queried using the llHTTPRequest function and the http_response event.
• If an avatar is "ghosted" (which occasionally happens due to a longstanding server bug), an empty string is returned even though the avatar is seemingly present and shows up in llSensor and the Mini-Map. This fact can be used as the basis of a Ghost Detector script.

Examples

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

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

}</lsl>

Notes

Active Name2Key Databases:

• http://n2k.danardlabs.com (SSL, Legacy Names & Usernames supported)
• http://w-hat.com/name2key
• http://kdc.ethernia.net/sys/name2key.php
• http://wiki.apez.biz/Development (web-service API functions getAvatarKey and getAvatarName)
• http://insl.kubwa.de/name2key.php?name=name (Bot based name2key Database. Supports: Legacy and Username formats)

Dead Name2Key Databases:

• http://www.libsecondlife.org/protocol/index.php/Name2key(Appears to be gone as of Apr 2008, but search for name2key on that site for more information)
• http://www.ulrikasheim.org/tools/name2key.html(Appears to be gone as of Apr 2008)

Name2Key Libraries:

• Name2Key_in_LSL
• Ugleh Ulrik's Name2Key PHP script

See Also

Functions

•	llGetUsername
•	llGetDisplayName
•	llGetObjectDetails
•	llRequestAgentData	–	Uses the dataserver to request avatar information

Articles

•

Prim Attribute Overloading

Deep Notes

Signature
function string llKey2Name( key id );