2023 SL SUG meetings week #13 summary

WQNC, January 2023 – blog post

The following notes were taken from the Tuesday, March 28th, 2023 Simulator User Group (SUG) meeting. They form a summary of the items discussed and is not intended to be a full transcript. A video of the entire meeting is embedded at the end of the article for those wishing to review the meeting in full – my thanks to Pantera for recording it.

Server Deployments

  • On Tuesday, March 28th, the SLS Main channel servers received the Estate Level Scripted Agent Controls (aka “Ban the Bots”).
  • On Wednesday March 29th, all simhosts on the RC channels will be updated to run the same simulator release, comprising the new LSL Functions llList2ListSlice, llSortListStrided, and llListFindListStrided (per BUG-231545). It also has a fix for DATA_SIM_STATUS from llRequestSimulatorData(), and doubles the amount of memory available for Linkset Data (LSD) to 128k.

Estate Level Scripted Agent Controls (aka “Ban the Bots”)

This is the simulator update referenced in the March 10th Lab Gab session – see: Lab Gab summary: Grumpity, Mojo & Patch – SL Mobile, land, bots & more – Bots and Policies).

  • The update includes a console variable that can be set by estate managers to either True or False. When set to True it will prevent Scripted Agents from entering regions in an estate (those required by the estate can be added to the access list so they can continue to access regions).
  • This will be supported in time by a viewer UI update to allow the option to be managed more directly – but it will still be a while before this UI change surfaces in the viewer.
  • There will be a policy change update published soon which will further cover these changes and the operation of Scripted Agents.

Further changes have been suggested within the Lab – notably to traffic – but it has yet to be decided on whether / when these will be implemented. In the meantime, please also refer to this FAQ.

Viewer Updates

On Tuesday, March 28th:

The remain viewer pipelines stand as:

  • Release viewer: Maintenance Q(uality) viewer, version Thursday, February 2.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • Maintenance S RC viewer, version, issued February 24.
    • Performance Floater / Auto FPS RC viewer updated to version, February 21, 2023.
  • Project viewers:
    • PBR Materials project viewer, version, March 23 – This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4.
    • Puppetry project viewer, version, December 8, 2022.

Reminder: LSL XML-RPC

Linden Lab is going to be shutting down LSL XML-RPC functionality completely. This was announced at the last SUG meeting, and confirmed by a later blog post. Please see either Shutting Down LSL XML-RPC (Linden Lab) or SL Scripters / creators: LSL XML-RPC shut-down (this blog) for details.

In Brief

  • This was another meeting with live music, so technical discussions were not up to the usual amount.
  • There was a general discussion on testing vehicle region crossings and on the deployment of the LSL functions currently being deployed and mentioned above. Please refer to the video for details.


2 thoughts on “2023 SL SUG meetings week #13 summary

  1. “Ban the Bots” – Sounds great, lets stamp them out… We do so hate it if a bot flies onto our lands, they must be up to no good, right?

    They have to be declared as bots for this “bot variable” to work. What about all the Tiny Empire bots that people make to cheat at the game in SL. Because bots are not allowed apparently in TE so I have been told, many don’t declare them as bots and so call them alts, yet still control them with programs and scripts.

    How will the bot companies get around this “bot variable”? I think simply not declaring them as bots.


    1. Yeah… the process is flawed by the Honesty Principle (“you will declare all your Scripted Agent accounts through their account dashboard”) – which people can avoid either a s result of not wanting to – or, in fairness, simply not realising flagging is required. The policy is supposedly being tightened up to handle those who don’t do so; but frankly, I’m not holding my breath for anything radical that will see a decent balance between legitimate use and the also legitimate concerns about the data-scrapers.


Have any thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.