Second Life Wiki - User contributions [en]

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-12T18:36:22Z

OddesE Oh:

Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apart from the problem that PERMISSION_DEBIT is currently limitless, meaning a vendor processing L$ 10 payments needs permission to llGiveMoney(to_some_avatar, unlimited_amount), there is also conceptually a big difference between REFUNDING money or GIVING money. I don't think a function llRefundMoney is needed, but it would be very good if the difference could be expressed in permissions. You could consider changing the color of the dialog box for request DEBIT permission from blue to red (after all, it's abuse sensitive.. blue can be a bit misleading). You could then have a yellow box for request REFUND permission. You would then restrict llGiveMoney, when called under REFUND permission, to
a) Only be called from within a money event context
b) Limit the amount given to the amount received in the money event.

Furthermore I suggest you add a 'budget' parameter to DEBIT permission, so any scripts that need to give money at will to operate can be restricted in their money-giving abilities.

For an illustration of the problems we currently have with DEBIT_PERMISSION, here are possible fraud scenarios:

Disguised-request-debit fraud

* Create an object for which it makes sense that it needs DEBIT permission, a slots machine, sploderball or vendor machine will do
* Create an algorithm to steal as much money as possible and let it run periodically

Users will give the DEBIT permission because it is expected that the object will ask for it. We need to have a budget parameter here so the dialog can say: .. wants to: Take a maximum of L$ 25 from you. Is this ok?

Request-debit-on-payment fraud

* Create a nice looking object that says: "Freebie: L$ 0"
* Do not set it 'For Sale', but instead llSetPayPrice(0, [DEFAULT,HIDDEN,HIDDEN,HIDDEN]);
* Create a money event and llSetPayText("Buy");
* Inside the money event, do a llRequestPermissions(id, [PERMISSION_DEBIT]);

The user will see:

* An object marked "Freebie: L$ 0"
* Upon rightclick, a pie menu item marked "Buy"
* Upon selection of the menu item, a dialog that says "Pay L$ to object "Freebie" owned by OddesE Oh?" with button "L$ 0"
* Upon payment, another dialog that says "Object "Freebie" owned by OddesE Oh wants to: Take L$ from you. Is this ok?" with buttons "Yes" and "No".

How many users do you trust with your money and this series of events?

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-12T18:34:10Z

OddesE Oh:

Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apart from the problem that PERMISSION_DEBIT is currently limitless, meaning a vendor processing L$ 10 payments needs permission to llGiveMoney(to_some_avatar, unlimited_amount), there is also conceptually a big difference between REFUNDING money or GIVING money. I don't think a function llRefundMoney is needed, but it would be very good if the difference could be expressed in permissions. You could consider changing the color of the dialog box for request DEBIT permission from blue to red (after all, it's abuse sensitive.. blue can be a bit misleading). You could then have a yellow box for request REFUND permission. You would then restrict llGiveMoney, when called under REFUND permission, to
a) Only be called from within a money event context
b) Limit the amount given to the amount received in the money event.

Furthermore I suggest you add a 'budget' parameter to DEBIT permission, so any scripts that need to give money at will to operate can be restricted in their money-giving abilities.

For an illustration of the problems we currently have with DEBIT_PERMISSION, here are possible fraud scenarios:

Disguised-request-debit

* Create an object for which it makes sense that it needs DEBIT permission, a slots machine, sploderball or vendor machine will do
* Create an algorithm to steal as much money as possible and let it run periodically

Users will give the DEBIT permission because it is expected that the object will ask for it. We need to have a budget parameter here so the dialog can say: .. wants to: Take a maximum of L$ 25 from you. Is this ok?

Request-debit-on-payment fraud

* Create a nice looking object that says: "Freebie: L$ 0"
* Do not set it 'For Sale', but instead llSetPayPrice(0, [DEFAULT,HIDDEN,HIDDEN,HIDDEN]);
* Create a money event and llSetPayText("Buy");
* Inside the money event, do a llRequestPermissions(id, [PERMISSION_DEBIT]);

The user will see:

* An object marked "Freebie: L$ 0"
* Upon rightclick, a pie menu item marked "Buy"
* Upon selection of the menu item, a dialog that says "Pay L$ to object "Freebie" owned by OddesE Oh?" with button "L$ 0"
* Upon payment, another dialog that says "Object "Freebie" owned by OddesE Oh wants to: Take L$ from you. Is this ok?" with buttons "Yes" and "No".

How many users do you trust with your money and this series of events?

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-12T18:32:17Z

OddesE Oh:

Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apart from the problem that PERMISSION_DEBIT is currently limitless, meaning a vendor processing L$ 10 payments needs permission to llGiveMoney(to_some_avatar, unlimited_amount), there is also conceptually a big difference between REFUNDING money or GIVING money. I don't think a function llRefundMoney is needed, but it would be very good if the difference could be expressed in permissions. You could consider changing the color of the dialog box for request DEBIT permission from blue to red (after all, it's abuse sensitive.. blue can be a bit misleading). You could then have a yellow box for request REFUND permission. You would then restrict llGiveMoney, when called under REFUND permission, to
a) Only be called from within a money event context
b) Limit the amount given to the amount received in the money event.

Furthermore I suggest you add a 'budget' parameter to DEBIT permission, so any scripts that need to give money at will to operate can be restricted in their money-giving abilities.

For an illustration of the problems we currently have with DEBIT_PERMISSION, here are possible fraud scenarios:

Disguised-request-debit

* Create an object for which it makes sense that it needs DEBIT permission, a slots machine, sploderball or vendor machine will do
* Create an algorithm to steal as much money as possible and let it run periodically

Users will give the DEBIT permission because it is expected that the object will ask for it. We need to have a budget parameter here so the dialog can say: .. wants to: Take a maximum of L$ 25 from you. Is this ok?

Request-debit-on-payment fraud

* Create a nice looking object that says: "Freebie: L$ 0"
* Do not set it 'For Sale', but instead llSetPayPrice(0, [DEFAULT,HIDDEN,HIDDEN,HIDDEN]);
* Create a money event and llSetPayText("Buy");
* Inside the money event, do a llRequestPermissions(id, [PERMISSION_DEBIT]);

The user will see:

An object marked "Freebie: L$ 0"
Upon rightclick, a pie menu item marked "Buy"
Upon selection of the menu item, a dialog that says "Pay L$ to object "Freebie" owned by OddesE Oh?" with button "L$ 0"
Upon payment, another dialog that says "Object "Freebie" owned by OddesE Oh wants to: Take L$ from you. Is this ok?" with buttons "Yes" and "No".

How many users do you trust with your money and this series of events?

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-12T18:03:37Z

OddesE Oh:

Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apart from the problem that PERMISSION_DEBIT is currently limitless, meaning a vendor processing L$ 10 payments needs permission to llGiveMoney(to_some_avatar, unlimited_amount), there is also conceptually a big difference between REFUNDING money or GIVING money. I don't think a function llRefundMoney is needed, but it would be very good if the difference could be expressed in permissions. You could consider changing the color of the dialog box for request DEBIT permission from blue to red (after all, it's abuse sensitive.. blue can be a bit misleading). You could then have a yellow box for request REFUND permission. You would then restrict llGiveMoney, when called under REFUND permission, to
a) Only be called from within a money event context
b) Limit the amount given to the amount received in the money event.

Furthermore I suggest you add a 'budget' parameter to DEBIT permission, so any scripts that need to give money at will to operate can be restricted in their money-giving abilities.

For an illustration of the problems we currently have with DEBIT_PERMISSION, here is a possible fraud scenario:

Request-debit-on-payment fraud

* Create a nice looking object that says: "Freebie: L$ 0"
* Do not set it 'For Sale', but instead llSetPayPrice(0, [DEFAULT,HIDDEN,HIDDEN,HIDDEN]);
* Create a money event and llSetPayText("Buy");
* Inside the money event, do a llRequestPermissions(id, [PERMISSION_DEBIT]);

The user will see:

An object marked "Freebie: L$ 0"
Upon rightclick, a pie menu item marked "Buy"
Upon selection of the menu item, a dialog that says "Pay L$ to object "Freebie" owned by OddesE Oh?" with button "L$ 0"
Upon payment, another dialog that says "Object "Freebie" owned by OddesE Oh wants to: Take L$ from you. Is this ok?" with buttons "Yes" and "No".

How many users do you trust with your money and this series of events?

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-12T18:02:51Z

OddesE Oh:

Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apart from the problem that PERMISSION_DEBIT is currently limitless, meaning a vendor processing L$ 10 payments needs permission to llGiveMoney(to_some_avatar, unlimited_amount), there is also conceptually a big difference between REFUNDING money or GIVING money. I don't think a function llRefundMoney is needed, but it would be very good if the difference could be expressed in permissions. You could consider changing the color of the dialog box for request DEBIT permission from blue to red (after all, it's abuse sensitive.. blue can be a bit misleading). You could then have a yellow box for request REFUND permission. You would then restrict llGiveMoney, when called under REFUND permission, to
a) Only be called from within a money event context
b) Limit the amount given to the amount received in the money event.

Furthermore I suggest you add a 'budget' parameter to DEBIT permission, so any scripts that need to give money at will to operate can be restricted in their money-giving abilities.

For an illustration of the problems we currently have with DEBIT_PERMISSION, here is a possible fraud scenario:

Request-debit-on-payment fraud

* Create a nice looking object that says: "Freebie: L$ 0"
* Do not set it 'For Sale', but instead llSetPayPrice(0, [DEFAULT,HIDDEN,HIDDEN,HIDDEN]);
* Create a money event and llSetPayText("Buy");
* Inside the money event, do a llRequestPermissions(id, [PERMISSION_DEBIT]);

The user will see:

An object marked "Freebie: L$ 0"
Upon rightclick, a pie menu item marked "Buy"
Upon selection of the menu item, a dialog that says "Pay L$ to object "Freebie" owned by OddesE Oh?" with button "L$ 0"
Upon payment, another dialog that says "Object "Freebie" owned by OddesE Oh wants to: Take L$ from you. Is this ok?" with buttons "Yes" and "No".

How many users do you trust with your money and this series of events?

LSL Useful Function WishList

2007-06-12T17:49:55Z

OddesE Oh: /* R */

__NOTOC__
{{LSL Header}}
==A==
[[llAddToEstateBanList]]
==C==
[[llChangeLandPassPrice]]

==E==
{{LSLG|llExecuteMenuCommand}}

==F==
{{LSLG|llFrandom}}

==G==
{{LSLG|llGetParcelBanList}}
{{LSLG|llGetEstateBanList}}
{{LSLG|llGetAvatarKeysOnParcel}}
{{LSLG|llGetAvatarKeysOnEstate}}
{{LSLG|llGetMyAccountBalance}}
{{LSLG|llGetGroup}}
{{LSLG|llGetGender}}
<s>llGetScriptCreatorKey</s> - use [[llGetInventoryCreator]]([[llGetScriptName]]()) instead
{{LSLG|llGetRegionPopulation}}
{{LSLG|llGetParcelPopulation}}
{{LSLG|llGetWorldPopulation}}
{{LSLG|llGetPrice}}
{{LSLG|llGetAgentPreferedLanguage}}

==I==
{{LSLG|llInstantMessageGroup}}
{{LSLG|llInviteToGroup}}
{{LSLG|llIsValidIntegerString}}
{{LSLG|llIsValidFloatString}}
{{LSLG|llIsValidVectorString}}
{{LSLG|llIsValidRotationString}}

==L==
{{LSLG|llLBETMB}}
==M==
{{LSLG|llMapTouch}}

==N==
{{LSLG|llName2Key}}

==O==
{{LSLG|llOnRegionReset}}

==P==
{{LSLG|llPizza}}
{{LSLG|position_change}}

==R==
{{LSLG|llRaiseError}}
{{LSLG|llRemoveFromEstateBanList}}
{{LSLG|llReturnObject}}
{{LSLG|llReturnOwnersObjects}}
{{LSLG|llRotateAgent}}
{{LSLG|llRequestPermissions(llGetOwner(), PERMISSION_REFUND);}}

==S==
{{LSLG|llSoundex}}
{{LSLG|llSpeakText}}
{{LSLG|llSpeech2Text}}
{{LSLG|llSpeech2TextRemove}}
{{LSLG|llSayWithinRange}}

==T==
{{LSLG|llTargetOffsetOmega}}
{{LSLG|llTeleportAgent}}
{{LSLG|llTriggerLandmark}}
{{LSLG|llTrackTouches}}

==Other functionality==
{{LSLG|Block comments}}
{{LSLG|True tab-stops}}
{{LSLG|Code Folding}}
{{LSLG|Windowed Scripting}}
{{LSLG|Switch Statement}}
{{LSLG|Array}}
{{LSLG|on_unrez|Event: Unrez / Delete}}
{{LSLG|Conditionals}}
{{LSLG|State variables}}

LSL Useful Function WishList

2007-06-12T17:49:10Z

OddesE Oh: /* S */

__NOTOC__
{{LSL Header}}
==A==
[[llAddToEstateBanList]]
==C==
[[llChangeLandPassPrice]]

==E==
{{LSLG|llExecuteMenuCommand}}

==F==
{{LSLG|llFrandom}}

==G==
{{LSLG|llGetParcelBanList}}
{{LSLG|llGetEstateBanList}}
{{LSLG|llGetAvatarKeysOnParcel}}
{{LSLG|llGetAvatarKeysOnEstate}}
{{LSLG|llGetMyAccountBalance}}
{{LSLG|llGetGroup}}
{{LSLG|llGetGender}}
<s>llGetScriptCreatorKey</s> - use [[llGetInventoryCreator]]([[llGetScriptName]]()) instead
{{LSLG|llGetRegionPopulation}}
{{LSLG|llGetParcelPopulation}}
{{LSLG|llGetWorldPopulation}}
{{LSLG|llGetPrice}}
{{LSLG|llGetAgentPreferedLanguage}}

==I==
{{LSLG|llInstantMessageGroup}}
{{LSLG|llInviteToGroup}}
{{LSLG|llIsValidIntegerString}}
{{LSLG|llIsValidFloatString}}
{{LSLG|llIsValidVectorString}}
{{LSLG|llIsValidRotationString}}

==L==
{{LSLG|llLBETMB}}
==M==
{{LSLG|llMapTouch}}

==N==
{{LSLG|llName2Key}}

==O==
{{LSLG|llOnRegionReset}}

==P==
{{LSLG|llPizza}}
{{LSLG|position_change}}

==R==
{{LSLG|llRaiseError}}
{{LSLG|llRemoveFromEstateBanList}}
{{LSLG|llReturnObject}}
{{LSLG|llReturnOwnersObjects}}
{{LSLG|llRotateAgent}}

==S==
{{LSLG|llSoundex}}
{{LSLG|llSpeakText}}
{{LSLG|llSpeech2Text}}
{{LSLG|llSpeech2TextRemove}}
{{LSLG|llSayWithinRange}}

==T==
{{LSLG|llTargetOffsetOmega}}
{{LSLG|llTeleportAgent}}
{{LSLG|llTriggerLandmark}}
{{LSLG|llTrackTouches}}

==Other functionality==
{{LSLG|Block comments}}
{{LSLG|True tab-stops}}
{{LSLG|Code Folding}}
{{LSLG|Windowed Scripting}}
{{LSLG|Switch Statement}}
{{LSLG|Array}}
{{LSLG|on_unrez|Event: Unrez / Delete}}
{{LSLG|Conditionals}}
{{LSLG|State variables}}

LlGetGender

2007-06-04T19:03:52Z

OddesE Oh:

{{LSL_Function
|func_id
|mode=request
|func_sleep=0.1
|func_energy=10.0
|func=llGetGender
|sort=GetGender
|p1_type=key|p1_name=avatar|p1_desc=agent UUID
|return_text=the gender of an agent located in the same region the script is running in.
|return_type=string
|spec
|caveats=*Works only for agents recently located in the same region the script is running in.
**Grid-wide GetGender could be provided via a [[dataserver]] call.
|examples
|helpers
|related
|also
|notes=Very useful for some special kind of products like poseballs and animations,also for attaching or detaching some body parts and access rules in some regions. <br/>
Sounds useful indeed, but should probably be agent data you can fetch with [[llRequestAgentData]].}}

LlExecuteMenuCommand

2007-06-04T18:58:34Z

OddesE Oh:

{{LSL_Function|func_id|mode=request
|func=llExecuteMenuCommand
|p1_type=list|p1_name=menu_sequence
|func_desc=Access a main menu item via a list '''menu_sequence'''.
|return_text
|spec
|caveats=Some menu items may not be available for security reasons.
NOTE: Scripts are run on the server so this function is probably impossible. -OddesE Oh
|examples=<pre>
llExecuteMenuCommand(["Client","Character","Rebake Textures"]);
llExecuteMenuCommand(["Tools","Select My Objects Only",TRUE]);
</pre>
|helpers|related|also|notes}}

LlInviteToGroup

2007-06-04T18:53:37Z

OddesE Oh:

{{LSL_Function/permission|PERMISSION_GROUP_INVITE|grant=a group officer|mode=request}}{{LSL_Function
|func_id
|func_sleep
|func_energy
|func=llInviteToGroup
|p1_type=key|p1_name=avatar
|p2_type=string|p2_name=role|p2_desc=Role name '''avatar''' is to have.
|sort
|func_desc=Adds '''avatar''' to the group the object is deeded to.
|return_text
|return_type
|spec=We need some way to invite an avatar to join the owners group if he has the right to invite members and has given the script permission to act as his delegate.

llInviteToGroup(key group, key avatar)

or

llInviteToGroup(key avatar)

would be great.

We basically need to be able to perform group administration tasks if the script owner is in the group and has the right to perform these tasks.

Depending on if the script has a ('active') group if it's not group-owned we might or might not need another function: list [[llGetOwnerGroups]]()
|caveats
|examples
|helpers
|related
|also_functions
|also_events
|notes
|mode=request}}

LlChangeLandPassPrice

2007-06-04T18:50:52Z

OddesE Oh:

To allow the access price to enter a parcel of land to be changed via a script.

[[LSL Useful Function WishList]]

LSL Useful Function WishList

2007-06-04T18:50:27Z

OddesE Oh: /* C */

__NOTOC__
{{LSL Header}}
==A==
[[llAddToEstateBanList]]
==C==
[[llChangeLandPassPrice]]

==E==
{{LSLG|llExecuteMenuCommand}}

==F==
{{LSLG|llFrandom}}

==G==
{{LSLG|llGetParcelBanList}}
{{LSLG|llGetEstateBanList}}
{{LSLG|llGetAvatarKeysOnParcel}}
{{LSLG|llGetAvatarKeysOnEstate}}
{{LSLG|llGetMyAccountBalance}}
{{LSLG|llGetGroup}}
{{LSLG|llGetGender}}
<s>llGetScriptCreatorKey</s> - use [[llGetInventoryCreator]]([[llGetScriptName]]()) instead
{{LSLG|llGetRegionPopulation}}
{{LSLG|llGetParcelPopulation}}
{{LSLG|llGetWorldPopulation}}
{{LSLG|llGetPrice}}
{{LSLG|llGetAgentPreferedLanguage}}

==I==
{{LSLG|llInstantMessageGroup}}
{{LSLG|llInviteToGroup}}
==L==
{{LSLG|llLBETMB}}
==N==
{{LSLG|llName2Key}}

==O==
{{LSLG|llOnRegionReset}}

==P==
{{LSLG|llPizza}}
{{LSLG|position_change}}

==R==
{{LSLG|llRaiseError}}
{{LSLG|llRemoveFromEstateBanList}}
{{LSLG|llReturnObject}}
{{LSLG|llReturnOwnersObjects}}
{{LSLG|llRotateAgent}}

==S==
{{LSLG|llSoundex}}
{{LSLG|llSpeakText}}
{{LSLG|llSpeech2Text}}
{{LSLG|llSpeech2TextRemove}}
{{LSLG|llSayWithinRange}}
{{LSLG|llRequestPermissions(llGetOwner(), PERMISSION_REFUND);}}

==T==
{{LSLG|llTargetOffsetOmega}}
{{LSLG|llTeleportAgent}}
{{LSLG|llTriggerLandmark}}
{{LSLG|llTrackTouches}}

==Other functionality==
{{LSLG|Block comments}}
{{LSLG|True tab-stops}}
{{LSLG|Code Folding}}
{{LSLG|Windowed Scripting}}
{{LSLG|Switch Statement}}
{{LSLG|Array}}
{{LSLG|on_unrez|Event: Unrez / Delete}}
{{LSLG|Conditionals}}
{{LSLG|State variables}}

LlChangeLandPassPrice

2007-06-04T18:49:53Z

OddesE Oh: New page: LSL Useful Function WishList

[[LSL Useful Function WishList]]

LlGetGroup

2007-06-04T18:48:38Z

OddesE Oh:

Should return the group associated with the object the running script is part of, or NULL_KEY if no group is associated with the object.

[[LSL Useful Function WishList]]

LlGetGroup

2007-06-04T18:47:09Z

OddesE Oh: New page: Should return the group associated with the object the running script is part of, or NULL_KEY if no group is associated with the object.

Should return the group associated with the object the running script is part of, or NULL_KEY if no group is associated with the object.

LlRequestPermissions(llGetOwner(), PERMISSION REFUND);

2007-06-02T00:48:21Z

OddesE Oh: New page: Currently, any script that processes payment TO an avatar needs DEBIT permission to be able to refund the paying avatar if the amount payed was incorrect or something else went wrong. Apar...

LSL Useful Function WishList

2007-06-02T00:34:04Z

OddesE Oh: /* S */

__NOTOC__
{{LSL Header}}
==A==
[[llAddToEstateBanList]]
==C==
[[llChangeLandPassPrice]]

To allow the access price to enter a parcel of land to be changed via a script.

==E==
{{LSLG|llExecuteMenuCommand}}

==F==
{{LSLG|llFrandom}}

==G==
{{LSLG|llGetParcelBanList}}
{{LSLG|llGetEstateBanList}}
{{LSLG|llGetAvatarKeysOnParcel}}
{{LSLG|llGetAvatarKeysOnEstate}}
{{LSLG|llGetMyAccountBalance}}
{{LSLG|llGetGroup}}
{{LSLG|llGetGender}}
<s>llGetScriptCreatorKey</s> - use [[llGetInventoryCreator]]([[llGetScriptName]]()) instead
{{LSLG|llGetRegionPopulation}}
{{LSLG|llGetParcelPopulation}}
{{LSLG|llGetWorldPopulation}}
{{LSLG|llGetPrice}}
{{LSLG|llGetAgentPreferedLanguage}}

==I==
{{LSLG|llInstantMessageGroup}}
{{LSLG|llInviteToGroup}}
==L==
{{LSLG|llLBETMB}}
==N==
{{LSLG|llName2Key}}

==O==
{{LSLG|llOnRegionReset}}

==P==
{{LSLG|llPizza}}
{{LSLG|position_change}}

==R==
{{LSLG|llRaiseError}}
{{LSLG|llRemoveFromEstateBanList}}
{{LSLG|llReturnObject}}
{{LSLG|llReturnOwnersObjects}}
{{LSLG|llRotateAgent}}

==S==
{{LSLG|llSoundex}}
{{LSLG|llSpeakText}}
{{LSLG|llSpeech2Text}}
{{LSLG|llSpeech2TextRemove}}
{{LSLG|llSayWithinRange}}
{{LSLG|llRequestPermissions(llGetOwner(), PERMISSION_REFUND);}}

==T==
{{LSLG|llTargetOffsetOmega}}
{{LSLG|llTeleportAgent}}
{{LSLG|llTriggerLandmark}}
{{LSLG|llTrackTouches}}

==Other functionality==
{{LSLG|Block comments}}
{{LSLG|True tab-stops}}
{{LSLG|Code Folding}}
{{LSLG|Windowed Scripting}}
{{LSLG|Switch Statement}}
{{LSLG|Array}}
{{LSLG|on_unrez|Event: Unrez / Delete}}
{{LSLG|Conditionals}}
{{LSLG|State variables}}

LlSubStringIndex

2007-06-01T18:50:59Z

OddesE Oh:

{{LSL_Function
|func_id=181|func_sleep=0.0|func_energy=10.0
|func=llSubStringIndex
|return_type=integer|p1_type=string|p1_name=source|p2_type=string|p2_name=pattern
|func_footnote=If '''pattern''' is not found in '''source''', {{HoverText|-1|negative one, 0x{{LSL_Hex/Write|-1}}}} is returned.
|func_desc
|return_text=that is the index of '''source''' in '''pattern'''.
|spec
|caveats=*Performs a literal match.
**Wildcards and RegEx are not supported.
|constants
|examples
|helpers=
An easy way to see if a string exists in another string...
<pre>
if(~llSubStringIndex(myString, str))
{//it exists
//This works because ~(-1) == 0
//It saves bytecode and is faster then doing == -1
//(It's also significantly less readable (unless you include the comments)
// and most developers I know will advice against these kind of practices. -OddesE Oh)
}
</pre>
|also_functions=
{{LSL DefineRow||[[llListFindList]]|Find a list in another list}}
|also_tests
|also_events
|also_articles
|notes
|cat1=String
|cat2
|cat3
|cat4
}}

LlGetLandOwnerAt

2007-03-16T21:30:54Z

OddesE Oh:

{{LSL_Function
|func_id=216|func_sleep=0.0|func_energy=10.0
|func=llGetLandOwnerAt
|return_type=key|p1_type=vector|p1_name=pos
|func_footnote
|func_desc=Returns the key of the owner of the land at pos.
|return_text=of the land owner.
|spec=If the land is in public domain [[NULL_KEY]] is returned. This land can be claimed by anyone with available tier. Land on the Preview grid is divvied out this way. Land on the main grid never enters public domain and is instead auctioned off by LL.

If the land is [[group]]-owned, the group key is returned (but this isn't usable for anything, since group keys cannot be used by other functions in LSL).
|caveats
|constants
|examples
|helpers
|also_functions
|also_tests
|also_events
|also_articles
|notes
|deprecated
|cat1=Parcel
|cat2=Owner
|cat3
|cat4
}}

LlInviteToGroup

2007-03-16T21:16:00Z

OddesE Oh:

We need some way to invite an avatar to join the owners group if he hast the right to invite members and has given the script permission to act as his delegate.

llInviteToGroup(key group, key avatar)

or

llInviteToGroup(key avatar)

would be great.

SEE

function llRequestPermissions, event runtime_permissions

We basically need to be able to perform group administration tasks if the script owner is in the group and has the right to perform these tasks.

Depending on if the script has a ('active') group if it's not group-owned we might or might not need another function: list llGetOwnerGroups()

LSL Useful Function WishList

2007-03-16T20:59:22Z

OddesE Oh:

__NOTOC__
{{LSL Header}}
==A==
[[llAddToEstateBanList]]

==E==
{{LSLG|llExecuteMenuCommand}}

==G==
{{LSLG|llGetParcelBanList}}
{{LSLG|llGetEstateBanList}}
{{LSLG|llGetAvatarKeysOnParcel}}
{{LSLG|llGetAvatarKeysOnEstate}}
{{LSLG|llGetMyAccountBalance}}
{{LSLG|llGetGroup}}
<s>llGetScriptCreatorKey</s> - use [[llGetInventoryCreator]]([[llGetScriptName]]()) instead
==I==
{{LSLG|llInstantMessageGroup}}
{{LSLG|llInviteToGroup}}
==L==
{{LSLG|llLBETMB}}
==N==
{{LSLG|llName2Key}}
==P==
{{LSLG|llPizza}}
{{LSLG|position_change}}

==R==
{{LSLG|llRaiseError}}
{{LSLG|llRemoveFromEstateBanList}}
{{LSLG|llReturnObject}}
{{LSLG|llReturnOwnersObjects}}
{{LSLG|llRotateAgent}}

==T==
{{LSLG|llTeleportAgent}}
{{LSLG|llTriggerLandmark}}
==Other functionality==
{{LSLG|Block comments}}
{{LSLG|True tab-stops}}
{{LSLG|Code Folding}}
{{LSLG|Windowed Scripting}}
{{LSLG|Switch Statement}}
{{LSLG|Array}}

Talk:LSL Variables

2007-02-17T19:02:42Z

OddesE Oh:

Suppose you have a global variable in a script that runs in an object that is on solid land, that is to say, the object is rezzed onto the land once and then left there for months. Can you then rely on the contents of that variable to remain stable? Will it be affected by (rolling) restarts? Could it be 'reset' to a default value (0, or NULL_KEY) at unpredictable moments?

LlSitTarget

2007-02-13T23:39:17Z

OddesE Oh:

{{LSL_Function
|func_id=238|sort=SitTarget|func_sleep=0.0|func_energy=10.0
|sort=SitTarget
|func=llSitTarget|p1_type=vector|p1_name=offset|p2_type=rotation|p2_name=rot
|func_footnote
|func_desc=Set the sit location for this object (if '''offset''' == {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} clear it)
|return_text
|spec
|caveats
|constants
|examples
|helpers
|also_functions=[[LSL_llSetSitText|llSetSitText]] [[LSL_llAvatarOnSitTarget|llAvatarOnSitTarget]]
|also_events=[[LSL_changed|changed]]
|also_articles
|notes
|permission
|negative_index
}}
{{LSLC|Stub|SitTarget}}

LlSitTarget

2007-02-13T23:37:04Z

OddesE Oh:

{{LSL_Function
|func_id=238|sort=SitTarget|func_sleep=0.0|func_energy=10.0
|sort=SitTarget
|func=llSitTarget|p1_type=vector|p1_name=offset|p2_type=rotation|p2_name=rot
|func_footnote
|func_desc=Set the sit location for this object (if '''offset''' == {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} clear it)
|return_text
|spec
|caveats
|constants
|examples
|helpers
|also_functions=[[LSL_llSetSitText|llSetSitText]] [[LSL_llAvatarOnSitTarget|llAvatarOnSitTarget]]
|also_events=change
|also_articles
|notes
|permission
|negative_index
}}
{{LSLC|Stub|SitTarget}}

LlSitTarget

2007-02-13T23:35:58Z

OddesE Oh:

{{LSL_Function
|func_id=238|sort=SitTarget|func_sleep=0.0|func_energy=10.0
|sort=SitTarget
|func=llSitTarget|p1_type=vector|p1_name=offset|p2_type=rotation|p2_name=rot
|func_footnote
|func_desc=Set the sit location for this object (if '''offset''' == {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} clear it)
|return_text
|spec
|caveats
|constants
|examples
|helpers
|also_functions=[[LSL_llSetSitText|llSetSitText]]
|also_events=change
|also_articles
|notes
|permission
|negative_index
}}
{{LSLC|Stub|SitTarget}}

LlSitTarget

2007-02-13T23:35:27Z

OddesE Oh:

{{LSL_Function
|func_id=238|sort=SitTarget|func_sleep=0.0|func_energy=10.0
|sort=SitTarget
|func=llSitTarget|p1_type=vector|p1_name=offset|p2_type=rotation|p2_name=rot
|func_footnote
|func_desc=Set the sit location for this object (if '''offset''' == {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} clear it)
|return_text
|spec
|caveats
|constants
|examples
|helpers
|also_functions=[[LSL_llSetSitText]]
|also_events=change
|also_articles
|notes
|permission
|negative_index
}}
{{LSLC|Stub|SitTarget}}

LlSitTarget

2007-02-13T23:34:02Z

OddesE Oh:

{{LSL_Function
|func_id=238|sort=SitTarget|func_sleep=0.0|func_energy=10.0
|sort=SitTarget
|func=llSitTarget|p1_type=vector|p1_name=offset|p2_type=rotation|p2_name=rot
|func_footnote
|func_desc=Set the sit location for this object (if '''offset''' == {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} clear it)
|return_text
|spec
|caveats
|constants
|examples
|helpers
|also_functions=llSetSitText
|also_events=change
|also_articles
|notes
|permission
|negative_index
}}
{{LSLC|Stub|SitTarget}}

Touch start

2007-02-13T23:28:39Z

OddesE Oh:

{{LSL_Event|event_id=2|event_delay|event=touch_start
|p1_type=integer
|p1_name=num_detected
|p1_desc=Number of agents detected touching during the last clockcycle
|event_desc=Triggered by the start of agent clicking on task
|constants
|spec
|caveats
|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:
default
{
touch_start(integer num_detected)
{
integer i = 0;
for(; i<num_detected; ++i)
llWhisper(0, "Touched by " + llKey2Name(llDetectedKey(i)));
}
}
|helpers
|also_header
|also_events
|also_functions
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Touch
|cat2=Detected
|cat3
|cat4
}}

Touch start

2007-02-13T23:27:55Z

OddesE Oh:

Touch start

2007-02-13T23:27:11Z

OddesE Oh:

{{LSL_Event|event_id=2|event_delay|event=touch_start
|p1_type=integer
|p1_name=num_detected
|p1_desc=Number of agents detected touching during the last clockcycle
|event_desc=Triggered by the start of agent clicking on task
|constants
|spec
|caveats
|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:
<lsl>
default
{
touch_start(integer num_detected)
{
integer i = 0;
for(; i<num_detected; ++i)
llWhisper(0, "Touched by " + llKey2Name(llDetectedKey(i)));
}
}
</lsl>
|helpers
|also_header
|also_events
|also_functions
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Touch
|cat2=Detected
|cat3
|cat4
}}

Touch start

2007-02-10T03:49:32Z

OddesE Oh:

{{LSL_Event|event_id=2|event_delay|event=touch_start|p1_type=integer|p1_name=num_detected|p1_desc=Number of agents detected touching during the last clockcycle|event_desc=Triggered by the start of agent clicking on task|constants|spec|caveats|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:
touch_start(integer num_detected)
{
integer i = 0;
for(; i<num_detected; ++i)
llWhisper(0, "Touched by " + llKey2Name(llDetectedKey(i)));
}
|helpers
|also_header|also_events|also_functions|also_articles|also_footer
|notes|mode|deprecated|cat1=Touch
|cat2=Detected
|cat3
|cat4}}
{{LSLC|Stub}}

Touch start

2007-02-10T03:44:31Z

OddesE Oh:

{{LSL_Event|event_id=2|event_delay|event=touch_start|p1_type=integer|p1_name=num_detected|p1_desc=Number of agents detected touching during the last clockcycle|event_desc=Triggered by the start of agent clicking on task|constants|spec|caveats|examples=
touch_start(integer total_number)
{
integer i = 0;
for(; i<total_number; ++i)
llWhisper(0, "Touched by " + llKey2Name(llDetectedKey(i)));
}
|helpers
|also_header|also_events|also_functions|also_articles|also_footer
|notes|mode|deprecated|cat1=Touch
|cat2=Detected
|cat3
|cat4}}
{{LSLC|Stub}}

Touch start

2007-02-10T03:44:05Z

OddesE Oh:

{{LSL_Event|event_id=2|event_delay|event=touch_start|p1_type=integer|p1_name=num_detected|p1_desc=Number of agents detected touching during the last clockcycle|event_desc=Triggered by the start of agent clicking on task|constants|spec|caveats|examples
touch_start(integer total_number)
{
integer i = 0;
for(; i<total_number; ++i)
llWhisper(0, "Touched by " + llKey2Name(llDetectedKey(i)));
}
|helpers
|also_header|also_events|also_functions|also_articles|also_footer
|notes|mode|deprecated|cat1=Touch
|cat2=Detected
|cat3
|cat4}}
{{LSLC|Stub}}

Touch start

2007-02-10T03:28:55Z

OddesE Oh: