Lucia Nightfire

🤨 Does that actually compile anywhere? Doesn't for me.

I also filed a feature request to allow scripts to know if an agent is departing a region as AFAIK, there isn't a 100% way to know without potential false positives using various means. https://jira.secondlife.com/browse/BUG-233192

The problem happens when an agent is unsat but the server never gets the message. Disabling then enabling the sit target does not release the stuck UUID either. I think the server should be updated to check if sit targets are really in use when the sit target is disabled and/or enabled.

See https://jira.secondlife.com/browse/BUG-232261 Aside from the above, I've seen vehicles changing regions where riders fall off or get disconnected causing sit targets to get stuck as well as agents having bad packet loss triggering it upon llUnsit() without a following disconnect/crash. I think llSitOnLink() needs another error condition handling that checks if an agent is currently teleporting/region crossing and if so, throw a new error code instead of executing, resulting in a stuck sit target.

9 pages is "quickly"? I'm surprised there wasn't a lock already.

To be fair, it is still niche in terms of adoption/uptake. I currently only see 25 users wearing Slim ATM, but it still "early". The marketing/support, though, seems to be where most of the "success" is, currently. The more awareness/content it gets, the better chance Slim will pick up more users.

Nina is one of few dozen regions that occasionally has Tiny Empires bot clusters show up.

llHash() can return negatives and modulo can handle negatives, so that return range would be -999 to 999 instead of 0 to 999, favoring < 14 even more.

Not on height alone, but I do know of cases where a height limit as an initial gatekeeper could have deterred abuse. I know of a few AFK users who were banned because of child avatars coming into an AFK venue, hopping on a sexbed with said AFKer, engaging in sex, while a third party took pics and AR'd the AFKer for *****. One of said AFKers was also the venue owner and their ban resulted in the venue being closed since the user couldn't/wouldn't use alts to continue to pay for the renting of the land. Another venue owner managed to get their ban rescinded after engaging with support for a week. If you search the forums you will find threads on this type of provocateurism and resulting discipline from LL. I have been alerted by AFK venue owners of similar attempts over the years with names of the offenders and I have witnessed it myself a few times and reported it, but have yet to see anyone wearing a child avatar banned for such behavior, only those not wearing child avatars.

I've personally seen someone on the grid wearing a male Genus head since June and have been wondering if it ever was going to be something or just a one-off. It had "M001" in the name.

The area under the left of her chin looks the same, but the rest is different, so maybe same brand, but different model?

There are other ways such as also referencing calculation of the height impacting slider values reported by llGetVisualParams(), but no way is perfect until LL gives us a means of getting bone scales/positions. The puppetry project might be the next best means.

Were you aware that adding that underscore after "CZ" in your MP listing titles hinders search results?

In the first script you can also use llGetRegionCorner() instead of waiting on dataserver replies from llRequestSimulatorData(llGetRegionName(),DATA_SIM_POS);

I was talking about Mark Kingdon.

Wasn't he from EA or am I thinking of someone else?

https://jira.secondlife.com/browse/BUG-6808

And if you ever want to know when a region last restarted without having already rezzed an object prior, you can use https://wiki.secondlife.com/wiki/LlGetEnv and "region_start_time".

There will soon be more people wearing the new Peach body than Gen.X Curvy or Gen.X Classic. 😆

File a bug report if you think you've found a bug. https://jira.secondlife.com/

The "estate_id" for https://wiki.secondlife.com/wiki/LlGetEnv is what you'd use for estate without having to set up and maintain a list of all regions under that estate.

Any of the following files in appdata > local > firestorm have LSD library data: keywords_lsl_1ed32442-4d87-1713-d156-23dd9c0456ec.llsd.xml keywords_lsl_3e156818-84b1-881a-14b1-f989bc7f9cea.llsd.xml keywords_lsl_55e840fd-ab59-a070-8a3c-0229983bbd3c.llsd.xml keywords_lsl_e0528c38-0cd1-b1aa-b2bf-711b5705fd5b.llsd.xml keywords_lsl_4b5a1c28-43ae-8e50-ef7b-11ba4c89b91a.llsd.xml keywords_lsl_3065c6a4-6499-4685-772f-463c9cc12888.llsd.xml keywords_lsl_5f772260-434c-b9df-178a-c31b16c8fd44.llsd.xml keywords_lsl_aa19a199-8cbf-4371-69a9-10d25012956c.llsd.xml The latest XML file is downloaded whenever you open the in-world script editor and go to Help > Keyword Help...

IMO, if you're asking for more L$ per sqm than the Life Properties guy(who overprices everywhere) in the same zoned district, you might not get rid of it any time soon.

Before llChar() came along I used llEscapeURL() and a harcoded value, since it was a roll of the dice with LSLEditor failing to allow hardcoded unicode between version updates back in the day.

Translation: That Premium Plus can buy a Homestead without having to own a full region "benefit" still wasn't cutting it (the overall cost) for many, so this will hopefully entice some.