Lucia Nightfire

Buy more land in the same region or have the estate owner raise the region's object bonus factor. The latter is less likely, especially if it is on Mainland.

And stalk anyone that comes onto the parcel just to say, "Hello"? Also, what is "SF"?

It's "Oberwolf Linden" helming a now, 5 month old, completely blank profile...

I've said it a million times. In regards to CEO and VP of Engineering, they're going to hire complete outsiders, people who have never logged into SL a day in their lives except to do R&D in preparation for a job.

You can also use keyframe motion up to a certain velocity/omega threshold on something the avatar is standing on and your avatar will be move with it.

I sense this thread will turn into a George Carlin homage.

"Why do they call it 'taking a dump' instead of 'leaving a dump'? I mean, after all, you're not really taking it anywhere."

It seems you're referencing objects that people can walk through/into to trigger collision based script events which typcially don't trigger with sitters unless they're sitting on physical objects. Experiences do not offer any additional functions to automatically trigger events in such environments. You will still need to use some form of timed or sensory method to detect when sitting users enter an area.

I've already answered both questions. A user does not need to be in an experience nor over experience allowed land to send them a "text". I do not understand what you mean by "triggering" and experience. You can use the script function, llAgentInExperience() to determine if a user is either over land your experience is allowed and/or if they have the experience allowed on their person and if they are, then send them a text? Sending them a "text" is not the same thing as sending them a request to participate in said experience via the script function, llRequestExperiencePermissions(). So, unless you only want to send participants texts, I'm not sure why you'd want to rely/depend on an experience to do so.

It's viewer-based animation starting/stopping fast timed to locomotion change. One big problem with using viewer based AOs is that there is no feedback on locomotion state "claims" or "stakes" like there is when using llSetAnimationOverride() where, say, if one scripted AO is overriding Walking and Running and you wear another scripted attachment that wants to override one of those locomotion states, it can check llGetAnimationOverride() to see if that locomotion state is already in use and/or if an animation in it's inventory is already bound to that locomotion state. Sadly, almost no AO maker that I've seen scripts their AOs to do these checks and instead, just overrides what is actively being used by the other AO instead of informing the wearer they need to disable or detach the other attachment that has already claimed locomotion states in order for the new attachment to work.

You don't need an experience to send someone a text or dialog message. Experiences "work" when the experience is allowed on the land a target agent is on and they have the experience in their Allowed list.

I see this all the time with the World Map waiting to show the image for the region I'm in last and with animated textures, loading everything within 30m of me first then loading the animated texture 1m in front of my camera last.

If you are using Firestorm's viewer based AO, turn it off and reset skeleton and animations. If that fixes it, the AO is using an animation incompatible with your head. If it doesn't fix it, leave the viewer based AO off, then detach all worn objects including HUDs, confirming in the "Worn" tab in your inventory that nothing is being worn, then reset skeleton and animations. Starting with your mesh head, slowly start attaching things until the issue occurs again, then you should know what is causing it. You can go in order of suspected object, such as head HUD or other head/body AOs/HUDs. Developer > Avatar > Animation Info can show you animations playing on your avatar, but their names won't resolve unless they're also in your user inventory and/or you've already resolved a list of animations in the attachment that is animating you.

WhosYour Daddy ImYour Daddy ListenToYour Daddy ObeyYour Daddy Sugar Daddy MyBabys Daddy Bone Daddy IssuesWith Daddy JokeFactory Daddy LongLegged Daddy Mac Daddy DayCare Daddy Deadbeat Daddy Iggy Pop Cherry Pop Cola Pop Tart Pop Top Pop Tootsie Pop De Sire Because someone thought "Sire" would make LL more money than "Papa". I just hope they aren't also handling budget decisions...

Do you use Malwarebytes? If so, see this bug report and the comments for how to whitelist the viewers you use in hopes of stopping teleport crashes.

So It's been over 5 months since my last report. I've been sitting on a new round of stats for a month and wanted to do a more in-depth studies such as splitting reports into body by gender and body+breast mods, but just haven't have the time to work on it lately and still wanted to release something so it's yet another head and body list. Top 300 heads with 136,093 unique wearers (up from 20,419 unique wearers) : Top 300 bodies with 145,390 unique wearers (up from 21,840 unique wearers) : Things of interest this round include: #1 is STILL holding at 40% market share. The Kupra body, as it did last round, has gained more ground, making it to #5, up from #16 last round. Caveats: The Kupra body is listed twice due to each having different creators, assuming the original creator later went with a new account to market it. There are a few "Unknown" entries where redactions were made due to the head/body either not being mesh or being an improperly branded/labeled, third-party, resold full-perm head/body. There are most likely lesser Legacy Male counts and greater Legacy Athletic Male values due to the error mentioned last round. Data is a month old, so any heads/bodies that came out within the last four weeks won't have stats data. The lists contain mesh heads/bodies from human, anime, furry, feral & robot avatars. Data was collected via "bots" traveling the grid. All manner of venues were visited to limit/reduce theme-skewed data.

Yes, this is Phoenix - Kelly The vendor location is at http://maps.secondlife.com/secondlife/Rhage/149/97/27

It will be the same thing as it is every year. Art exhibits, art exhibits everywhere!

I'm a kitsune. If you tried to eat me, you'd get major cotton mouth or be coughing up hair balls for years. https://gyazo.com/23f6283eab0d2877896e6f4c06207d7c

The reason blocked users send their victims money, typically L$1 at a time, is the hope that you'll send it back. Once you send the money back, they will then look at their transaction history and under the record where you gave the money back they will see the location you were at when you did it. This is how they stalk people.

As I mentioned in the Animesh Developers group earlier: Animesh and user avatars have to be animated separately with synchronoized animations. There is no sitting-on & following effect capability on its own. There is a feature request accepted for the capability, but I doubt we will be blessed with it any year soon. https://jira.secondlife.com/browse/BUG-100864 fwiw Also, fwiw, attach points would work similarly where you "assign" the attach points to a unrigged link and it will then "bind" to the attach point the skeleton uses and follow on an offset pos/rot.

I've only ever heard of a posted "prim limit" mean land impact, not prim/link count.

No, it's been going on since November of 2019. That's when a change was made that introduced a series of bugs like BUG-228939.

I'm not sure how llGetObjectDetails() would be used in regards to object inventory, but I have been bringing up the need for llGetInventoryDesc() for some time in the server meetings. IDK if/when a dev can make it happen, but seeing how quickly llGetInventoryAcquireTime() was implemented when I recently brought it up, maybe there is a better chance now than there was this time last year.

I still see on_rez() & object_rez() randomly not trigger in certain apps of mine. I've had to script my more critical apps to not use either.