nyuuzyou/wikis huggingface dataset:
Name

See the following pages for more information:
== Resident Name / Account Name ==
* Linden Lab Official:Second Life Last Names FAQ
* Linden Lab Official:Can I have a custom last name for my Second Life account?
* Linden Lab Official:Why isn't the last name I want listed?
* Linden Lab Official:Custom Name Program (beta) General Information
* Can I turn off the display of my own avatar's name to others?
* Linden Lab Official:Custom Name Program (beta) General Information & Custom Name Program
== Group related ==
* How do I change the title in front of my avatar's name?
* Linden Lab Official:Can I change a group's name?
== LSL related ==
*llGetObjectName
*llGetLinkName
*llRequestAgentData with DATA_NAME
*llGetObjectDetails with OBJECT_NAME
*llDetectedName
*llKey2Name
*llName2Key (proposal)
*Name2Key in LSL (LSL Library)
Name2Key

== Black DB Name2Key ==
After a lot of work in making this work, i finally managed to get the Name2Key search running with Second Life's avatar search.
Can also use Black DB Name2Key Website and use the Live name search.
UPDATED: Very sorry, just tonight i found out that i put llName2Key(name); instead of llName2Key(Name); The lower case `n` originally cause the name2key to search for the users UUID instead of the user who was being searched for.
== llName2Key Script ==
string black_db_name2key_service = "";
key QID;
string Name;
key UUID;
llName2Key(string name)
{
 QID = llHTTPRequest(black_db_name2key_service+llEscapeURL(name), [], "");
}
default
{
 state_entry()
 {
 llListen(0, "", llGetOwner(), "");
 }
 listen(integer channel, string name, key id, string str)
 {
 Name = str;
 llName2Key(Name);
 }
 http_response(key req, integer status, list meta, string body)
 {
 if(req == QID && status == 200)
 {
 UUID = (key)(llStringTrim(body, STRING_TRIM));
 if(UUID == NULL_KEY)
 {
 //None found
 }
 else
 {
 llOwnerSay(Name + "'s UUID Key = "+(string)UUID);
 }
 }
 }
}
NameTest

== Library ==
string previous_name;
key previous_key;
key owner_key; // to filter out owner chat
integer name_channel;
integer name_listener = 0;
key requestor;
key name_key_query;
key key_name_query;
integer pickChannel()
{
 return (integer)("0x"+llGetSubString((string)llGetKey(),-8,-1));
}
askForPreviousName(key agent, string prompt)
{
 name_listener = llListen(name_channel, "", "", "");
 llTextBox( agent, prompt, name_channel );
}
string nameFilter(string possibleName)
{
 string candidate_name = "";
 
 list name_list = llParseString2List( llStringTrim(possibleName, STRING_TRIM), [" ","."], [] );
 integer number_of_words = llGetListLength(name_list);
 if (number_of_words == 0)
 {
 llRegionSayTo(requestor, 0, "No name found");
 }
 else if (number_of_words > 2)
 {
 llRegionSayTo(requestor, 0, "That is too many words to be a name");
 }
 else
 {
 candidate_name = llDumpList2String(name_list,".");
 }
 return candidate_name;
}
default
{
 on_rez(integer unused)
 {
 llResetScript();
 }
 state_entry()
 {
 owner_key = llGetOwner();
 name_channel = pickChannel();
 vector ORANGE = <1 , 0.522, 0.106>;
 llSetText("Touch to translate a previous name", ORANGE, 1.0);
 }
 touch_start(integer num_touches)
 {
 requestor = llDetectedKey(0);
 if (owner_key == requestor)
 {
 askForPreviousName(owner_key, "Enter an old name:");
 }
 else
 {
 askForPreviousName(requestor, "Enter your previous name:");
 }
 }
 listen(integer channel, string name, key id, string message)
 {
 if (channel == name_channel)
 {
 previous_name = nameFilter(message); // will send any error message to the id
 if (llStringLength(previous_name) > 0)
 {
 state key_query;
 }
 }
 }
}
state key_query
{
 state_entry()
 {
 name_key_query = llRequestUserKey(previous_name);
 }
 
 dataserver(key queryid, string data) 
 {
 if ( name_key_query == queryid )
 {
 previous_key = (key)data;
 if (previous_key == NULL_KEY)
 {
 llRegionSayTo(requestor, 0, "'"+previous_name+"' is not a valid name");
 state default;
 }
 else
 {
 state name_query;
 }
 }
 }
 state_exit()
 {
 name_key_query = NULL_KEY;
 }
}
state name_query
{
 state_entry()
 {
 key_name_query = llRequestUsername(previous_key);
 }
 
 dataserver(key queryid, string data) 
 {
 if ( key_name_query == queryid )
 {
 if (data == previous_name)
 {
 llSay(0,"'"+previous_name+"' is the current name");
 }
 else
 {
 llSay(0,"'"+data+"' was '"+previous_name+"'");
 }
 state default;
 }
 }
 state_exit()
 {
 key_name_query = NULL_KEY;
 previous_name = "";
 previous_key = NULL_KEY;
 }
}
Name to agent ID API

One of the challenges that will be created by our allowing name changes is that anyone with an external database that uses name lookups will have to adjust by replacing or reindexing to use agent ids. This service is a publicly available rest endpoint to which a user submits a username/last name combination (or a username only with “Resident” the default last name), and is returned the agent_id associated with that name if it exists.
==API==
Base URL: https://api.secondlife.com/get_agent_id
Scheme: HTTP
===[POST] /get_agent_id ===
Provide the agent_id for a given username/lastname combination.
This API allows a user to post a username and lastname (or just a username with Resident the default lastname) and get back a JSON object with the agent id for that name (if it exists).
====Parameters====
Name 	Description
api-key (header, required)	Requests must include a valid API key header. API keys can be obtained at https://accounts.secondlife.com/manage_api_key.
body (body, required)) 	The JSON request body containing the username and lastname to inquire about. The last name is optional; if no lastname is provided ‘Resident’ will be used by default.Example:{
 "username": "Foo",
 "lastname": "Bar"
}
====Responses====
Response content type: application/json
Code	Description
200 	The agent_id for the submitted name was successfully returned.Example:application/json
{
 "agent_id": "00000000-0000-0000-0000-000000000001",
 "username": "foo",
 "lastname": "bar"
}
403 	Too many requests for this API key (more than 2 per second).
404 	The requested user doesn't exist in the system or the API key is invalid.Examples:0
{
 "error": "invalid_last_name",
 "message": "Last name Bar is invalid."
}
1
{
 "error": "not_a_user,",
 "message": "No such user Foo"
}
2
{
 "error": "invalid_api_key,",
 "message": "Invalid Key: 00000000-00000000-00000000-00000000"
}
405 	The request was not an HTTP POST request.
500 	An unexpected error that the application didn't handle occurred.
===Models===
Request{
username	string(Required; Username or first name of the user whose agent_id we seek)
lastname	string (Not required; Last name of the user whose agent_id we seek. Will default to ‘Resident’ if not provided.)
}
Error{
error 	string(Required; an error code unambiguously describing the error.)
message	string(Required; a human-readable description of the encountered error condition.)
}
NeighborList

==Message Layout==
{
	NeighborList High Trusted Unencoded
	{
		NeighborBlock	Multiple		4
		{	IP			IPADDR	}
		{	Port		IPPORT	}
		{	PublicIP IPADDR	}
		{	PublicPort IPPORT	}
		{	RegionID	LLUUID	}
		{	Name		Variable		1	}	
		{	SimAccess	U8	}
	}
}
==Usage and Notes==
Category:Messages
Neko

Neko means cat in Japanese, and in the physical world, it's not uncommon to see young teens in Japan dressing up "Neko" as a form of cosplay, inspired by Japanese manga and anime.
Within the boundaries of Second Life, a similar "virtual neko" phenomenon has occurred.
Nekos in Second Life are essentially human avatars who wear cat ears and a tail. A few have chosen to look more feral by wearing feline-colored skins, paw feet, or whiskers, but even in this form, they remain distinctly human, without the bulky masks or body shapes typically seen in the furry community.
To learn more about the history of Neko and find out how to be a Neko in Second Life, visit Virtual Neko in Second Life, a blog dedicated providing a central resource for the SL Neko community, featuring Neko resource pages, store lists, Neko "how to" guides, clothing and fashion, clubs, events, and sales.
Neko/ja

猫に扮したコスチュームの一種。
Neko は広い意味でファーリーの一種かもしれませんが、ファーリーが使うようなお面を Neko のアバターは使いません。素顔に猫耳、ひげを着け、毛皮、尻尾、爪を身に着けます。(いくつかは省略されるかもせしれません。) 服装は一般にゴス風です。
"Neko" というファッション用語は、現実世界でなく、Second Life 内で発生し、広まったように思われます。
Nerve Monster

Nerve monsters are a common type of followers. They are most frequently encountered in the sandboxes, the combat zones, and sometimes Mohrr.
==Variations==
Most often, nerve monsters are red in color, but occasionally are green, purple, white, or transparent white (usually called "ghost nerve monsters". Their size varies but, including tentacles, they usually have the width of a broad-shouldered man. The nerve monster imaged at left has standard coloration and size.
==See Also==
* Follower
* Follower Escaper
Nesting of Child Prims in a Parent

== Idea / Feature request: ==
Possibility to use NESTED Parent/Child Prims.
If in the current SL edition we link child prims to a parent, we cannot keep a linked child set together.
Say I want to build a car, and the steering wheel is built like a unit of 3 linked prims.
When I now want to link the steering wheel to the car, the 'unit' "steering wheel" gets lost, and ends up as 3 separate prims.
So if I would like to replace the steering wheel, by unlinking the car, I end up with 3 separate childs, instead of 1 steering wheel prim.
If it would be possible to add 'nested' child prims this problem would be solved.
The structure of a linked set then could/should behave more like a TREE, rather than the current 'linear' structure.
Maybe we need new functions for this, to be able to discern the level of "nested-ness".
Example: Say we have this structure:
 PARENT (link #1) = 
 { ROOTPRIM + 
 CHILD 1 (link #2) = PARENT OF: { CHILD 1a (link #3) + CHILD 1b (link #4)}
 CHILD 2 (link #5) = PARENT OF: { CHILD 2a (link #6) + CHILD 2b (link #7)}
 }
Now suppose we want to edit CHILD 2, because CHILD 2b should be replaced by a new prim.
In the current situation this means: CTRL+SHIFT-L (unlink complete set)
but now also all childs from CHILD 1 get un-linked too.
Ideally, it would be most convenient if when we unlink the ROOT PARENT PRIM we would get to the next linked levels.
So in the example above: ideally UN-linking the PARENT would give us : PARENT, CHILD 1, CHILD 2, where we can go further by UN-linking e.g. CHILD 2 into 2a and 2b by repeating our UNLINK session. 
Please consider this idea and give it your thoughts!
Regards,
--Tjako Schumann 05:03, 26 September 2007 (PDT)
I would just like to second this suggestion - the current system of "total unlinking" is really a problem when assembling pre-built parts. Janita Collins
NewFileAgentInventory

POST:
<llsd>
	<map>
		<key>asset_type</key>
		<string>texture</string>
		<key>description</key>
		<string>(No Description)</string>
		<key>folder_id</key>
		<uuid>43b352d4-5458-465e-bb6c-a3159dea7540</uuid>
		<key>inventory_type</key>
		<string>texture</string>
		<key>name</key>
		<string>ripple</string>
	</map>
</llsd>
Response:
<llsd>
	<map>
		<key>state</key>
		<string>upload</string>
		<key>uploader</key>
		<string>https://sim8251.agni.lindenlab.com:12043/cap/d0a30292-8506-7cbe-f934-f1af69a233ff</string>
	</map>
</llsd>
NewFileAgentInventory CAP

POST
<llsd><map><key>asset_type</key><string>sound</string><key>description</key><string>(No Description)</string><key>folder_id</key><uuid>cb06cb32-272a-441c-926d-a2e0b6147745</uuid><key>inventory_type</key><string>sound</string><key>name</key><string>itmnd chorus test</string></map></llsd>
Response:
<llsd><map><key>state</key><string>upload</string><key>uploader</key><string>https://sim3507.agni.lindenlab.com:12043/cap/8792958d-2d39-6660-48e3-2de8e43e78be</string></map></llsd>
NewLine

__NOTOC__
== Function: string NewLine(string ); ==
Returns a string with all "\n" seperators replaced by 'new line' escape codes.
The advantage of this function is the use of one integer and one string.
== Specification ==
string NewLine(string message)
{
 integer newlinepos = llSubStringIndex(message, "\\n");
 while(newlinepos >= 0)
 {
 message = llDeleteSubString(message, newlinepos, newlinepos + 1);
 message = llInsertString(message, newlinepos, "\n");
 newlinepos = llSubStringIndex(message, "\\n");
 }
 return message;
}
A shorter alternative:
string NewLine(string message)
{
 list lWords = llParseStringKeepNulls(message, ["\\n"], []);
 return llDumpList2String(lWords, "\n");
}
== Example ==
Example used in a prim to generate floating text.
string NewLine(string message)
{
 integer newlinepos = llSubStringIndex(message, "\\n");
 while(newlinepos >= 0)
 {
 message = llDeleteSubString(message, newlinepos, newlinepos + 1);
 message = llInsertString(message, newlinepos, "\n");
 newlinepos = llSubStringIndex(message, "\\n");
 }
 return message;
}
default
{
 on_rez(integer rez_param)
 {
 llResetScript();
 }
 state_entry()
 {
 llSetText("", <1,1,1>, 0.0); 
 llListen(1, "", llGetOwner(), "");
 }
 listen(integer channel, string name, key id, string str)
 {
 str = NewLine(str); 
 llSetText(str, <1,1,1>, 1.0); 
 }
}
In chat,
"/1 test test test" causes the prim to display:
test test test
"/1 test\ntest\ntest" causes the prim to display:
test
test
test
New Berlin/de

newBERLIN - Berlin 1:1 in Second Life®. In der virtuellen Metropole könnt ihr nicht nur Berliner Bauwerke sehen, sondern auch Kultur und Events erleben und echte Berliner genauso wie Deutsche und Leute von überall auf der Welt kennenlernen. Kommt vorbei und lernt die Hauptstadt und ihre Bewohner kennen!
== Links ==
* BerlinIn3D.com
New Citizens Incorporated

NCI is a voluntary association, dedicated to providing information, education and assistance to Second Life users (new and old), in order to maximize the benefits that they can gain from Second Life. NCI believes that new users who are better educated, supported and prepared benefit all of Second Life. NCI does not operate for profit and is not motivated by any desire for monetary gain. 
===Group Information and Links===
* NCI Website
* NCI Forums
* NCI Wiki
New Hover Tip default behavior

Please be careful when editing .ini that you don't change something else that you might need.
# View menu > select "Show Hover Tips" option (the default setting) now shows Hover Tips only for objects with which one can interact.
# View menu > deselect "Show Hover Tips" option works as before; no Hover Tips will be shown
# To view Hover Tips for all objects (the old default behavior), add the line "ShowAllObjectHoverTip TRUE" to the settings.ini file, found in the following locations:
#* Windows: Documents and Settings\USERNAME\Application Data\SecondLife\user_settings
#* Mac OS X: Users/USERNAME/Library/Application Support/SecondLife/user_settings
# To view Hover Tips only for Land, add the line "ShowLandHoverTip TRUE" to the settings.ini file instead.
IMPORTANT NOTE: Be sure to use a TAB character between the option name and the "TRUE" setting. Then, after editing the file, restart Second Life to see the Hover Tips as desired.***
You can find your settings.ini file with a Start/Search
Hover Tip, New behavior
New Hover Tip default behavior/de

Sei vorsichtig, wenn Du *.ini - Dateien bearbeitest, damit Du nicht etwas anderes veränderst, das Du vielleicht noch brauchst.
# Wenn Du im Menü "View" die Option "Show Hover Tips" auswählst (die Vorgabeeinstellung) werden jetzt Hover Tips nur bei Objekten angezeigt, mit denen Du interagieren kannst.
# Das Abwählen der Option im Menü "View" > "Show Hover Tips" funktioniert wie früher: es werden keine Hover Tips angezeigt
# Um Hover Tips für alle Objekte (das alte Standardverhalten), füge die Zeile "ShowAllObjectHoverTip TRUE" der Datei settings.ini hinzu, die an den folgenden Orten gefunden werden kann:
#* Windows: "Dokumente und Einstellungen\USERNAME\Anwendungsdaten\SecondLife\user_settings
#* Mac OS X: Users/USERNAME/Library/Application Support/SecondLife/user_settings
# Um Hover Tips nur für Land anzuzeigen, füge stattdessen die Zeile "ShowLandHoverTip TRUE" zu der Datei settings.ini hinzu.
WICHTIGER HINWEIS: Sei sicher, dass Du zwischen dem Namen der Option und der "TRUE" Einstellung die Tabulatortaste TAB verwendest. Dann, nach dem bearbeiten der Datei, must Du SecondLife erneut starten, um die Hover Tips wie gewünscht zu sehen.***
Du kannst die Datei "settings.ini" auch über Start/Suche finden
New Hover Tip default behavior/es

Please be careful when editing .ini that you don't change something else that you might need.
# View menu > select "Show Hover Tips" option (the default setting) now shows Hover Tips only for objects with which one can interact.
# View menu > deselect "Show Hover Tips" option works as before; no Hover Tips will be shown
# To view Hover Tips for all objects (the old default behavior), add the line "ShowAllObjectHoverTip TRUE" to the settings.ini file, found in the following locations:
#* Windows: Documents and Settings\USERNAME\Application Data\SecondLife\user_settings
#* Mac OS X: Users/USERNAME/Library/Application Support/SecondLife/user_settings
# To view Hover Tips only for Land, add the line "ShowLandHoverTip TRUE" to the settings.ini file instead.
IMPORTANT NOTE: Be sure to use a TAB character between the option name and the "TRUE" setting. Then, after editing the file, restart SecondLife to see the Hover Tips as desired.***
You can find your settings.ini file with a Start/Search
Category:Articles for Spanish translation
New Pride Land Ferry Schedule

The following is the schedule for passenger ferry service operated by MASONLines in the New Pride Land continent, effective 4th February, 2009. All times shown are minutes past the hour.
==Route Map==
=="Blue Line"==
Service between Tiki Village and Badpuppy. Plans to extend to Hylas & Exotica in 2009.
===Westbound Service - Badpuppy to Tiki Village===
Badpuppy	Mission Beach (arr)	Mission Beach (dep)	Tiki Village
:43 	:47 	:01 	:04
:13 	:17 	:31 	:34
===Eastbound Service - Tiki Village to Badpuppy===
Tiki Village	Mission Beach	Badpuppy
:05 	:08 	:13
:35 	:38 	:43
=="Red Line"==
Southeastern Local Service between Mission Beach and Ewing Arts. 
NOTE: Service suspended from 1/1/09
=="Green Line"==
Northeastern Local Service Between Mission Beach and Selene (Under Construction)
=== Northbound Service - Mission Beach to Selene ===
Mission Beach	Sparta	Troy	Thrace	Selene
:22 	:24 	:26 	:28 	:
:52 	:54 	:56 	:58 	:
=== Southbound Service - Selene to Mission Beach ===
Selene	Thrace	Troy	Sparta	Mission Beach
: 	:28 	:30 	:32 	:34
: 	:58 	:00 	:02 	:04
New Resident Services

== Welcome to the New Resident Services (NRS) Wiki Page ==
== Founder ==
:*Treacle Darlandes
=== Active Co-Owners ===
:*Eoleon Elcano
:*BΞNJI RΞZ
== Total Group Members == 
:*4000+
== Group Charter ==
:Community help for new & older SL Residents. This is a G rated group, which means no adult topics or language. Please respect our choice of maturity rating. Do feel free to say 'Hi' in the group or ask questions. No spamming, no commerce. Thank you. :-) 
:*Home to New Resident Services help group: http://slurl.com/secondlife/Lawst%20Paradise/136/26/22
== Mission Focus and Statement ==
:The New Resident Services group was set up by Treacle Darlandes to work within the ROF Organization, to play a role helping new people and those who wish to learn more technical elements of Second Life®. Treacle has a lot of experience in Second Life®, formerly Manager at Help People Institute (HPI), now SecondAbility Mentor (RHN) and White Tiger Mentor (RHN). The association of New Resident Services with White Tiger Mentors is that as two separate groups they work side by side to assist new Residents or even any seasoned Residents in need. Together we will co-ordinate training for Helpers, pool our knowledge and resources and continue to plan learning classes and live music events. NRS and WTM Members will support each other as Partners, Associates and Friends in helping, greeting, mentoring and any other associated activities that Members from each group would wish to be involved in, whilst retaining individuality both in terms of status and goals.
==Useful Links==
*New Resident Services is on Facebook.
*White Tiger Mentors Wiki Page
Category:Second Life Groups
Category:Second Life Volunteers
New Transaction History

= L$ Transaction History Page Updates =
The L$ Transaction History web page allows Second Life Residents to view recent L$ transactions involving their account. As business has grown in Second Life, this page has become challenging for some Residents to use. As a result, we have made significant updates to support a higher number of transactions per account. Along with those changes, some small updates were made to the functionality of this page. 
Last week, we rolled out this updated page. However, based upon user feedback, we learned that these changes had more of an impact than expected. As a result, we rolled back those changes. For the next two weeks, we are going to leave the old Transaction History page up for you to use while making the new Transaction History page available for Resident feedback. The new page will be pointing at production data, just like the old page. 
We would like to get your feedback on this JIRA BUG-5664 before April 30, 2014. We will be updating the new page to incorporate the feedback we receive, and will release an updated version before disabling the old page.
== Current functionality ==
The old Transaction History page supports a variety of basic functions to allow Residents to pull their data. Here’s a summary of the current functionality.
* 32 days of transactions are shown (though we communicate that only 30 is shown)
* The date range to display is configurable within the 32 day period
* Check box allows showing/not showing L$0 transactions
* Results can be exported in XLS and XML format
* Subtotal is shown for the currently selected date range
* The in page results show a portion of the transaction ID, but the full ID is only available in the download
* Displays up to 500 transactions
* Default date range is today’s date
== Updated Page ==
The new Transaction History page was created to allow more than 500 transactions to be displayed for Residents with very active businesses. In addition, the following new functionality will be introduced:
* Results can be filtered by a specified string (e.g. show only “Gift” transactions)
* Results can be exported as a CSV file, an Excel compatible file
* Results now include all transactions from the date range selected (no longer 500 or less)
We have summarized the outstanding issues with the new page in JIRA. Please comment on BUG-5664 if you have additional feedback.
New York Microcontinent

New York is a Microcontinent located at Coordinates 959-963/1161-1166, inside Grid Sector I11, Little Northern Ocean. Its temporary name is A060.
== Strcture ==
It is made of 20 sims. This is not enough for A60 to be considered a Continent, even if its Geographic features are highly developed. All sims are themed of the ols steampunk technology that once existed in New York.
== Geography ==
This microcontinent is a real masterpiece of Geography. It has all what is needed for a real country to have. There are high mountains in North, permanently covered with snow (snowlands) and a maximum Altitude of 77 meters. From these high mountains, rivers flow all over the land. These are rivers, navigable with small boats, not sea water. The central part of land is made of low hills, passed by many rivers. It also includes plains in urban areas.
Buildings are all old-style.
A large transportation system is present. There are a lot of roads. Only a few of them are covered with asphalt, the vast majority are paved roads or country roads. New York Railway is the best way to visit the microcontinent. Automated trains circle along the railway from time to time. And not only trains. There are trams in urban places. Sailing is possible with small boats.
== Land Status ==
This is a very friendly place. There are no ban lines, no entity orbs, no restrictions for visitors. More often, visitors receive welcome messages. Residents are friendly. Protected Land covers a large surface. Unfortunately, there is Unused Land that covers many parcels.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Oceans