[BUG-227416] Lengthen LSL-timed bans in line with ability granted in viewers

[sl-service-account]

How would you like the feature to work?

Currently one can manually set temporary land bans through viewers to ~1 year, but the LSL function llAddToLandBanList() still caps the time to a FAR lower maximum of 144 hours (6 days)—it accepts higher values, but the effected ban will still capped to that.

There’s no particular reason for the LSL function not to match viewer-based possibilities, so the llAddToLandBanList(key avatar, float hours) should remove that 144 hours internal cap, and allow (and actually effect) the same values as official viewer-entered bans.

Why is this feature important to you? How would it benefit the community?

Many places, from small clubs to large, community-based regions, rely heavily on as much flexibility as LSL will allow, to extend local governance & access management to trusted employees through script-based systems; and all of these places could certainly use the same flexibility in temporary ban lengths that the official viewer now offers, especially given the (considerably limited) featureset of broader region-based bans, which still don’t have a much-needed expiry date option.

This feature would bring the LSL command in line with what’s newly available in the viewer.

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-227416 | | Summary | Lengthen LSL-timed bans in line with ability granted in viewers | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Labels | server-team | | Reporter | Landaree Levee (landaree.levee) | | Created at | 2019-07-29T19:18:08Z | | Updated at | 2022-11-03T19:56:34Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2021-12-21T17:39:34.007-0600', 'Epic Link': 'SL-14375', 'How would you like the feature to work?': 'Currently one can manually set temporary land bans through viewers to ~1 year, but the LSL function llAddToLandBanList() still caps the time to a FAR lower maximum of 144 hours (6 days)—it accepts higher values, but the effected ban will still capped to that.\r\n\r\nThere’s no particular reason for the LSL function not to match viewer-based possibilities, so the llAddToLandBanList(key avatar, float hours) should remove that 144 hours internal cap, and allow (and actually effect) the same values as official viewer-entered bans.', 'Original Reporter': 'Landaree Levee (landaree.levee)', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': 'Many places, from small clubs to large, community-based regions, rely heavily on as much flexibility as LSL will allow, to extend local governance & access management to trusted employees through script-based systems; and all of these places could certainly use the same flexibility in temporary ban lengths that the official viewer now offers, especially given the (considerably limited) featureset of broader region-based bans, which still don’t have a much-needed expiry date option.\r\n\r\nThis feature would bring the LSL command in line with what’s newly available in the viewer.', } ```

[sl-service-account]

JIRAUSER339840 commented at 2021-12-21T23:39:34Z, updated at 2021-12-22T02:12:31Z

For the record: the {}Viewer{}'s maximum land ban duration is set to 8766 hours in the configuration file: {_}.../skins/default/xui/en/floater_banduration.xml{}.  It is possible to modify this value in a Viewer installation, however the value used by the llAddToBanList() is currently hard-coded in the server binary.  It wouldn't be easy to coordinate the two, but it would be easy to make the {}Server{}'s hard-coded value agree with the default value in the Viewer config.

[sl-service-account]

Torric Rodas commented at 2021-12-22T09:32:20Z

Hi Leviathan,

The feature request Landa put through for this was to assist with scripted security orbs etc. To permit them to impose a timed parcel ban for longer than 6 days, which is the current maximum.   He mentioned the viewer being able to ban for longer to highlight the disparity between the two timed bans.  But it is the  llAddToLandBanList command being lengthened that we are specifically interested in.

[sl-service-account]

Landaree Levee commented at 2021-12-22T11:10:40Z, updated at 2021-12-22T12:44:01Z

The idea being that if one sends a llAddToLandBanList(, 1000) command through script execution, it will ban that avatar for 1,000 hours, rather than capping it to 144h. as it currently does.

This way, trusted officers can effect such ban lengths through a scripted security system deployed & controlled by the owner, without needing to become land owners themselves to do it manually.

[sl-service-account]

JIRAUSER339840 commented at 2021-12-22T18:52:07Z

Yes, this would be a straightforward change on the {}Server{}'s LSL implementation.

One thing I'm wondering is... Is 8766 the right maximum duration for {}llAddToLandList(){}?  Perhaps it should be something big enough that we never need to bump it again.  So... something like 8766000 hours (1000 years).  Or put another way: Why should llAddToLandList() prevent a landowner from banning another Resident forever?  What is the benefit of limiting it to only one year?