Difference between revisions of "LlKey2Name"
Jump to navigation
Jump to search
Rolig Loon (talk | contribs) |
Rolig Loon (talk | contribs) |
||
| Line 11: | Line 11: | ||
|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. | |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. | * 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. | ||
* The opposite function ([[ | * The opposite function ([[llName2Key]]) can be used to find the legacy name associated with an avatar in the same region. To find the name of an avatar anywhere on the grid, use [[llRequestUserKey]], which triggers a [[dataserver]] 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. | * 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. | ||
|constants | |constants | ||
Revision as of 12:28, 12 June 2018
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
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.
- The opposite function (llName2Key) can be used to find the legacy name associated with an avatar in the same region. To find the name of an avatar anywhere on the grid, use llRequestUserKey, which triggers a dataserver 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
// Best viewed in Chat History (ctrl-h)
default
{
collision_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llKey2Name(id);
string detectedName = llDetectedName(0);
llSay(0, "llKey2Name: " + name
+ "\nllDetectedName: " + detectedName);
}
touch_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llKey2Name(id);
string detectedName = llDetectedName(0);
llSay(0, "llKey2Name: " + name
+ "\nllDetectedName: " + detectedName);
}
}
Notes
World Wide Web Consortium
- N2K - Independent of databases or bots, this uses the W3C html2text to convert the viewer search to text and extract the key from Second Life's own services.
Active Name2Key Databases:
- W-Hat name2key (last names replaced with the Resident word for the Usernames)
- KDC name2key
Dead Name2Key Databases:
- Kubwa name2key (Bot based name2key Database; Supports: Legacy and Username formats; Shows related names; SSL support.) (Appears to be gone as of Apr 2013 [Reports Error 404])
http://wiki.apez.biz/Development (web-service API functions getAvatarKey and getAvatarName)(Apez seems to be gone ? - May 2011)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)DB4MV name2key (Name2Key Database for Avatars (Legacy Names,Usernames, and Display Names, GroupNames and Keys, LSL API)(Currently listed as non-existant by host)
Name2Key Libraries:
See Also
Functions
| • | llGetUsername | |||
| • | llGetDisplayName | |||
| • | llGetObjectDetails | |||
| • | llRequestAgentData | – | Uses the dataserver to request avatar information |
Articles
| • | Prim Attribute Overloading |
Deep Notes
History
- llKey2Name Added in SL 0.4.0[1]
Footnotes
- ^ Early release notes were not very accurate or thorough, they sometimes included information about features added in previous releases or failed to include information about features added in that release.
Signature |
|---|
function string llKey2Name( key id ); |
Haiku |
|---|
|
Numbers in machines,
|