nyuuzyou/wikis huggingface dataset:
Coach Class Request

Do you have an interest in a specific subject or skill and would like to make a request for this class to be taught by Mentor Coaches? Add your requests below! Remember to thank your Coach for fulfilling your need if the need is met! :) Coaches: if you would like to fulfill a need, mark your interest beside their comment so they know you are interested and may host a class soon!
@Coaches: Please also have a look at Talk:Classes Offered By Mentors.
----
* Chaos Mohr hosted a class about the Tao of Volunteers which I considered as very helpful. I'd like to request this class beeing hosted by either Chaos Mohr himself or another Mentor Coach who might want to contact him for colaboration. The Tao seems to very easy to handle, but staying calm and friendly in the face of abuse and while someone is insulting you and/or your friends can be difficult to handle. This class provided techniques on how to deal with these situations in an appropriate way. --Zai Lynch(talk|contribs) 15:52, 14 May 2008 (PDT)
* A class about Land Management. Bugs out there (e.g.: Got ghost prims, what to do?"), extended anti-griefing options (un/freeze, ban, access list,...), deeding land to group and consequences of it, etc. --Zai Lynch(talk|contribs) 15:52, 14 May 2008 (PDT)
* I would like to request a class on how to develop 3d documentation of alien DNA using the Second Life Grid's building tools. -George Lindenormal
** George, I would be happy to conduct this class. However, the cost of importing samples and documentation from the three nearest galaxies has proven to be prohibitive in the past. If at least three (3) more residents are interested in this topic, I'll begin compiling the necessary course resources. - Nava Muni
* I would like to request a class on how to build detailed structures e.g. an aeroplane using the building tools. - i request that it happens during a week day at 3pm server time because the 2 oclock sesion is too early for me to be able to get to. - Nanuika Rau
CoarseLocationUpdate

==Message Layout==
{
	CoarseLocationUpdate Medium Trusted Unencoded
	{
		Location	Variable
		{	X		U8	}
		{	Y		U8	}
		{	Z		U8	}	
	}
	{
		Index 		Single
		{	You		S16	}
		{	Prey	S16	}
	}
}
==Usage and Notes==
This packet is used to populate the mini-map with the green indicators to represent where agents are. Z axis is multiplied by 4 to obtain true Z location. This still leaves the problem of the Z axis being limited to 1020m in height. Anything above that height overflows the U8 and is reported as 0.
The 'You' and 'Prey' index values are to tell the client what location in the set is the logged in agent, and if they are mapping or following somebody, what index value in the set that person is. Index values start at 0, where 0 is the first item in the list. If locations for 'You' or 'Prey' aren't present in the Location blocks, their indices are -1.
==Official Client Behavior==
The mini-map avatar list is cleared every time this message is received.
The client does not draw the green dot that represents them on the mini-map, this is the reason for the You index. Prey index causes the client to draw a red circle in place of the little green indicator.
Category:Messages
Coca-Cola

==The beginning==
In April 2007, Coca Cola launched a contest for a virtual Coke machine that was to be utilized in Second Life. The contest invited people to design a Coke dispensing machine for use in Second Life. Dance Machine
Coke's initiation into Second Life was spearheaded by new marketing consultancy crayon, which devised the strategy for the soft drink marketer and helped it tap an advisory council made up of Second Life residents and designers which selected the winner of the competition.
Michael Donnelly, Coke's director of global interactive marketing said "the Virtual Thirst platform is something that could be extended into offline media and moreover, into portable media games, wireless and other emerging platforms. The concept could eventually tie into or complement Coke's current campaign "The Coke Side of Life." He characterized the Second Life play as a learning experience." And Indeed it was.
==The Winner is...==
The winning concept, as selected by Second Life residents, was Ann Marie Mathis' "Magic Coke Bottles" concept: Scattered around Second Life's environments were over a dozen bottle-shaped puzzles, which when successfully solved immerse all nearby in a unique and refreshing virtual experience. The avatar that solved the puzzle was automatically given one of several cool prizes which they can then freely copy and distribute to others. The Coca-Cola Company unveiled the winning design from its “Virtual Thirst” competition on November 8, 2007 at 1:00 pm EST on Crayonville Island. The problem was the puzzles were over 100 prims and therefore about 20 or so were rezzed.
 * Virtual Thirst Case Study Video - click here
 * Audio from Unveiling Event (30 minutes) - 14 MB MP3 File
 * Download / Photo - Ann Marie Mathis, winner of the Virtual Thirst competition.
 * Virtual Thirst Photos - Virtual Thirst Photos
 * Prototype and Diary Videos: Videos
Virtual Thirst the website for the Coke sim.
==The licensing gift==
On the 7th of June 2007 Vint Falken received an e-mail from SLexchange (now Xstreet SL) that his/her Coke outfit was in violation of Coca-Cola’s trademark and the listing was taken down from their website. So, he/she contacted C.C. Chapman who had handled the Virtual Thirst campaign, and talked to Coke. June 22, 2007 SLexchange sent out the following: ‘ We have spoken to Coca-Cola and they have released their trademark to SL Merchants.
What does this mean?
Since Michael Donnelly is Coke's director of global interactive marketing, it covers the global brands. Its means that (to my understanding) that all Coke brands can be made in world without fear of infringment. And he did allow anyone to continue to make coke Products.
Code Sizer

= How Small Is That Code =
Q: Want to know how small that code is?
A: The most accurate, least misleading technique we have found is as follows.
First compile & run this brief & clear & conventional (though neither clever nor fast nor small) script:
This code is not accurate for use with mono compilation. An example of code similar to this for use with mono compilation is on the talk page.
// http://wiki.secondlife.com/wiki/Code_Sizer
integer unspent = 16384; // the well-known available size of byte code plus heap plus stack
integer wasted = 313; // the well-known byte size of this script before you add source code to it
// Count the bytes newly occupied by new byte code when you added source code to this script.
integer getSpentBytes(integer spendable)
{
 return spendable - llGetFreeMemory();
}
// Print the bytes spent when you added code to this script,
// whenever you Save or Reset this script.
default
{
 state_entry()
 {
 llOwnerSay((string) getSpentBytes(unspent - wasted));
 }
}
The integer zero should be the result printed when you first try this.
See how that works?
This code quotes the well-known available size of byte code plus heap plus stack. This code quotes the well-known size of itself. This code calculates the difference between those two quotes, i.e., the count of bytes that should be free until you add more code. This code prints zero so long as those well-known sizes do not change (and prints zero in the unlikely test case of the change in wasted exactly canceling out the change in unspent).
Now you add code, and run the script again. For example, suppose you create a second copy of the getSpentBytes routine, giving its name some otherwise unused spelling like getSpentBites. Then you will see the second copy costs 47 bytes. A third copy costs the same, another 47 bytes for a total of 94 bytes. And so on.
Get it?
Now you can easily & instantly measure how small any code is.
Note: Take care to avoid falling into the easy error of printing the llGetFreeMemory count of bytes before and after you delete the last function of the script, as if that difference measured the byte code space cost of a function. Measurements taken that way overestimate the space cost by four bytes, because adding the first function to a script spends an extra 4 bytes to create the Function Block, aka the User Function Lookup Table, as doc'ed when you search for "GFR" in such places as the 2007-07-06 edition of http://www.libsecondlife.org/wiki/LSO.
= See Also =
Functions
llGetFreeMemory - count bytes of code plus heap plus stack spent by the script as yet
Scripts
Code Racer - quickly see if one version of code usually runs faster than another
Efficiency Tester - run as long as you please to count approximate milliseconds of run time with every more accuracy
Code highlighting

== wiki.secondlife.com ==
If you're creating pages on this wiki that include external code examples (like LSL or HTML), it's highly useful to enclose the code between tags that retain formatting and other desirable attributes, like colorized syntax.
=== Tags ===
These tags are actively being used.
* - Fixed-width text. Used in generic scenarios, and when others are too restricting for whatever reason.
* <lsl> - Widely used on the LSL Portal and other LSL scripts that appear on-wiki.
* <html4strict> - Use this when you need to highlight HTML code snippets, such as for use with Shared Media.
* - Used not just for simpler, single-line code, but user input that needs highlighting, as described in the Knowledge Base Style Guide.
For more tags, see the Parser extension tags on Special:Version. Some tags are possible because of GeSHiHighlight.
=== Examples ===
These pages use code highlighting tags extensively.
* :Category:LSL Library - Click a script page to see how it appears with the <lsl> tag.
* Shared Media LSL Recipes - Becky Pippen mentioned a limitation of the <lsl> tags: namely, you seemingly can't highlight code inside, so she's using instead.
* Shared Media wrapper - Torley Linden learned from Khepri Contractor that the <html4strict> tag works.
== community.secondlife.com ==
When creating a post, from the editing toolbar, click , then paste in your script.
Users of Firefox (with Greasemonkey installed) and Google Chrome can install LSL posting tool for community.secondlife.com created by Cerise to get LSL highlighting on the forums. This is especially useful in the Scripting and Scripting Library forums where LSL scripts are shared.
To use the highlighter, paste in your script with the button as usual, then press the button to highlight. Use if you want to remove the highlights.
Coeur Microcontinent

Coeur (or A094 on its transitory name) is a Microcontinent detected at Coordinates 556-559/1116-1123, Grid Sector E11, Far West Ocean. 
== Structure ==
It is made of 11 or 12 sims, all sharing the name Coeur. This is a French microcontinent, but you can find your way through even if the only language you know is English. 
== Geography ==
Many parts are urban. Buildings are in an old style and usually they are connected one to another, so they have common walls. In some places, there are passages over the roads There are shops (boutiques).. Roas system covers the entire microcontinent. They are built for horse traction, not for cars.
Geographic features are more realistic and include hills.
Rural areas are also present. A good destination is the large garden found in sim Provence Coeur Est 2.
== Land Status ==
It is very easy to walk along this microcontinent.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Oceans
Collaborative Building

=== Feature Design Document ===
See below.
=== Functional Spec ===
(none)
=== Test scripts ===
(none)
=== Discussion for future improvements ===
(none)
=== Relationship to other features ===
=== User Guides ===
(none)
=Collaborative Building=
==Allow anyone to move (Edit window, General tab)==
===Collaboration this allows:===
Allows someone to rearrange your stuff. 
===Collaboration this does not allow:===
Does not allow modifying the object itself (shape, color, etc.) nor modifying the contents.
===Protection this affords===
Only the objects your choose can be modified.
===Drawbacks===
You need to remember to turn this off or strangers can move your stuff.
==Friends - Can modify my objects==
===Collaboration this allows:===
* This gives your friend the ability to modify your objects. 
===Collaboration this does not allow:===
* Your friend cannot change the next owner permissions. Only the owner can do that.
* Your friend cannot change the contents of your objects, However, your friend can take the object, then rez it again, and can then modify items in the contents(if the next owner permissions were set).
===Scenarios best suited by this===
Building objects or buildings that do not require scripts or other items in contents.
===Protection this affords===
The other user cannot modify scripts in your object.. most of the time. If next owner permissions are permissive, the friend can take and rez and then owns modifiable copies of the script.
===Drawbacks===
* Your friend cannot help you fix your script.
* Your friend can modify any of your items, and delete your content.
==Groups - Object Management - Manipulate (move, copy, modify) group-owned objects==
===Collaboration this allows:===
This allows someone to modify a script in your objects if the script is set to "share with group".
===Collaboration this does not allow:===
none?
===Scenarios best suited by this===
Large collaborative builds.
===Protection this affords===
Only the people with the Manipulate abiliity can modify items.
===Drawbacks===
Turning on the "share with group" flag for each box, script, notecard is tedious.
Collar

A collar resembles a popular accessoire in Second Life®. 
It can be a "simple" piece of jewelery, often worn by neko or furry avatars, though many collars are scripted in order to allow the wearer certain features. These are especially popular within the role play community of Second Life. Quite common features let the wearer grant certain permissions to a third person, like animating the own avatar, limiting it's mobility, tracking if the collar is worn or not, etc.
These kinds of collars are sometimes equipped with an API to allow interaction with other devices.
Besides several commercial closed source releases, there is also a popular set of open source scripts available for content creators. The so called OpenCollar scripts are provided and documented at Google Code. Also an open LSL Protocol, called LockMeister System, is available for developement in order to enhance compatibility to other products.
Such collars might also allow features which may require the so called Restrained Love Protocol, which is integrated in some Third-party Viewers.
It is not clear if or which of these scripted collars are counted amongst adult content, which would only allow them to be sold at regions having an adult region rating. However, it is clear that they aren't allowed to be advertised with adult content keywords, when they're supposed to be sold on PG or Mature regions.
Collar/hu

A nyakörv Second Life-ban legtöbbet résztvevő tárgy®. 
Lehet egyszerű prímből készült díszítésként, egészen a legbonyolultabb, scriptelt BDSM eszközként, sculptból, meshből modelezve.
Legtöbbször neko vagy furry avatarok általános viseletében találhatóak, mint kiegészítő, java részük pedig erősen scriptelt, mellyel a viselője több lehetőséghez jut. Nagyon elterjedt és közkedvelt tárgy még a szerepjátékos közösségeken belül is. Általános lehetőségként a viselője különböző jogokat adhat egy harmadik félnek, mint pl:
*avatar animálása
*limitálhatja viselője mozgás szabadságát
*nyomon követheti cselekedeteit
*etc...
Ezek a nyakörvek általában egy olyan apival jelennek meg, mely megengedi az interakciót más eszközökkel is.
Néhány nyakörv el van látva különleges funkciókkal, mint pl:
*Opencollar scriptek 
*Néhány open LSL protokoll mint LockMeister System
*
Sok nyakörv rendelkezik még egy igen kiválló lehetőséggel, melyhez külön Third-party Viewer szükséges.
Ilyen az RLV avagy Restrained Love Protokoll
Ha nem vagy tisztában melyik nyakörv sorolható be a felnőtt kategóriába, bizonyosodj meg arról, hogy a sim, melyen kapható, adult besorolásban található.
Collective Action Against TPV policy

Please edit this page to add any actions/statements that might or should be considered an option for the open source developers as a collective, signed with our names.
In no particular order.
* Make changes to the current TPV policy and present those to Joe Linden.
* Same as above, but as iterative process:
*# Propose changes to the current TPV policy on the wiki.
*#* For an example, see the proposed reformulation of 7d, the liability clause.
*# Present those changes to OpenSource-Dev and ask everyone (including LLMaybe Joe Linden can make sure legal is aware of it.) to voice their objections (if any).
*# Modify proposal to take care of objections.
*#* The objectors (and everyone else) can partake in that—it's a wiki!
*# Repeat 2-3 until no (major) objections are left
* Collectively state that we will stop supporting Snowglobe until the current problems with the TPV policy have been resolved.
* Do absolutely nothing
* Formally submit TPV Concerns with signatures, in some fashion. (It needs to be updated)
----
Footnotes
College of Scripting Music and Science

On the first day, Keystoner logged in. He traveled across the lands of Second Life, and saw that it was good. He created a parcel in the region of Horsa and called it College of Scripting Music and Science.
And on the second day, Keystoner built a floor and four walls and saw that it was good. He separated North from South and called North 'Orientation Area' and South the 'First Floor'.
And on the third day, Keystoner built 7 more floors and saw that they were good. He filled them with tutorials, illustrating a wide variety of LSL functions.
== Vision Statement ==
The college was created for the purpose of helping Second Life and it's residents, so that the average user can come and learn to script in LSL.
Residents can learn here how to add function to their objects. Using scripts, objects can be animated and be interacted with and serve purpose to the owner's needs.
Tutorials are added periodically, and spread out through categorized floors. We have 8 floors with over 600 tutorials. There is also a music section, teaching the basics of musical notes, scales, and chords; music functions and a playable piano included.
Physics section to come...
== College Group ==
Group Guidelines
The group is for Scripting questions and answers about scripts you are working on. 
We can help you figure out how to make things, but do not request completed scripts. Please assist us in making this group useful to teach and learn scripting. Lets keep focused on scripting.
To be invited to group you must visit the college.
== Owners ==
* 
* 
* 
== Links ==
* Youtube Channel
== See also ==
* Resident Help Network Portal
Category:LSL
Category:Resident Help Network
Category:Institutions
Category:Education
College of Scripting Music and Science/Group Guidelines

=College of Scripting Music and Science=
==Group Channel Guidlines==
Hi Everyone and welcome to the College group.
This group is designed to help you become a scripter.
We have thousands of members, so group chat must be regulated. We ask you to focus on scripting help only, in group chat. That means you should not be asking to share or trade ready-made scripts. This is not a script collection group; there are other groups for that purpose. Please feel free to ask any questions for scripts you are working on.
We cannot distinguish between a product advertisement and your advice to visit a website link, nor will we visit every link to make sure it's not spam.
Posting a website address that isn't the scripting wiki will be subject to banning.
The following are the formal guidelines to be followed in the College of Scripting, Music and Science Group IMs
Please remember, the script group has thousands of members and is not a general conversation channel. Make sure to use the channel only for scripting questions. Questions and concerns that do not need to be broadcast to the whole mentor and learner group should be brought up in an instant message direct to the person you are addressing.
===Use Channel for Helpful Reference===
*Do ask specific questions regarding scripts and scripting.
*Do encourage the use of the scripting tutorials at the College of Scripting, Music and Science.
*Please don't spam the chat with requests for products or products for sale.
*Please don't ask for scripts that are for any type of griefing.
*Do file an Abuse Report via Help >Report Abuse... for abuse, harassment or griefing concerns.
===Use Channel Etiquette===
*Do be courteous to your fellow group members in the group channel.
*Do avoid general conversation... Try other venues for friendly chatter such as a Private IM
*Do avoid disputes. Agree to disagree! Please keep debates in Private IMs.
*Please remember there's no need to respond if your answer is "sorry I don't know."
===Consequences===
College of Scripting, Music and Science Group Members are expected to know the group channel guidelines and abide by them. If a Member does not follow the guidelines they may be removed from the group, with or without warning.
== Joining the Group ==
To be invited to group you must visit the college.
== See also ==
* College of Scripting Music and Science
* SLetiquette
Category:Second Life Groups
Collision message sender

Receiving a message every time that you step on a prim is annoying, so this script uses a short name store to check that the avatar has not been sent the message for at least 10 minutes.
As an avatar stands on or hits against the prim, the timer is reset to a further 10 minutes, at the end of the timer period, the name list is cleared.
<source lang="lsl2">
// The script written by Taff Nouvelle.
// Use it in any way that you want
// but please leave this header intact.
string message = " Merry Christmas "; // put your message here.
list users;
string user;
default
{
 collision_start(integer num_detected) // check for an avatar colliding with the prim.
 {
 user = llDetectedName(0);
 if (llListFindList(users,[user]) == -1)// look at the list, if the name is not there,
 {
 llSay(0, message + user); // send the message to the detected avatar.
 users += user; // add the users name to a list so they only get the message once.
 llSetTimerEvent(600); // change the number for the number of seconds before clearing the list.
 }
 }
 timer()
 {
 llSetTimerEvent(0); // turn the timer off
 users = []; // clear the list
 }
}
Color-to-Vector Tool

=====Say the Prim's Color Vector=====
This script is useful as a WYSIWYG color reporter. Each time the prim's color changes, the color vector is chatted to the owner. Note, it reports the color of face 0(zero) by default.
integer FACE = 0;
default {
 changed(integer change) {
 if (change & CHANGED_COLOR) llOwnerSay("Color Vector = " + (string)llGetColor(FACE));
 }
}
This script shows it hovering over the prim as well for less chat spam and longer display value.
default {
 changed(integer change) {
 if (change & CHANGED_COLOR) llSetText("Color Vector = " + (string)llGetColor(0),<1.0,1.0,1.0>,1.0);
 }
}
Category:LSL Examples