Difference between revisions of "LlGetEstateBanList"

From Second Life Wiki
Jump to navigation Jump to search
m
Line 1: Line 1:
{{#vardefine:self|self}}{{LSL_Function/negative_index|true|start}}{{LSL_Function|func_id|mode=request|func_sleep=0.1|func_energy=10.0
{{#vardefine:self|self}}{{LSL_Function/negative_index|true|start}}{{#vardefine:self|}}{{LSL_Function|func_id|mode=request|func_sleep=0.1|func_energy=10.0
|func=llGetEstateBanList|sort=GetEstateBanList
|func=llGetEstateBanList|sort=GetEstateBanList
|func_desc
|func_desc

Revision as of 14:01, 7 March 2007

Emblem-important-yellow.png LSL Feature Request
The described function does not exist. This article is a feature request.

Summary

Function: list llGetEstateBanList( integer start );
REQUEST Function ID
0.1 Forced Delay
10.0 Energy

Returns a list that is a partial list (50 entries after position start) of agents (UUID) banned on the estate.

• integer start index

start supports negative indexes.

Specification

Index Positive Negative
First 0 -length
Last length - 1 -1

Indexes

  • Positive indexes count from the beginning, the first item being indexed as 0, the last as (length - 1).
  • Negative indexes count from the far end, the first item being indexed as -length, the last as -1.

Caveats

  • This function causes the script to sleep for 0.1 seconds.
  • If start is out of bounds the script continues to execute without an error message.
  • It is limited to returning 50 entries to keep the script from crashing. (300 * 43 bytes = 12900 bytes)
All Issues ~ Search JIRA for related Bugs

Examples

Notes

we can add, and we can remove bans - but we can't fully manage the estate 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 estate ban list at all times, and fully sync it up with an external database.

See Also

Articles

•  Negative Index

Deep Notes

Search JIRA for related Issues

Signature

//function list llGetEstateBanList( integer start );