Second Life Wiki - User contributions [en]

User:James Benedek

2013-01-09T00:11:08Z

James Benedek: /* Now: */

[[Image:Jamesbenedek.jpg|thumb|512px|James Benedek's Profile Pic]]

Second Life profile - [https://my.secondlife.com/james.benedek James Benedek]

==The Past:==
-Joined Second Life on 10/19/2006.

-Became a Official Bug Hunter & Jira Bug Reporter in 2007 (later testing Havok 4 Beta and Open Grid Beta).

-Built the Red Cross Island region in 2007 for the real world Danish Red Cross.

-Founded the 2142 military combat group in 2007.

-Released many freebies: scripts, objects clothes since 2007 including the Capture the Flag system that is still widely used within the SL Combat Community.

-Became a Second Life Volunteer Mentor in 2007.

-Became a Second Life Volunteer Coach in 2008.

-Built all of the infustructure for the Secondlife 5th Birthday regions in 2008.

-Took a break from Second Life on 26/10/2008 till late 2009 leaving my good friend LordBob Boa to thankfully manage of the group 2142.

-Started learning to 3D model using Autodesk 3DS Max in 2009.

-Founded the shop Urban Scene in 2010.

-Switched to using Autodesk Maya to 3D model in 2010.

==Now:==
-Spend most of my time working on Mesh for 2142.

You can visit 2142 at: [http://maps.secondlife.com/secondlife/Westminster/128/128/10/ http://maps.secondlife.com/secondlife/Westminster/128/128/10/]

''or''

Join the 2142 group at: [http://www.2142sl.info/join http://www.2142sl.info/join]

''or''

See Urban Scene mesh items at: [https://marketplace.secondlife.com/stores/123798 https://marketplace.secondlife.com/stores/123798]

[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:LSL Mentors|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]
[[Category:Second Life Birthday Staff]]

User:James Benedek

2013-01-09T00:10:31Z

James Benedek:

[[Image:Jamesbenedek.jpg|thumb|512px|James Benedek's Profile Pic]]

Second Life profile - [https://my.secondlife.com/james.benedek James Benedek]

==The Past:==
-Joined Second Life on 10/19/2006.

-Became a Official Bug Hunter & Jira Bug Reporter in 2007 (later testing Havok 4 Beta and Open Grid Beta).

-Built the Red Cross Island region in 2007 for the real world Danish Red Cross.

-Founded the 2142 military combat group in 2007.

-Released many freebies: scripts, objects clothes since 2007 including the Capture the Flag system that is still widely used within the SL Combat Community.

-Became a Second Life Volunteer Mentor in 2007.

-Became a Second Life Volunteer Coach in 2008.

-Built all of the infustructure for the Secondlife 5th Birthday regions in 2008.

-Took a break from Second Life on 26/10/2008 till late 2009 leaving my good friend LordBob Boa to thankfully manage of the group 2142.

-Started learning to 3D model using Autodesk 3DS Max in 2009.

-Founded the shop Urban Scene in 2010.

-Switched to using Autodesk Maya to 3D model in 2010.

==Now:==
-Spend most of my time working on Mesh for 2142.[[newline]]

You can visit 2142 at: [http://maps.secondlife.com/secondlife/Westminster/128/128/10/ http://maps.secondlife.com/secondlife/Westminster/128/128/10/]

''or''

Join the 2142 group at: [http://www.2142sl.info/join http://www.2142sl.info/join]

''or''

See Urban Scene mesh items at: [https://marketplace.secondlife.com/stores/123798 https://marketplace.secondlife.com/stores/123798]

[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:LSL Mentors|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]
[[Category:Second Life Birthday Staff]]

File:Jamesbenedek.jpg

2013-01-08T23:14:08Z

James Benedek: uploaded a new version of "File:Jamesbenedek.jpg"

A pic of James Benedek I did in GIMP

File:Implying.png

2013-01-08T23:07:36Z

James Benedek: implying

implying

LlFixSL

2012-07-17T19:51:53Z

James Benedek: Created page with "{{KBwarning|This is ''not'' a real LSL function... but it should be.}} {{LSL_Function |func_id|func_sleep=0|func_energy=9001.0 |mode=request|func=llFixSl|sort=FixSl |func_desc=Wi…"

{{KBwarning|This is ''not'' a real LSL function... but it should be.}}
{{LSL_Function
|func_id|func_sleep=0|func_energy=9001.0
|mode=request|func=llFixSl|sort=FixSl
|func_desc=Will cause SL to work and hopefully not be buggy!
|p1_type=integer|p1_name=time_till_next_broken_server_update|p1_desc=Y U BREAK THINGS?!
|func_footnote=You will be happy when no bugs exist!
|return_text
|spec
|caveats=IF ONLY IT EXISTED
|examples=
<lsl>
default
{
state_entry()
{
llFixSL(integer time_till_next_broken_server_update);
integer time_till_next_update = time_till_next_update + 100;
llCelebrate(key user);
state they_fixed_sl_finally_omg;
}
}

state they_fixed_sl_finally_omg
{
state_entry()
{
llLoopSoundGridwide("Andrew W.K. - Party Hard",9001); //loop a sound on 9001 volume all over the grid
}
}

</lsl>
|notes=LOLWUT!}}

User:James Benedek

2009-07-06T21:17:04Z

James Benedek:

[[Image:jamesbenedek.jpg]]

----

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖Jira Second Life Bug Hunter. - {{Jira Reporter}}

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:LSL Mentors|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]
[[Category:Second Life Birthday Staff]]

A Basic LSL Tutorial

2009-07-06T21:06:28Z

James Benedek:

Basic Tutorial on LSL.
By [[James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

'''Errors and how to fix them?'''
---------------------------
If you get an error while scripting at any time, it will usually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a syntax error). Sometimes this may not be the case though.

'''Basic understanding of terms''':
-----------------------------
A function shown in red and does

A event is shown in light blue

A string is characters and should be in "", like "hello bill!".

A integer is a whole number like 1

A vector is numbers placed out like so <0,0,0>, it can represent
colour, position.

A float is a decimal number like 1.0, usually used in alpha and calculation.

A key is a random generated UUID on the linden labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

'''TASK 1''':
-------
Lets begin by doing a easy task first off, lets make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit in-between the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

'''TASK 2''':
-------
Lets just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when someone touches it
}
}
</lsl>

'''TASK 3''':
-------
Lets now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}
</lsl>

'''TASK 4''':
-------
Lets now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldn't be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}
</lsl>

'''TASK 5''':
-------
Now that you understand alpha we shall make our object disappear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}
</lsl>

'''Task 6''':
-------
Lets try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}
</lsl>

'''Task 7''':
-------
Now lets move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}
</lsl>

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}
</lsl>

'''Task 8''':
-------
Now lets try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will firstly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}
</lsl>

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggy in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}
</lsl>

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}
</lsl>

To learn more about llListen take a look at:

https://wiki.secondlife.com/wiki/llListen

'''TASK 9''':
-------
Now lets experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}
</lsl>

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

https://wiki.secondlife.com/wiki/llSetPos

'''TASK 10''':
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}
</lsl>

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

http://wiki.secondlife.com/wiki/LSL_Portal

http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage

http://rpgstats.com/wiki/index.php?title=Main_Page

---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

A Basic LSL Tutorial

2009-07-06T21:02:20Z

James Benedek:

Basic Tutorial on LSL.
By [[James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

'''Errors and how to fix them?'''
---------------------------
If you get an error while scripting at anytime, it will ususually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a synthax error). Sometimes this may not be the case though.

'''Basic understanding of terms''':
-----------------------------
A function shown in red and does

A event is shown in light blue

A string is charachters and should be in "", like "hello bill!".

A integer is a whole number like 1

A vector is numbers placed out like so <0,0,0>, it can represent
colour, position.

A float is a decimal number like 1.0, usually used in alpha and calculation.

A key is a random generated UUID on the linden labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

'''TASK 1''':
-------
Lets begin by doing a easy task first off, lets make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit inbetween the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

'''TASK 2''':
-------
Lets just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when someone touches it
}
}
</lsl>

'''TASK 3''':
-------
Lets now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}
</lsl>

'''TASK 4''':
-------
Lets now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldnt be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}
</lsl>

'''TASK 5''':
-------
Now that you understand alpha we shall make our object dissapear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}
</lsl>

'''Task 6''':
-------
Lets try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}
</lsl>

'''Task 7''':
-------
Now lets move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}
</lsl>

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}
</lsl>

'''Task 8''':
-------
Now lets try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will fistly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}
</lsl>

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggier in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}
</lsl>

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}
</lsl>

To learn more about llListen take a look at:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=llListen

'''TASK 9''':
-------
Now lets experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}
</lsl>

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSetPos

'''TASK 10''':
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}
</lsl>

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

[http://wiki.secondlife.com/wiki/LSL_Portal]

[http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage]

[http://rpgstats.com/wiki/index.php?title=Main_Page]

---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

A Basic LSL Tutorial

2009-07-06T20:55:58Z

James Benedek: Created page with 'Basic Tutorial on LSL. By James Benedek --------------------------------------------------------------------------------------------------- ----------------------------------...'

Basic Tutorial on LSL.
By [[James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

Errors and how to fix them?
---------------------------
If you get an error while scripting at anytime, it will ususually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a synthax error). Sometimes this may not be the case though.

Basic understanding of terms:
-----------------------------
A function shown in red and does

A event is shown in light blue

A string is charachters and should be in "", like "hello bill!".

A integer is a whole number like 1

A vector is numbers placed out like so <0,0,0>, it can represent
colour, position.

A float is a decimal number like 1.0, usually used in alpha and calculation.

A key is a random generated UUID on the linden labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

TASK 1:
-------
Lets begin by doing a easy task first off, lets make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit inbetween the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

TASK 2:
-------
Lets just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when somone touches it
}
}

TASK 3:
-------
Lets now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}

TASK 4:
-------
Lets now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldnt be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}

TASK 5:
-------
Now that you understand alpha we shall make our object dissapear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}

Task 6:
-------
Lets try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}

Task 7:
-------
Now lets move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}

Task 8:
-------
Now lets try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will fistly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggier in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}

To learn more about llListen take a look at:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=llListen

TASK 9:
-------
Now lets experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSetPos

TASK 10:
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

http://wiki.secondlife.com/wiki/LSL_Portal

http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage

http://rpgstats.com/wiki/index.php?title=Main_Page

---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

LSL Tutorial

2009-07-06T20:54:44Z

James Benedek: /* Beginner Tutorials */

{{LSL Header|ml=*}}

== Beginner Tutorials ==
'''[[Getting Ready to Learn LSL]]:''' Before learning LSL, it is helpful to learn the basics of Second Life. Here are some pointers to getting started.

'''[[Help:Getting started with LSL|Getting started with LSL]]:''' Tutorial for absolute beginners. Basic SL inventory and navigation required.

'''[[Hello Avatar]]:''' A place to try next after Getting Started in LSL.

'''[[Chatbot]]:''' A short tutorial list of concise LSL statements that make the default wood box translucent and bouncy and then kick and spin it along, also a script to run such commands for you.

'''[[DialogMenus|Building a dialog menu step by step]]:''' A tutorial for learners on implementing a simple, starter dialog menu system. Designed to illustrate the basic principles in layman's English.

'''[[Video Tutorial/Script editor featurettes]]:''' Features of the inworld Script editor. Look at [[LSL Alternate Editors]] for external 3rd party editors.

'''[[LSL 101: The Wikibook]]:''' A collaborative project to create a "complete", narrative, guide to LSL scripting, starting with no assumptions of previous programming experience. and going to ... who knows where?

'''[[A Basic LSL Tutorial]]:''' A tutorial for people who are new to LSL scripting, with basics tasks and LSL scripting terms explained in quick short answers for you.

== In-World Tutorials ==
'''[http://slurl.com/secondlife/Hyles/124/208/1002/?title=Linden%20Script%20Exhibition Free interactive in-world Linden Script Tutorial]:''' Bromley College has developed a free interactive scripting tutorial exhibition in-world.

You can also find the tutorial in-world by choosing '''Search > Classifieds''' and searching for the phrase '''linden script tutorial'''

'''[http://slurl.com/secondlife/Star%20Beach%20Island/150/212/22/?x=300&y=300&img=http%3A//cd.bromley.ac.uk/bteccourses/sl/images/shimmer_island.jpg&title=Learning%20in%20Virtual%20Reality&msg=Here%20at%20Shimmer%20island%2C%20I%20shall%20be%20exploring%20the%20potential%20of%20Second%20Life%20in%20support%20of%20my%20current%20trials%20with%20the%20Moodle%20vle%20for%20Virtual%20Learning.%20So%20please%20feel%20free%20to%20drop%20in%20for%20a%20chat%20with%20us%20to%20see%20how%20things%20are%20going.%20Regards%20Skipper%20Abel Bromley College in-world Virtual Learning trials]:''' Please feel free to come over and look around

'''[http://slurl.com/secondlife/Horsa/43/236/84 Many free scripting tutorials that are easy to read at our College of Scripting, Music and Science]:''' Come by to learn scripting and building.

'''[http://swiss-projects.ch/secondlife-tutorial Swiss Projects Tutorial, the Swiss Tutorial for Second Life®; interactive, inworld and in the Web, in German]:''' das schweizer Tutorial zu Second Life®; interaktiv, inworld und im Web, in deutscher Sprache. SLURL: '''[http://slurl.com/secondlife/swiss%20projects]'''

== External Tutorials ==
'''[http://www.ddj.com/dept/ai/197008520?pgno=1 Using LSL introductory tutorial]''' Dr. Dobb's tutorial

'''[http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial]:''' Video tutorial for building and scripting a clock.

'''[http://people.cc.ku.edu/~grobe/intro-to-LSL/ Using the Linden Script Language]:''' A very comprehensive tutorial on basic scripting from Kan-ed.

'''[http://johannahyacinth.blogspot.com/2006/12/scripting-basics-part-1.html Scripting Basics (Part 1)]:''' Scripting basics from Johanna Hyacinth. Also try [http://johannahyacinth.blogspot.com/2006/12/scripting-basics-part-2_18.html part2] and [http://johannahyacinth.blogspot.com/2006/11/lsl-magic-barrier.html part3].

'''[http://stonedchipmunkrocks.googlepages.com/peternelson%27sguidetolsl Peter Nelson's Guide to LSL]:''' A series of LSL tutorials from Peter Nelson. A work in progress.

'''[http://dev.aol.com/article/2007/04/second-life A New Hampshire Coder in Linden Lab's Court]:''' An article on dev.aol.com discussing software engineering strategies for LSL

'''[http://slifeguide.googlepages.com/scripting.html Scripting in Second Life]:''' by oceanspray

'''[http://wintermute.linguistics.ucla.edu/lsl/ Programming in Second Life]''' tutorial for teen grid and others

'''[http://www.wakatech.com/articles/lsl-scripting-basics/configuring-lsl-scripts-using-a-notecard/ Configuring LSL Scripts Using a Notecard]''' Tutorial on configuring with notecards.

'''[http://hobblescripts.com/index.php?option=com_content&view=article&id=2:lsl-scripting-tutorial&catid=5:tutorial&Itemid=3 An easy to follow tutorial for LSL]''' Guides you through creating your first fun script explaining the basic language features.

== Scripting Tools ==
These tools are designed to '''ease the process of scripting''', whether it's autogenerating scripts or helping you to edit them. Some of them were featured in [http://blog.secondlife.com/2008/07/19/get-started-scripting-with-autoscript-video-tip-of-the-week-42/ Torley's Autoscript post]:

<videoflash>xW619vHfYeg</videoflash>

* '''[http://www.3greeneggs.com/autoscript/ Autoscript]''' - Ann Enigma's versatile tool lets you make a script with a few clicks, then examine and edit it further. Easily add interactivity to your objects and get started scripting! Available in Français and Deutsch too.

* '''[http://web.mit.edu/~eric_r/Public/S4SL/ Scratch for Second Life]''' - Eric Rosenbaums’s exciting app (for Mac and Windows) in development which lets you arrange scripts visually as if they were Legos. I haven’t had a chance to even scratch (ha!) its surface yet, but watch Eric’s video to better understand:

* '''[http://particles-lsl-generator.bashora.com/ Particle script generator]''' - This formatted webpage may be easier to use than SL’s own script editor. Change your parameters and try it out inworld.

* '''[http://www.heatonresearch.com/examples/particle/particle.html Encog's Particle Machine]''' - "The particle machine allows you to specify particle effects and see them created in the Second Life world."

[[Category:Tutorials]]
[[Category:LSL Tutorials]]

Combat

2008-10-03T23:49:18Z

James Benedek: /* Rausch */

{{Help|Misc=*}}

Combat in Second Life is a very fun and active hobby. This article will try to teach you exactly how Second Life combat works.

== Introduction ==

Some areas of Second Life, like New Jessie, are designed for the sole purpose of inter-resident combat;
in other areas combat is part of a larger role-playing ambiance.
There are two basic types of combat system in second life:
the built-in Linden Lab Combat System, and a variety of
User-created combat systems.

==Linden Lab Combat System (LLCS)==

The Linden Lab Combat System is in effect in any parcel that the owner has
designated as "unsafe". When you are in one of these areas there will be a heart with a percentage next to it on your upper menu bar. When you see this meter, it means you can be killed in the area. When this percentage drops to zero, you are then 'dead', and you will teleported to your home location.

Please note that being killed is '''not''' a big deal. You have to teleport back into the combat simulation from your home location, if you want to return to the combat. You will not lose anything (money, attachments, inventory) if you happen to die in this manner.

In the LLCS, damage is dealt by collisions with scripted objects that have used
[[LlSetDamage]] to make themselves damaging; Residents also take damage when they
collide with any object, or with the ground (as in falling), at sufficiently high
speed.

Damage "heals" gradually over time.

So, where do you go when you're looking for a fight?

===New Jessie - an Open Combat Zone===

[http://slurl.com/secondlife/New%20Jessie/197/92/301 New Jessie SLURL]

New Jessie is an open combat sim which is unaffiliated with any military and where everyone is welcome. When you land here, you can set your home here so that during combat, you need not teleport back when you die. There is a healthy mix of close quarters combat in a small town there, as well as a pair of bunkers and a shorefront with barbed wire and tank spikes. On top of all of it, there is a hub featuring a weapons shop, many free weapons, and a combat museum detailing the history of early combat in Second Life.

===Rausch===

Some of the most popular public LLCS combat areas are Rausch, Blue Base, and Red Base. These three sims are free-for-all sandboxes. There is a "safe zone" in the Rausch sandbox where you can't be attacked. It is usually surrounded by big yellow markers, and people have a tendency to gather in this area. (Please note that the "bases" are not really "bases" for anyone. They are free-for-all maps.)

The difference between Rausch and New Jessie and other sims is that while New Jessie is governed in the name of fair combat, Rausch truly is a complete free for all.

The fastest way to find these regions is to type "combat" into the places search.

[http://slurl.com/secondlife/Combat%20(sandbox)%20Rausch/172/163/22 Rausch Safe Zone SLURL]

[[Image:CombatBases.jpg]]

There are also many other regions & groups specifically for fair combat / military roleplay, which are non profit and running the LLCS damage, these are:

[http://slurl.com/secondlife/Salamis/172/163/22 Merczateers HQ(Salamis) SLURL]

[http://slurl.com/secondlife/Titan/172/163/22 Ordo HQ(Titan) SLURL]

[http://slurl.com/secondlife/2142/172/163/22 2142 HQ(2142) SLURL]

[http://slurl.com/secondlife/Elshout/172/163/22 Alliance Navy HQ(Elshout) SLURL]

[http://slurl.com/secondlife/Ziost/172/163/22 39th HQ(Ziost) SLURL]

[http://slurl.com/secondlife/Vadoo%20Reef/172/163/22 Echelon Union HQ(Vadoo Reef) SLURL]

[http://slurl.com/secondlife/Cannes%20Villes/172/163/22 Imperium Battalion HQ(Cannes Villes) SLURL]

[http://slurl.com/secondlife/Pacific%20Breeze/172/163/22 Sparta HQ(Pacific Breeze) SLURL]

[http://slurl.com/secondlife/San%20Andreas/67/151/40 Rathium HQ(San Andreas) SLURL]

[http://slurl.com/secondlife/core/161/68/34 Core Combat Sand Box Safe Zone(Core) SLURL]

== User-Created Combat Systems (UCCS) ==

User-created combat systems do not use the built-in LLCS (and for this reason are sometimes called "safezone" combat systems), but instead use scripted objects both to track and to deal damage.

This type of combat system can be used in any area that allows scripts to run. Usually these systems require the player to wear a "tag" or a "HUD" in order to play. This monitors your health, and various other stats, varying among the combat systems.

These systems usually come with their own sets of rules that disallow the use of anything from advanced weapons to Bots to shields to instant-killers with the exception of basic weaponry and in some rare cases some small explosives. Sometimes the UCCS' rules include the neccessity of [[Roleplay]]ing, but some again are just straight forward killing. Some advanced UCCS keep stats of the players such as kill count, death count, level etc.

When the player dies, unlike the LLCS, they will not be teleported back home. They will typically either "respawn" after a few minutes or some advanced systems will spawn a "spawn ball" which the player sits on and they will be able to respawn at a random location in the combat area with full health.
The exact effects of "death" depend on the particular UCCS in use.

It is important to note that many UCCS frown upon Defenses (shield, auto orbit), Advanced "guns", Large Scale Explosives (+5 m), Automated Turrets, orbit, lag bombs. Most UCCS simulations also recommend using High quality basic weaponry that do not cause Lag within the SIM.

A Few Notable User Created Combat Systems are 'CCS' 'RCS 'DCS' 'TCS' 'Carnage Island Combat' 'XCS', 'Pure Combat', '[http://www.goodman-studios.biz/docs/battlezone-combat-system-2 BattleZone]', and '[http://www.goodman-studios.biz/docs/gorean-ladder-meter Gorean Ladder Meter]'.

Because user-created combat systems generally depend on cooperation between scripted damage-dealing objects and scripted damage-sensing objects owned and worn by the player being damaged, there is a great potential for 'cheating', by writing scripts that appear to be obeying the rules of the system, but that in fact make the player very hard to damage, very good at dealing damage, or both. While most users of these combat systems enjoy competing legitimately, there are always a few who try to cheat, and different combat communities and combat systems have taken various approaches to detecting, preventing, or discouraging the cheaters.

== Engagement ==

In Second Life you have a vast array of weapons, combat vehicles, and defense mechanisms at your disposal, for a vast and sometimes baffling array of different and often incompatible combat systems.

When buying combat devices, it's important to be sure that they are compatible with
the combat system(s) in use in the area(s) where you plan to engage!
That Gorean sword may prove entirely useless against the band of Samurai
that you were planning to fight...

=== Weaponry ===

There are hundreds of [[weapon]]s in Second Life to choose from, compatible with various different combat systems. These weapons may be classified into several categories:

*Basic Guns - Guns that fire basic physical bullets. These are stopped by most quality shield systems.
*Advanced "Guns" - Guns that fire tracking, non-physical bullets. These can't be stopped by all but the most advanced (and expensive) defense systems.
*Explosives and "Nukes" - Self explanatory. These range from basic explosives to nukes that can kill everyone within 96m of the detonation point.
*Advanced Weapons - The most effective and powerful weapons often combine a number of different effects with sophisticated, often HUD-based controls. There are several quality HUD-based combat systems available, as described below.
*Robots and Turrets - These can be remote controlled, or set to fire on certain targets automatically.
*Annoyance weapons - Stuff like caging guns, anything that flings people into the air, and in general things that annoy rather than, or as well as, dealing combat-system damage. Considered "noobish" and frowned upon by experienced combat people.

For more information, see [[Weapon]].

=== Combat Vehicles ===

Sadly, the use of combat vehicles has reduced in second life. While they are very fun to fly, most vehicles will be "disrupted" by shields in actual combat situations, causing them to fly away. The only way to avoid this is to use non-physical vehicles.

=== Defense ===

Defense plays an important part in combat life. An undefended avatar can be obliterated by modern weaponry, ruining the fun for many new combat players. There are several ways to defend yourself in Second Life.

*Shields
*Defense Bots
*Killing someone before they kill you

There are several different "brands" of shields to choose from, compatible with various different combat systems. Shields are a must, and they are well worth the cost. A good shield should physically push bullets away before they reach the actual shield. Even the best shield, however, is vulnerable to tracking bullets.

Defense bots are the most advanced way of keeping alive in Second Life combat. Defense bots position your physical avatar underground and/or out of the sim, where it is not possible for 98% of weapons to kill them, while allowing you to play "through" the bot. Just like in real life, weapons in SL advance in complexity every day. There are several weapons that can kill someone using the "off-sim" modes of these bots, and more appear all the time.

Most defense bots allow you to issue "Combat HUD-like" commands on people, enabling you to kill them and stay safely protected in your bot.

Note that many combat systems and combat areas, such as medieval or primitive role-play
areas, will probably disallow some or all of the "high-tech" defensive items, especially bots.

== Non-Lethal Warfare ==

There are some weapons that can be used to disrupt or annoy another player without actually killing them.

*Orbiting is the term used when one player causes another player to be flung up insanely high in the air.
*People use "traps" to render a physical avatar unable to move.
*"Lag-Bombs" are devices of various kinds that eat up Sim resources and cause lag, thus slowing down the target Resident's activities.

While this kind on non-lethal device can (sometimes) be appropriate to delay or detour a legitimate opponent in a combat game, they are also commonly used by [[griefer]]s against unwilling victims in both combat and non-combat areas. They therefore tend to have a poor reputation, and to be looked down upon in many combat communities.

In the area of defense against pushes and pulls, most combatants use a device known as a "non-phys". A non-phys makes your avatar non-physical, in other words immune to being pushed or pulled. Period. A non-phys is basically a prim that you sit on, usually it becomes invisible once you sit, and you steer it around just like you are moving normally. When using a non-phys, you can pass through objects and walls.

If a non-phys is not handy and you are in danger of being orbited, just create a prim box and sit on it. Sitting on the ground will do you no good at all.

== Advanced Weapons ==

The most powerful weapons in Second Life enable you to simply say (or click) a command, such as "kill joh", resulting in the nearest person (within 96m) with joh in their name being killed instantly - shields or no shields.
Because many of the currently popular weapons in this class use Heads-Up Displays ([[HUD]]s), they are sometimes referred to as "Combat HUDs".
They usually offer a substantial arsenal of attacks that you can deploy, other than the standard "kill person" command. These include orbiting, "burning" people, trapping, auto-killing, etc.

Some advanced weapons are designed primarily to deal damage and provide defense in a single combat system (either LLCS or a user-created system); others support two or more different combat systems in a single device.
Still others concentrate on the non-lethal actions and annoyances described above, and merge into the category of griefer and anti-griefer devices and away from legitimate combat.

Underground bots and phase devices (in a nutshell devices that make you undetectable to sensors) are the only protection against the most powerful weapon in this class.

[[Category:Tutorials|Combat]]

Combat

2008-09-16T21:26:37Z

James Benedek:

{{Help|Misc=*}}

Combat in Second Life is a very fun and active hobby. This article will try to teach you exactly how Second Life combat works.

== Introduction ==

Some areas of Second Life are designed for the sole purpose of inter-resident combat;
in other areas combat is part of a larger role-playing ambiance.
There are two basic types of combat system in second life:
the built-in Linden Lab Combat System, and a variety of
User-created combat systems.

===Linden Lab Combat System (LLCS)===

The Linden Lab Combat System is in effect in any parcel that the owner has
designated as "unsafe". When you are in one of these areas there will be a heart with a percentage next to it on your upper menu bar. When you see this meter, it means you can be killed in the area. When this percentage drops to zero, you are then 'dead', and you will teleported to your home location.

Please note that being killed is '''not''' a big deal. You have to teleport back into the combat simulation from your home location, if you want to return to the combat. You will not lose anything (money, attachments, inventory) if you happen to die in this manner.

In the LLCS, damage is dealt by collisions with scripted objects that have used
[[LlSetDamage]] to make themselves damaging; Residents also take damage when they
collide with any object, or with the ground (as in falling), at sufficiently high
speed.

Damage "heals" gradually over time.

Some of the most popular public LLCS combat areas are Rausch, Blue Base, and Red Base. These three sims are free-for-all sandboxes. There is a "safe zone" in the Rausch sandbox where you can't be attacked. It is usually surrounded by big yellow markers, and people have a tendency to gather in this area. (Please note that the "bases" are not really "bases" for anyone. They are free-for-all maps.)

The fastest way to find these regions is to type "combat" into the places search.

[http://slurl.com/secondlife/Combat%20(sandbox)%20Rausch/172/163/22 Rausch Safe Zone SLURL]

[[Image:CombatBases.jpg]]

There are also many other regions & groups specifically for fair combat / military roleplay, which are non profit and running the LLCS damage, these are:

[http://slurl.com/secondlife/New%20Jessie/197/92/301 New Jessie SLURL]

[http://slurl.com/secondlife/Salamis/172/163/22 Merczateers HQ(Salamis) SLURL]

[http://slurl.com/secondlife/Titan/172/163/22 Ordo HQ(Titan) SLURL]

[http://slurl.com/secondlife/2142/172/163/22 2142 HQ(2142) SLURL]

[http://slurl.com/secondlife/Elshout/172/163/22 Alliance Navy HQ(Elshout) SLURL]

[http://slurl.com/secondlife/Ziost/172/163/22 39th HQ(Ziost) SLURL]

[http://slurl.com/secondlife/Vadoo%20Reef/172/163/22 Echelon Union HQ(Vadoo Reef) SLURL]

[http://slurl.com/secondlife/Cannes%20Villes/172/163/22 Imperium Battalion HQ(Cannes Villes) SLURL]

[http://slurl.com/secondlife/Pacific%20Breeze/172/163/22 Sparta HQ(Pacific Breeze) SLURL]

=== User-Created Combat Systems (UCCS) ===

User-created combat systems do not use the built-in LLCS (and for this reason are sometimes called "safezone" combat systems), but instead use scripted objects both to track and to deal damage.

This type of combat system can be used in any area that allows scripts to run. Usually these systems require the player to wear a "tag" or a "HUD" in order to play. This monitors your health, and various other stats, varying among the combat systems.

These systems usually come with their own sets of rules that disallow the use of anything from advanced weapons to Bots to shields to instant-killers with the exception of basic weaponry and in some rare cases some small explosives. Sometimes the UCCS' rules include the neccessity of [[Roleplay]]ing, but some again are just straight forward killing. Some advanced UCCS keep stats of the players such as kill count, death count, level etc.

When the player dies, unlike the LLCS, they will not be teleported back home. They will typically either "respawn" after a few minutes or some advanced systems will spawn a "spawn ball" which the player sits on and they will be able to respawn at a random location in the combat area with full health.
The exact effects of "death" depend on the particular UCCS in use.

It is important to note that many UCCS frown upon Defenses (shield, auto orbit), Advanced "guns", Large Scale Explosives (+5 m), Automated Turrets, orbit, lag bombs. Most UCCS simulations also recommend using High quality basic weaponry that do not cause Lag within the SIM.

A Few Notable User Created Combat Systems are 'CCS' 'RCS 'DCS' 'TCS' 'Carnage Island Combat' 'XCS', 'Pure Combat', '[http://www.goodman-studios.biz/docs/battlezone-combat-system-2 BattleZone]', and '[http://www.goodman-studios.biz/docs/gorean-ladder-meter Gorean Ladder Meter]'.

Because user-created combat systems generally depend on cooperation between scripted damage-dealing objects and scripted damage-sensing objects owned and worn by the player being damaged, there is a great potential for 'cheating', by writing scripts that appear to be obeying the rules of the system, but that in fact make the player very hard to damage, very good at dealing damage, or both. While most users of these combat systems enjoy competing legitimately, there are always a few who try to cheat, and different combat communities and combat systems have taken various approaches to detecting, preventing, or discouraging the cheaters.

== Engagement ==

In Second Life you have a vast array of weapons, combat vehicles, and defense mechanisms at your disposal, for a vast and sometimes baffling array of different and often incompatible combat systems.

When buying combat devices, it's important to be sure that they are compatible with
the combat system(s) in use in the area(s) where you plan to engage!
That Gorean sword may prove entirely useless against the band of Samurai
that you were planning to fight...

=== Weaponry ===

There are hundreds of [[weapon]]s in Second Life to choose from, compatible with various different combat systems. These weapons may be classified into several categories:

*Basic Guns - Guns that fire basic physical bullets. These are stopped by most quality shield systems.
*Advanced "Guns" - Guns that fire tracking, non-physical bullets. These can't be stopped by all but the most advanced (and expensive) defense systems.
*Explosives and "Nukes" - Self explanatory. These range from basic explosives to nukes that can kill everyone within 96m of the detonation point.
*Advanced Weapons - The most effective and powerful weapons often combine a number of different effects with sophisticated, often HUD-based controls. There are several quality HUD-based combat systems available, as described below.
*Robots and Turrets - These can be remote controlled, or set to fire on certain targets automatically.
*Annoyance weapons - Stuff like caging guns, anything that flings people into the air, and in general things that annoy rather than, or as well as, dealing combat-system damage. Considered "noobish" and frowned upon by experienced combat people.

For more information, see [[Weapon]].

=== Combat Vehicles ===

Sadly, the use of combat vehicles has reduced in second life. While they are very fun to fly, most vehicles will be "disrupted" by shields in actual combat situations, causing them to fly away. The only way to avoid this is to use non-physical vehicles.

=== Defense ===

Defense plays an important part in combat life. An undefended avatar can be obliterated by modern weaponry, ruining the fun for many new combat players. There are several ways to defend yourself in Second Life.

*Shields
*Defense Bots
*Killing someone before they kill you

There are several different "brands" of shields to choose from, compatible with various different combat systems. Shields are a must, and they are well worth the cost. A good shield should physically push bullets away before they reach the actual shield. Even the best shield, however, is vulnerable to tracking bullets.

Defense bots are the most advanced way of keeping alive in Second Life combat. Defense bots position your physical avatar underground and/or out of the sim, where it is not possible for 98% of weapons to kill them, while allowing you to play "through" the bot. Just like in real life, weapons in SL advance in complexity every day. There are several weapons that can kill someone using the "off-sim" modes of these bots, and more appear all the time.

Most defense bots allow you to issue "Combat HUD-like" commands on people, enabling you to kill them and stay safely protected in your bot.

Note that many combat systems and combat areas, such as medieval or primitive role-play
areas, will probably disallow some or all of the "high-tech" defensive items, especially bots.

== Non-Lethal Warfare ==

There are some weapons that can be used to disrupt or annoy another player without actually killing them.

*Orbiting is the term used when one player causes another player to be flung up insanely high in the air.
*People use "traps" to render a physical avatar unable to move.
*"Lag-Bombs" are devices of various kinds that eat up Sim resources and cause lag, thus slowing down the target Resident's activities.

While this kind on non-lethal device can (sometimes) be appropriate to delay or detour a legitimate opponent in a combat game, they are also commonly used by [[griefer]]s against unwilling victims in both combat and non-combat areas. They therefore tend to have a poor reputation, and to be looked down upon in many combat communities.

In the area of defense against pushes and pulls, most combatants use a device known as a "non-phys". A non-phys makes your avatar non-physical, in other words immune to being pushed or pulled. Period. A non-phys is basically a prim that you sit on, usually it becomes invisible once you sit, and you steer it around just like you are moving normally. When using a non-phys, you can pass through objects and walls.

If a non-phys is not handy and you are in danger of being orbited, just create a prim box and sit on it. Sitting on the ground will do you no good at all.

== Advanced Weapons ==

The most powerful weapons in Second Life enable you to simply say (or click) a command, such as "kill joh", resulting in the nearest person (within 96m) with joh in their name being killed instantly - shields or no shields.
Because many of the currently popular weapons in this class use Heads-Up Displays ([[HUD]]s), they are sometimes referred to as "Combat HUDs".
They usually offer a substantial arsenal of attacks that you can deploy, other than the standard "kill person" command. These include orbiting, "burning" people, trapping, auto-killing, etc.

Some advanced weapons are designed primarily to deal damage and provide defense in a single combat system (either LLCS or a user-created system); others support two or more different combat systems in a single device.
Still others concentrate on the non-lethal actions and annoyances described above, and merge into the category of griefer and anti-griefer devices and away from legitimate combat.

Underground bots and phase devices (in a nutshell devices that make you undetectable to sensors) are the only protection against the most powerful weapon in this class.

[[Category:Tutorials|Combat]]

Open Grid Public Beta/Map Locations

2008-08-02T12:14:18Z

James Benedek:

OpenSim regions cannot be placed directly adjacent to existing regions on aditi or vaak.

:[[User:Zha_Ewry|Zha Ewry]]: "Setup as a very basic stand alone opensim. set the default location and the location of your region to be the same value, and run only one region on the server. (ie. in OpenSim.ini, make sure you set default_loc_x and default_loc_y, and make them match the ones in the default.xml in the Regions subdirectory of you r bin directory in your install. Make sure your X and Ys are multiples of 256."

Non-Linden Lab OpenSims should use default_loc_x and default_loc_y values greater than 4096.

Claim Map Locations Below

==[[User:Whump_Linden | Whump Linden ]]==

* 2048/2048
* 2304/2560

==[[User:Dahlia_Trimble | Dahlia Trimble ]]==

* 4096/4096

==[[User:Christophe003_Carter | Christophe003 Carter ]]==

* 4608/4608

==[[User:BlueWall Slade | Bluewall Slade]]==
*6400/6400

==[[User:Winne Woodget | Winne Woodget]]==

* 6912/6912

==[[User:Matias Carter | Matias Carter]]==

* 7168/7168

==[[User:Xugu Madison | Xugu Madison]]==

* 8192/8192

==[[User:Eddy Stryker | Eddy Stryker]]==

* 5888/5888

==[[User:Latif Khalifa | Latif Khalifa]]==

* 6144/6144

==[[User:Tracy Welles | Tracy Welles ]]==

* 4352/4352

==[[User:Bluecat Jun | Bluecat Jun ]]==

* 7424/7424

==[[User:Julie Wasserstrom | Julie Wasserstrom ]]==

* 5888/5888

==[[User:Chris Samtanko | Chris Samtanko ]]==

*4864/4864

==[http://mrtopf.de/blog Tao Takashi ]==

*6656/6656

==[[User:Jim Kupferberg | Jim Kupferberg ]]==

*6667/6667

==[[User:Emma Nowhere | Emma Nowhere ]]==

*5120/5120

==[[User:Gomez Bracken | Gomez Bracken ]]==

*8448/8448

==[[User:Ciemaar Flintoff | Ciemaar Flintoff ]]==

*6656/7680

==[[User:Media Hax | Media Hax ]]==

*5632/5632
==[[User:Twa Hinkle | Twa Hinkle ]]==

*7680/7680

==[[User:Vicero Lambert | Vicero Lambert ]]==

*5130/5130

==[[User:Whichway Janus | Whichway Janus ]]==

*6969/6969

==[[User:Stamo Stuer | Stamo Stuer ]]==

*5376/5376

==[[User:Patnad Babii | Patnad Babii ]]==

*10000/10000

==[[User:Torrid Luna | Torrid Luna ]]==

*6144/6144

==[http://blog.simgis.com Darb Dabney ]==

* 4608/4352

==[[User:Morph Wollongong | Morph Wollongong ]]==

* 6789/6789

==[[User:Estate Shepherd | Estate Shepherd ]]==

* 8704/8704

==[[User:Zerodog Witte | Zerodog Witte ]]==

* 8448/8448

==[[User:Lil Linden | Lil Linden]]==

* 2806/2806

==[[User:EriX Oh | EriX Oh]]==

* 4100/4100

==[[User:James Benedek | James Benedek]]==

* 7936/7936

[[Category:Open_Grid_Public_Beta]]

Open Grid Public Beta/Map Locations

2008-08-02T12:13:39Z

James Benedek:

LlPushObject

2008-07-12T20:03:41Z

James Benedek:

{{LSL_Function
|func_id=165|func_sleep=0.0|func_energy=10.0
|func=llPushObject
|p1_type=key|p1_name=target|p1_desc=Avatar or object [[UUID]] in the sim
|p2_type=vector|p2_name=impulse
|p3_type=vector|p3_name=ang_impulse|p3_desc=angular impulse
|p4_type=integer|p4_name=local|p4_desc=boolean, if {{LSL Const|TRUE|integer|1}} uses the [[Viewer coordinate frames#Local|local]] axis of '''target''', if {{LSL Const|FALSE|integer|0}} uses the [[Viewer coordinate frames#Region|region]] axis.
|func_footnote
|func_desc=Applies '''impulse''' and '''ang_impulse''' to object '''id'''
|return_text
|spec
|caveats=*Only works on land where Push is not restricted or where the script is owned by the land owner.
**If the land is owned by a group, the scripted object must be deeded to the same group.
*The effectiveness of Push is modulated by the amount of [[ScriptEnergy|script energy]] available.
**There is a [[LlPushObject/Havok4Implementation|simplified code snippet]] describing how Push is implemented in the Havok4 project and reveals some of the details of how the energy budget affects the final Push magnitude.
|constants
|examples=
<lsl>// Pushes the collided object or avatar.
default
{
collision_start(integer num_detected)
{
llPushObject(llDetectedKey(0),<0,0,100>, <0,0,100>, TRUE);
}
}</lsl>
|helpers
|also_functions
|also_events
|also_tests
|also_articles
|notes
|permission
|negative_index
|cat1=Physics
|cat2
|cat3
|cat4
}}

LlPreloadSound

2008-07-12T19:55:16Z

James Benedek:

{{LSL_Function/inventory|sound|uuid=true|type=sound}}
{{LSL_Function
|func_id=93|func_sleep=1.0|func_energy=10.0
|func=llPreloadSound
|p1_type=string|p1_name=sound
|func_footnote
|func_desc=Preloads '''sound''' on viewers within range
|return_text
|spec
|caveats
|constants
|examples=<lsl>default //Will preload when rezzed, then play when 'touched'.
{
on_rez(integer start_param)
{
llSetText("Preloading....",<1,0,0>,1);
llPreloadSound("SOUND UUID HERE");
llSetText("Touch To Play",<1,1,1>,1);
}
touch_start(integer num_detected)
{
llPlaySound("SOUND UUID HERE",1);
}
}</lsl>
|helpers
|also_functions
|also_events
|also_tests
|also_articles
|notes
|sort=PreloadSound
|cat1=Sound
|cat2
|cat3
|cat4
}}

Land collision

2008-07-12T19:46:57Z

James Benedek:

{{LSL_Event
|event_id=9
|event_delay
|event=land_collision
|p1_type=vector
|p1_name=pos
|p1_desc=position of collision with the ground
|event_desc=Triggered when task is colliding with land
|constants
|spec
|caveats
|examples=<lsl>//Will die on collision with land.
default
{
land_collision(vector pos)
{
llDie();
}
}</lsl>
|helpers
|also_header=*{{LSLGC|Collision|Collision events & functions}}
|also_events
|also_functions={{LSL DefineRow||[[llGround]]|Gets the ground height}}
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Collision
|cat2=Ground
|cat3
|cat4
|cat5
|cat6
}}

User:James Benedek

2008-07-12T19:32:30Z

James Benedek:

[[Image:jamesbenedek.jpg]]

----

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖Jira Second Life Bug Hunter. - {{Jira Reporter}}

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:LSL Mentors|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]
[[Category:Second Life Birthday Staff]]

SL5B

2008-06-04T12:44:40Z

James Benedek: /* Staff List / Event Contacts */

{{TOCnestright}}

[[Image:SL5B-little-wiki.jpg|SL5B Logo]]
== General Information ==
'''Welcome to the official central resource for information related to Second Life's 5th Birthday! The event is being coordinated by the SL5B Committee, which is made up of Resident Volunteers and Lindens.'''

This year's birthday celebration is a 2-week event. The first week, June 23 to June 29, will be kicked off by speeches from Philip Linden and M Linden. Themes for that week will feature exhibits from cultures past and present, arts, fashion, machinima, and music. For these exhibits, we’ve extended the deadline [http://creator.zoho.com/showForm.do?formLinkId=27&link=true&sharedBy=dustylinden (cultures apply here, business link below)] to Thursday, June 5 at 6pm PDT.

The second week, from June 30 to July 7, will feature exhibits from business, education, health care and nonprofits. We’ll close with a ceremony including a special guest speaker with a very important announcement. The deadline for the business, education, health care and nonprofit exhibits [http://creator.zoho.com/showForm.do?formLinkId=5&link=true&sharedBy=dustylinden&privatelink=1xQS80Cgrqs5bJwWzDYrMXhwPpWQEUf3g69QfzTwNSmvE0T8UauNh73aT4G6F2rbUwGDXB1z3vS884RbJpK98C1jVHBBHyZqOg26 (businesses apply here, cultures link above)] is Tuesday, June 10 6pm PDT.

New information will be added here as we are able to make it available, to keep our fellow residents of Second Life informed on the progress of our 5th Birthday Event.

== Important Dates ==
* (To be updated)
* Second Life's 5th Birthday Event begins Jun 23, 2008 9:00 am (Monday) to Jul 7, 2008 11:59 pm (Monday)
* '''Notice:''' all times are in US Pacific time

== Signup Form for Exhibitors ==
* [http://creator.zoho.com/showForm.do?formLinkId=27&link=true&sharedBy=dustylinden Cultures apply here, business link below]
* [http://creator.zoho.com/showForm.do?formLinkId=5&link=true&sharedBy=dustylinden&privatelink=1xQS80Cgrqs5bJwWzDYrMXhwPpWQEUf3g69QfzTwNSmvE0T8UauNh73aT4G6F2rbUwGDXB1z3vS884RbJpK98C1jVHBBHyZqOg26 Businesses apply here, cultures link above]

== Guidelines/Policies for SL5B ==
* [http://blog.secondlife.com/2008/06/03/sl5b-birthday-expanded-and-new-submission-deadlines/ Additional Guidelines]
* (draft version) [http://forums.slopenid.net/topic/sl5b-draft-policy?replies=3 Draft Policies for SL5B]

== Staff List / Event Contacts ==
* (To be updated)
* Linden Event Liason: Dusty Linden
* Main Organiser: [[User:Trinity Coulter|Trinity Coulter]] (previously [[User:SignpostMarv Martin|SignpostMarv Martin]])
* Main Organiser: [[User:DawnRyder Wycliffe|DawnRyder Wycliffe]]
* Musical Performances: [[User:Chel Norfolk|Chel Norfolk]], [[User:CarrieAnn Nurmi|CarrieAnn Nurmi]], [[User:Daisy Beauchamp|Daisy Beauchamp]], [[User:Kelley Shortbread|Kelley Shortbread]], Live Music - [[User:Moaria Faddoul|Moaria Faddoul]]
* LSL Infrastructure: [[User:Will Webb|Will Webb]], [[User:James Benedek|James Bendedek]]
* Building Coordinator: [[User:Evie Fairchild|Evie Fairchild]], [[User:SamBivalent Spork|SamBivalent Spork]]
* Layout and Exhibits: [[User:Pyrii Akula|Pyrii Akula]], [[User:Evie Fairchild|Evie Fairchild]], [[User:Phaylen Fairchild|Phaylen Fairchild]]
* Art Exhibits: [[User:Shoshana Epsilon|Shoshana Epsilon]], [[User:Stephen Venkman|Stephen Venkman]], [[User:CodeBastard Redgrave|CodeBastard Redgrave]]
*Sim Coordinator: [[User:Meghan Dench|Meghan Dench]], [[User:Shoshana Epsilon|Shoshana Epsilon]]
* Terraform Artist: [[User:Poid Mahovlich|Poid Mahovlich]], [[User:Persis Trilling|Persis Trilling]], [[User:Dizzy Banjo|Dizzy Banjo]], [[User:Jurin Juran|Jurin Juran]]
* Architect: [[User:Scope Cleaver|Scope Cleaver]], [[User:Prad Prathivi|Prad Prathivi]], [[User:James Benedek|James Bendedek]]
* Chief Baker: [[User:YadNi Monde|YadNi Monde]]
* Linguists: [[User:Sandor Balczo|Sandor Balczo (Italian)]]

== Calendar of Events ==
* (Information being developed)
* Opening Event/Keynote
* Music/Parties
* Live Performances
* Second Life Cultural Events
* Industry Roundtables, Tours, Talks
* Closing Presentations

== Feedback Survey ==
* (To be added)

== Supplemental Information ==
* See [[http://forum.slbirthday.info/ for more information]].

== Office Hours ==
The following heads are currently running office hours:

{{:SL5B/Office Hours}}

[[Category:SL5B]]

User:Meghan Dench

2008-04-14T16:03:41Z

James Benedek:

[[Image:Meg00001.jpg]]
{{visl
|Greeters=
|Mentors=*
|Helpers=
|Instructors=
|Scribe=
|Linguist=
|Buddy=
|}}
{{Jira Reporter}}
[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]

<b>I am:</b>
* Second Life Mentor
* Second Life Mentor Coach
* Second Life Orientation Coach
* Second Life Bug Hunter
* Lovely : )

== My Second Life Orientation Sessions Schedule ==

'''These sessions are held for Second Life Apprentice Mentors to attend, and this is a mandatory session in order for the Apprentice to be moved over to the main Second Life Mentors Group, All scheduled sessions can be found [https://wiki.secondlife.com/wiki/Classes_Offered_By_Mentors/ here]'''

Here are my scheduled sessions:

*
*

== MY QUOTES: ==

[16:43] EnusBot2 LLQABot: Dench i Love You M.E.G.S.
_________________________________________________________________

[18:03] Elisheba Rossini: bleeding monkey.... go to sleep
[18:03] Meghan Dench: LOL
_________________________________________________________________

[22:45] Enus Linden: megs, sorry you slept [22:45] Enus Linden: i know you hate4 sleep [22:45] Enus Linden: is such a shame...
_________________________________________________________________

[3:51] Meghan Dench: I
[3:51] Meghan Dench: <3
[3:51] Meghan Dench: U
[3:51] Meghan Dench: .
[3:51] James Benedek: you are less than 3 of me?
[3:51] Meghan Dench: ?
[3:51] Meghan Dench: LOL
[3:51] James Benedek: lmao
[3:51] James Benedek: :P
[3:52] Meghan Dench: Cute : P
[3:52] James Benedek: only a nerd would say that XD
[3:52] Meghan Dench: haha
[3:52] James Benedek: hahah
[3:52] Meghan Dench: Not a nerd
[3:52] Meghan Dench: LOL
[3:52] James Benedek: if im not a nerd what am i ? :P
[3:52] Meghan Dench: Cute : P
[3:53] James Benedek: aww
[3:53] Meghan Dench: hehe

User:James Benedek

2008-04-14T15:56:53Z

James Benedek:

[[Image:jamesbenedek.jpg]]

----

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖Jira Second Life Bug Hunter. - {{Jira Reporter}}

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

[[Category:English speaking Volunteers|{{PAGENAME}}]]
[[Category:SL Mentor Coach|{{PAGENAME}}]]
[[Category:Bug Triage|{{PAGENAME}}]]

User:James Benedek

2008-04-14T15:34:31Z

James Benedek: /* Projects */

[[Image:jamesbenedek.jpg]]

----

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖SL Bug Hunter.

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

User:James Benedek

2008-04-14T15:31:52Z

James Benedek:

[[Image:jamesbenedek.jpg]]

----

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖SL Bug Hunter.

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''The Gravity Room''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513121

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

User:James Benedek

2008-04-14T15:30:35Z

James Benedek: /* About */

[[Image:jamesbenedek.jpg]]

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

----

==About==

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

[[Image:James benedek profile.jpeg|thumb|512px|James Benedek's Profile Pic]]

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖SL Bug Hunter.

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''The Gravity Room''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513121

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

File:James benedek profile.jpeg

2008-04-14T15:28:49Z

James Benedek: the profile pic of James Benedek from http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6

the profile pic of James Benedek from http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6

User:James Benedek

2008-04-14T15:23:46Z

James Benedek:

[[Image:jamesbenedek.jpg]]

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page* - http://jamesbenedek.googlepages.com]

✖Building Guide & Tips

✖Scripting Guide & Tips

✖General Help and FAQ

✖AND MUCH MUCH....MORE!

----

==About==
[[Image:1.jpeg|thumb|512px|James Benedek's Profile Pic]]

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

==Info==
✖Joined SL on 10/19/2006

✖Builder.

✖Scripter.

✖Texturer.

✖Founder of [[2142]].

✖SL Mentor

✖SL Mentor Buddy

✖SL Mentor Coach

✖SL Bug Hunter.

✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''The Gravity Room''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513121

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

User:James Benedek

2008-04-14T15:18:41Z

James Benedek: New page: Image:jamesbenedek.jpg [http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page*] ✖Building Guide & Tips ✖Scripting Guide & Tips ✖General Help and FAQ...

[[Image:jamesbenedek.jpg]]

[http://jamesbenedek.googlepages.com *Click Here to go to James Benedek's Help Page*]
✖Building Guide & Tips
✖Scripting Guide & Tips
✖General Help and FAQ
✖AND MUCH MUCH....MORE!

----

==About==
[[Image:1.jpeg|thumb|512px|James Benedek's Profile Pic]]

James Benedek is known for his helpful and nice attitude, extensive commitment to helping Linden Labs and others via : mentoring, welcoming and teaching new residents, updating and reproducing listed bugs on the Jira (http://jira.secondlife.com).

==Info==
✖Joined SL on 10/19/2006
✖Builder.
✖Scripter.
✖Texturer.
✖Founder of [[2142]].
✖SL Mentor
✖SL Mentor Buddy
✖SL Mentor Coach
✖SL Bug Hunter.
✖Havok 4 beta grid tester

Second Life profile - [http://world.secondlife.com/resident/d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6 James Benedek]

==Projects==
✖'''[[Mentor Messenger HUD]]''' - A HUD that lets the Second Life Mentors be informed where help in Second Life is Needed this is only available to official Second Life Mentors and is currently in - Beta 0.3.

✖'''[[Real Combat System]]''' - '''FREE''' at (http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=537334) to support his feature to make damage land more real (http://jira.secondlife.com/browse/VWR-3884) its abilties include(spawns, HUD blood effects when hit, oxygen meter in water, swimming ability in water, damagable and fixable vehicles, death and kills counter, anti-AV flight).

✖'''The Gravity Room''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513121

✖'''Free Lag Meter''' - http://www.slexchange.com/modules.php?name=Marketplace&file=item&ItemID=513181

✖'''Red Cross Island'''

File:Jamesbenedek.jpg

2008-04-14T15:07:39Z

James Benedek: A pic of James Benedek I did in GIMP

A pic of James Benedek I did in GIMP