2026 week #34: SUG meeting summary

The following notes were taken from the Tuesday, August 18, 2026 Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. No video for this meeting – Pantera is on vacation.

Meeting Overview

• The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas is held every other Tuesday at 12:00 noon, SLT (holidays, etc., allowing), per the Second Life Public Calendar.
• The “Leviathan Office Hour” meetings are held on the Tuesdays which do not have a formal SUG meeting, and are chaired by Leviathan Linden. They are more brainstorming / general discussion sessions.
• Meetings are held in text in-world, at this location.

Simulator Deployments

• No deployments this week, but all simhosts will be restarted.

General Updates

• Rider Linden is focused on the next version of the VSCode plugin (for which he’s asked for anyone willing to help document to contact him)  and a further update to the Lua editor viewer.
• Leviathan Linden has been focused on anti-griefing / crash mitigation work.
• Monty Linden is hoping to get back to his work on EventQueueGet.
• Kyle Linden repeated his call for those wishing to help edit the SL Wiki to contact him.
• Harold Linden (Lua):
  • Is working on migrating most of the Luau-specific interruption and script serialization logic from the closed server repo to the SLua repo.
  • Is also , taking the time to re-engineer things in a way that makes script bytecode-sharing and improving our garbage collection strategy easier.
  • Hopes this work will make individual server releases less bound to particular SLua repo versions by moving the “hairy” parts of the integration to SLua itself, so keeping a nice interface.
  • Those who want to do benchmarking / local running of scripts will find this work “extremely useful since you’ll be able to implement a runtime environment that’s much closer to how your scripts actually run on the server”.
  • Once this work is done, Harold plans to cut a new Lua simulator release.
  • Simulators running the Lua code are still “remarkably stable”.
• Pepper Linden continues to work on some region crossing code, and the hope is to move their work forward as a project simulator, and progressing it through the release mechanism.

General Discussion

• The subject of a scripted means to toggle Animesh objects on/ off and enabling attachments on Animesh objects raised at the previous CCUG meeting was raised here, as requested at that meeting.
  • This included referencing New LSL llAnimeshEnabled(integer enabled); Toggle Animesh Property on/off.
  • Rider Linden indicated he was broadly in favour of the approach – with the caveat that care would have to be taken if how it works due to concerns of object return if enabling one or more Animesh objects via script (thus increasing their Land Impact by around 16) could trigger parcel object return.
  • The suggestion was to have a switch in the function so that if enabling an Animesh object (and thus increasing its LI) which would cause any start-up of an Animesh object to fail if the change in LI risked triggering object return.
• The above triggered a discussion on the additional LI penalty on Animesh and its need & validity, together with the ordering object return.
  • There was some confusion on the subject of attachments – with it initially being mistaken for avatars being able to wear Animesh attachments (which is supported) and the request for Animesh objects supporting their own attachments via their skeletons.
  • The latter was proposed for “Animesh 2.0” (aka Project Muscadene) which also promised body shape and  physics support for Animesh, but this died before fully implemented when attention turned to updating Avatar complexity  / Land Impact calculations – which also subsequently died.
  • The discussion on object return related to exceeding a parcel’s Land Capacity. Currently the last object(s) rezzed will be returned if the limit it exceeded. However, if the limit is broken whilst editing an object (because it crosses between accounting models and it’s LI increases), then there is an argument to say it is the object being edited which should be returned, not the last item(s) rezzed.
  • These discussions continued through most of the rest of the meeting with no firm decisions made.
• Folded into part of this was a question on synchronising inventory on Aditi (the beta grid) and the Main grid. This should be a matter of logging-in to Aditi and then waiting for the next automated synchronising process, run (IIRC) at around 02:00 SLT each day.
• There was also a general discussion on scripting which, given I’m not scripter, I’m not even going to attempt to translate!

Date of Next Meetings

• Leviathan Linden: Tuesday, August 25, 2026.
• Formal SUG meeting: Tuesday, September 1, 2026.