Second Life Wiki - User contributions [en]

LlGetUsername

2010-11-06T21:09:09Z

DarthBunny Petrov:

{{LSL_Function/avatar|id|sim=*}}{{LSL_Function
|inject-1={{LSL Generic/pre-release|server-release=[[Display Names|DisplayNames]]}}
|func_id=NNN|func_sleep=0.0|func_energy=10.0
|sort=GetUsername|func=llGetUsername
|return_type=string|p1_type=key|p1_name=id
|func_footnote='''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 username 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).
|func_desc
|return_text=that is the unique username of the avatar specified by '''id'''.
|spec
|caveats=* To get around the "avatar must be present" limitation, you can use the [[llRequestUsername]] function and the [[dataserver]] event to obtain the avatar's username from a key.
* There is no opposite function ([[llUsername2Key]]) available.
* Display Name changes may take up to 72 hours to propagate. During this time scripts may report the old display name.
|constants
|examples=<lsl>// Best viewed in Chat History (ctrl-h)
default
{
collision_start(integer a)//Announce who collided
{
llSay(0, "llGetDisplayName: " + llGetDisplayName(llDetectedKey(0)) +
"\nllGetUsername: " + llGetUsername(llDetectedKey(0)));
}
touch_start(integer a)
{
llSay(0,"llGetDisplayName: " + llGetDisplayName(llDetectedKey(0)) +
"\nllGetUsername: " + llGetUsername(llDetectedKey(0)));
}
}</lsl>
|helpers
|also_functions=
{{LSL DefineRow||[[llGetDisplayName]]}}
{{LSL DefineRow||[[llRequestUsername]]|Uses the [[dataserver]] to request avatar information}}
|also_events
|also_articles=
|also_tests
|notes=
|cat1=Avatar
|cat2=Username
|cat3=Key
|cat4=Avatar/Name
}}

Category:LSL Avatar/Name

2010-11-06T20:58:31Z

DarthBunny Petrov:

{{LSL Header}}{{LSLC|}}{{LSLC|Avatar}}[[Category:Display Names]]
===Names===
From an LSL standpoint avatars can have 3 different names.

{| {{Prettytable}}
! Names:
! {{Hl2}} | Description
! {{Hl2}} | Unique
! {{Hl2}} | Get (in region)
! {{Hl2}} | Request ([[dataserver]])
! {{Hl2}} | [[llSensor]]([[llSensorRepeat|Repeat]]) flags
! {{Hl2}} | {{LSLGC|Detected|detected}} events
|-
! {{Hl2}} | Display
| The name that is displayed on the screen.
| No
| [[llGetDisplayName]]
| [[llRequestDisplayName]]
| [[Display_Names/LSL#What_about_an_AGENT_BY_DISPLAY_NAME_flag_for_llSensor.3F|NA]]
| {{HoverText|NA|Use llGetDisplayName in conjunction with llDetectedKey.}}
|-
! {{Hl2}} | User
| The name the users logs in with.
| Yes
| [[llGetUsername]]
| [[llRequestUsername]]
| [[AGENT_BY_USERNAME]]
| {{HoverText|NA|Use llGetUsername in conjunction with llDetectedKey.}}
|-
! {{Hl2}} | Legacy
| An interface predating [[Display Names]].
| Yes
| [[llKey2Name]]
| [[llRequestAgentData]]
| [[AGENT_BY_LEGACY_NAME]]
| [[llDetectedName]]
|}
{| {{prettytable|style=float:right;margin-top:0;}}
|+ <h4>Name Formats by Account Type</h4>
|
! {{Hl2}} | Modern
! {{Hl2}} | Legacy
|-
! {{Hl2}} | User Name
| "username"
| "firstname.lastname"
|-
! {{Hl2}} | Legacy Name
| "username Resident"
| "FirstName LastName"
|-
! {{Hl2}} | Display Default
| "username"
| "FirstName LastName"
|}

=== Modern and Legacy Accounts ===
* Modern accounts are created by choosing a user name, which consists of one name (no spaces).
* Legacy accounts were created by choosing two names: first and last names. These two names are used together to form the username.

To maintain compatibility with legacy scripts (that expect two names), modern accounts are given the legacy last name "Resident".

The default value of the Display Name depends upon the type of the account. For legacy accounts, it's the Legacy Name, for modern accounts, its the Username.

<lsl>string LegacyToUsername(string legacy)
{
list name = llParseString2List(llToLower(legacy), [" "]);
if(llList2String(name, 1) == "resident")//it's not a legacy account. (lowercase "resident" because of llToLower)
return llList2String(name, 0);//first name is username
return llDumpList2String(name, ".");
}</lsl>

=== Legacy-Name Only Functions ===

These functions only take Legacy Names and there are no alternative functions available.

* [[llCollisionFilter]]
* [[llListen]]

===FAQs===
There are a couple of FAQs that go into much more detail about this:
* LSL FAQ: [[Display_Names/LSL]]
* General FAQ: [[Display_Names]]

User:Ama Omega/archive/script jira triage

2010-10-13T13:22:59Z

DarthBunny Petrov: /* New Features */

== Details ==
Every other Monday at Kelly's office hours we will hold a Scripting jira triage. If you have an issue you would like discussed, please add it to the end of the issue triage list below. Please add a single line for each jira with:<br>your avatar name, jira id, jira subject

Process:
* Delete all issues in "Triaged Last Time"
* Discuss the issues one at a time from top to bottom
* After discussing the issue I will set the 'last triaged' field, change status if appropriate and comment on the issue
* Move the triaged issue down to the "Triaged Last Week" category.

== Issues To Triage ==
=== Bugs ===
* {{Jira|SVC-5335}} - llGetSubString can produce results that crash Mono scripts - 1 vote - Tano Toll ([[User:Cerise Sorbet|Cerise Sorbet]])

=== New Features ===
* {{jira|SVC-6357}} - '''llGetUnixTimeNanos'''() - greater precision timing mechanism - 1 vote - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-5742}} - Unbundle PRIM_* rules for llSetPrimitiveParams and similar functions to allow for individual parameter settings for all possible parameters. - 10 votes - [[User:Talarus_Luan|Talarus Luan]]
* {{jira|SVC-6350}} - Megaprims in Estate Tools (specific proposal) - 1 vote - [[User:Talarus_Luan|Talarus Luan]]
* {{jira|SVC-92}} - '''llTargetSay'''() - region-wide direct communication - 2 votes - [[User:Haravikk_Mistral|Haravikk Mistral]]
** Discussed in previous triage as {{jira|SVC-6326}}, encompasses suggested alternative solution of '''llTriggerSay'''(), was previously '''llInstantMessageLocal'''().
* {{jira|SVC-2105}} - '''llSetLinkListPrimitiveParams'''() for setting multiple, specific linked items - 54 votes - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-6385}} - Expose/Add more flags to '''llGetParcelFlags''' - 1 vote - [[User:DarthBunny Petrov|DarthBunny Petrov]]

== Triaged Last Time ==
* {{jira|SVC-4323}} - Casting a list with a vector to string, differs from casting a vector to string - 1 vote - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-924}} - '''llSit'''() - scriptable ability to force an avatar to sit on an object - 7 votes - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-2988}} - Convert [[llListSort]]() to use faster sorting methods! - 49 votes - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-6326}} - Remove [[llInstantMessage]] delay for avatars in region - 1 vote - [[User:Haravikk_Mistral|Haravikk Mistral]]
** Replaced by {{jira|SVC-92}} - '''llTargetSay'''() - region-wide direct communication - 2 votes - [[User:Haravikk_Mistral|Haravikk Mistral]]
* {{jira|SVC-6364}} - Automatically optimise calls to [[llGetListLength]](list) by replacing them with (list != []) - 1 vote - [[User:Haravikk_Mistral|Haravikk Mistral]]

User:DarthBunny Petrov

2010-10-08T04:22:10Z

DarthBunny Petrov: Created page with '==Who?== * Rezzed at February 17th, 2007. * Builds/scripts/textures things mainly for fun; this sometimes results in things that are sold. * Does customer service stuff and esta...'

==Who?==

* Rezzed at February 17th, 2007.
* Builds/scripts/textures things mainly for fun; this sometimes results in things that are sold.
* Does customer service stuff and estate managing things at a private estate.
* Loves Star Trek and other geeky stuff.
* Over-uses the words 'stuff' and 'thing(s)'.

Skybox

2010-10-08T00:16:25Z

DarthBunny Petrov: /* What else should I know? */

{{KBmaster}} {{TOCright}}

== What's a skybox? ==

In Second Life, a '''skybox is exactly what it sounds like: a building in the sky'''.

Skyboxes are as varied in appearance as ground structures: they range from simple work platforms which aren't technically boxes (for building, photography, and other focused activities) to elaborate houses (like castles in the clouds!) and even whole malls. Also, places that feel natural "in the air", like space stations, could be considered skyboxes within Second Life's [[culture]].

<gallery widths=320px heights=320px perrow=2>
File:4597277377_433ed5e9d8_o.jpg|A minimalist, elegant skybox by maclane Mills
File:3431138779_3c4264feb7_o.jpg|A distinctively curved design by Trin Trevellion
File:4616809636_13843663f0_o.jpg|Exodi, floating sky store
File:4987038456_5455ff3935_o.jpg|Some prefab skyboxes include matching furniture
</gallery>

== How can I get a skybox? ==

You can, as with just about everything else in Second Life, build your own. Here's a video tutorial showing how to place objects in the sky:

: {{KBvideo|sAGnG63TdJg|640|385|type=youtube}}

{{KBcaution|As shown in the video, "{{xref|rez}} a cube and sit on it" may not work if the region you're in uses a "terrain extender", due to [https://jira.secondlife.com/browse/SVC-3811 this bug].}}

If you'd prefer the convenience of a "prefab" skybox, there's a '''[http://bit.ly/d2Uc6F special "Sky Boxes" category on the Marketplace]''' and you can also '''[http://bit.ly/cE2ulW search for skyboxes]''', as many aren't in that category (yet). The same means shown above can be used to get up there and place the skybox.

== How high can a skybox be? ==

As shown in the [[Limits|limits list]], the build height is 4,096m. However, the base of even a very high skybox will likely be placed below that (for example, 4,000m), allowing for room to be built upwards in case the owner wants to add an extra floor or other expansions.

== Why bother? ==

Since avatars can fly in Second Life and placing objects in the air isn't affected by gravity (unless you choose to enable physics on them), making use of vertical space is very popular for several reasons, including:

# '''Privacy''' - It's less likely for both text and voice chat to be heard when it's hard to get to where you are. (Although IMs, instant messages, can be a better option since they can't be snooped on by proximity.) New Residents and casual passerby are less likely to look thousands of meters upwards. Part of this is because there's a built-in fly height limit (also shown on the [[Limits|limits list]]), which can be bypassed with a scripted "flight assist" gadget, but is otherwise a default restriction. A skybox doesn't guarantee privacy, however, and at most is a casual deterrent. Use the tools in '''World''' menu > '''Place Profile''' to restrict parcel and region access.
# '''Performance''' - What's in the sky is a lot less dense than what's on the ground. When less things need to be rendered, performance improves. Also, lack of visual clutter can help someone focus on a creative task, not unlike how [http://www.techmalaya.com/2009/02/07/full-screen-text-editor-blogger/ distraction-free text editors have become popular].
# '''Immersion''' - Some Residents have figured out clever ways to create the illusion of a self-contained environment by putting a build inside a textured, giant sphere. This obviously doesn't work on the ground, where the terrain and water are visible. A variation on this are skyboxes that have textures on the windows that simulate city landscapes and other "fake" environments to better control the experience.

<gallery widths=320px heights=320px perrow=2>
File:4604986523_667c315f3d_o.jpg|A texture is projected onto the window to make it look like the outside world is prettier
File:3458032368_32ef25dbf0_o.jpg|"Baked" shadows add cohesion to the outside cityscape
File:4118385703_1d8d025e86_o.jpg|Deshima space station is wrapped in a giant colored sphere which provides this background
File:3821274922_c4c991b31a_o.jpg|An outside view showing these stores in their own sphere "world"
</gallery>

== What else should I know? ==

There are special considerations to building in the sky:

* '''You should only build on land you own or otherwise are allowed to''' (feel free to practice in a [[sandbox]]). Don't leave "sky litter" on someone else's property.
* '''Check if sky boxes are allowed by the local covenant,''' or if there are certain restrictions. For example, the [[Linden Lab Official:Linden_Home/Covenant#Linden Home Restrictions|Linden Home Covenant]] does not allow sky boxes. Private estates may or may not allow them, or have minimum and or maximum heights for sky boxes.
* '''Don't let your skybox overlap onto adjacent parcels.''' It's hard to tell where one parcel ends and another begins since property lines are only visible on ground terrain, so watch the navigation bar at the top of the Viewer window — as you walk or fly around, if the parcel name changes to another, you'll know you're past the borders.
* You may also wish to right-click the navigation bar and check '''Show Coordinates''' so you can '''see exactly where you are''', including height.
*: [[File:Show_Coordinates.png]]

== Alternate usages ==

[http://en.wikipedia.org/wiki/Skybox_(video_games) "Skybox" in other 3D environments] commonly means a simple construct to simulate skies.

Talk:Display Names/LSL

2010-08-20T14:12:05Z

DarthBunny Petrov: /* The "N" and the "n" used for name in functions */

I have a Name2Key database to deliver gifts and to link registred users on my website to their SL account. The Name2Key Database does a namesearch lookup with a bot, if the name could not be found in the database. Will the namesearch lookup find the display names or the real names ? And whats when there are multiple people are using the same display name ?

:''With bots we are talking more viewer code than scripting. It will depend on how your bot works and how it does its searches. I would not be surprised if it required some updating to find the correct resident.'' - [[User:Kelly Linden|Kelly Linden]] 15:31, 19 August 2010 (UTC)

== The "N" and the "n" used for name in functions ==

Hi Kelly,

considering function names llGetDisplayName and llGetUsername (''same for lRequestxxxx'') you'll see a difference for Name and name ; is it a mistake when you have written this article or the real names of the functions?

If they are the real function names, that will generate compile errors surely because we are humans :))

Yours truly

Garmin

[[User:Garmin Kawaguichi|Garmin Kawaguichi]] 10:39, 20 August 2010 (UTC)

:That is because it's a username (one word) and a display name (two words), I think. A similar difference is in the llSensor constants: AGENT_BY_DISPLAY_NAME and AGENT_BY_USERNAME. Getting compile errors due to typos I already get a lot, I expect some more with these yeah :p [[User:DarthBunny Petrov|DarthBunny Petrov]] 14:12, 20 August 2010 (UTC)

== The dataserver functions ==
I'm curious about why the dataserver requests to get the username and display name weren't added to llRequestAgentData (with for example new constants DATA_USERNAME and DATA_DISPLAY_NAME). Is it easier to add new functions? Or do separate functions just make more sense from a language design point of view or something? [[User:DarthBunny Petrov|DarthBunny Petrov]] 14:12, 20 August 2010 (UTC)