Difference between revisions of "LlGetParcelBanList"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{LSL_Function|func_id | {{LSL_Function|func_id|func_sleep=0.1|func_energy=10.0|func=llGetParcelBanList|sort=GetParcelBanList|func_desc=Returns a list of all agent names currently banned on parcel. | ||
|return_text|spec|caveats|examples|helpers|related|also|notes=we can add, and we can remove bans - but we can't fully manage the parcel ban list to its full potential. While the 300 name limit is generous, we could leverage this function to know exactly what is on the ban list at all times, and fully sync it up with an external database.| | |return_text|spec|caveats|examples|helpers|related|also|notes=we can add, and we can remove bans - but we can't fully manage the parcel ban list to its full potential. While the 300 name limit is generous, we could leverage this function to know exactly what is on the ban list at all times, and fully sync it up with an external database.|mode=request}} |
Latest revision as of 12:57, 25 February 2007
LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
LSL Feature Request | |
The described function does not exist. This article is a feature request. |
Summary
Function: llGetParcelBanList( );REQUEST | Function ID |
0.1 | Forced Delay |
10.0 | Energy |
Returns a list of all agent names currently banned on parcel.
Caveats
Examples
Notes
we can add, and we can remove bans - but we can't fully manage the parcel ban list to its full potential. While the 300 name limit is generous, we could leverage this function to know exactly what is on the ban list at all times, and fully sync it up with an external database.