✨ Feature Requests

Gacha is an unethical predatory practice designed to abuse the psychology of neurodivergent individuals and individuals who are prone to addiction. It obfuscates the cost of an item by a series of small payments that prey on a humans inability to really understand what is being spent. Its use in gaming has been for the express purpose of generating wealth beyond the true worth of an item through exploitation. If you are going to allow this predatory monetization in your game than you might as well allow a traditional slot machine or a roulette table because they are functionally the same thing. There are no solutions that make this ethical. And lets face facts you don't have the manpower to regulate the current grid in a timely manner. This is a huge undertaking and predatory monetization and other psycological tricks will be deployed in the loopholes your policy will leave open. Like NextUp which was truly not much different than gacha. Im sure this was a decision made by the CEO or the accountants. Im hoping you can find a way to put a stop to this. Its the right and ethical thing to do.

so that those problems be treated in priority as it leads to avatars being robbed their ID/psw and it then makes problems be even bigger when such campaigns are correctly managed. Example today on a well-known creator group (I replaced the fake MP store link by XXX): [09:30] Scorpiuta Resident: 💯💥FREE SUITS CHIC 💥💯💯❤️‍🔥❤️‍🔥 For Free💢💯💥💥 for the first fifty people. Significant discounts on our new product The quantity is very limited. 50%💯💥💢 off for the rest Welcome to our store XXX ... which means that the original 9 y/o avatar has been robbed its ID/psw too, with payment set as used and i prefer not to know how much L$ are going to disappear that way too. PS: One hour before a reply from LL is received saying that they are soon going to review / consider the phishing ticket means that during more than 1 hour the guys have collected victims with identity theft ... with even more accounts that they will be able to use for identity theft, leading to never ending problems.

Linden Labs, Users do not understand PBR technology and they see it as a negative based on the implementation that has transpired over the last year. PBR doesn't work for users on lower-end computers. Color mapping has changed and many do not understand this or even know that it has happened. It is important that you, Linden Labs, do your due diligence to make sure users are educated and understand PBR so that creators are actually able to make the transition to PBR without angering a portion of our user base. We hear things like, "Even on PBR viewers, I don't like how colors look." "I don't like PBR so I won't by any PBR items." "PBR should never be used on clothing." "PBR is just to make things shiny." My suggestion to combat this is for Linden Labs to produce a series of short, easily digestible to the public, tips or videos on PBR & ACEs color mapping. This will not only help users understand the reasons for the change and the purpose but why PBR is a good technology. Even asking users for tips to submit and have a place where people can view these tips to try to be able to use PBR. To be fair, I think this should start with a heartfelt apology to the community for the poor implementation of PBR and lack of education on your part. I think you'd be surprised to see how many still are not on the PBR hype train. There are many creators who have not done a single PBR release. They are still hanging on to Blinn-Phong. I suspect they worry about sales, knowledge on how to transition from BP to PBR, etc. These are all things that could be helped or solved with Linden Labs actually explaining what happened and how they are working to fix it and education on PBR and how it will help lift Second Life into the next decade.

Ever since Viewer 2 was released in 2010, Second Life's avatar height has never been accurate or equal to prim height. Prim height had been the standard used in earlier Viewer 1 viewers before 2010. Fifteen years later, we're now using Viewer 7, which still retains the false avatar height measurements from Viewer 2. Our modern avatar shapes are still taller than a comparable shape created from before 2010 in v1 viewers, or than a modern prim of same said height. Try it for yourself: Download any of the v1-based SL viewers (such as Singularity Viewer or Cool VL Viewer) and experiment with making an avatar shape with a height equal to that of a 5'10" (177 cm) tall prim (Note: this should be done without wearing a shoebase) Change to a Viewer 7 based viewer and see how the described height in a v7 viewer using this same shape has increased, yet the prim retains it's correct height! I propose that described Avatar Height in all current viewers (via Appearances menu) should be re-syncronised to the previous prim height as per pre-2010 v1 viewers. Not only would this be more accurate, it would also be beneficial to those creators who build houses or other structures where ceiling and doorway heights matter.

Problem Currently, when users need to reset their avatar's skeleton, the changes only apply locally to their own viewer. For other users to see the reset skeleton, the avatar owner must use a workaround that involves resetting their skeleton locally, teleporting elsewhere, and then teleporting back. This process is cumbersome and interrupts the user experience. Solution Implement a system where when an avatar owner resets their skeleton, it automatically sends a packet to all viewers that can see that avatar, instructing their clients to also reset the skeleton display on their end. The same functionality could be extended to animations, allowing users to clear all animations across all viewers simultaneously. Links BUG-225527 Github: Make it so that reset skeleton is a networked ViewerEffect

To Linden Lab, With the reintroduction of Gachas to Second Life, I am concerned about an unresolved and critical exploit that has long impacted artists work and livelihoods. The Bug: No Copy Gacha Duplication via Sim Crash A longstanding exploit allows users to duplicate No Copy Gacha items by: Rezzing a No Copy Gacha item in-world Picking the item back up Forcing a sim crash Upon region restart, the item can appear both in the user’s inventory and rezzed inworld effectively duplicating it. This method enables malicious users to mass copy limited items and resell them on the Marketplace at the expense of the original creator. These listings often do not show the “(Limited Quantities Available)” tag, indicating they were not legitimately obtained through the original Gacha machines. __ Impact on Creators: As a creator, it was devastating to spend weeks or months designing an entire Gacha set for events like The Arcade or Epiphany, only to see duplicated copies flood the Marketplace mere hours after the event opens. Worse still: Linden Lab's support response times (especially on weekends) have historically been too slow to address DMCA claims before significant financial damage is done. Exploiters often profit thousands of Linden Dollars before listings are even reviewed. __ Documented History & Community Efforts This issue has been widely reported over the years via: Jira reports Blogs A dedicated Discord server ("Creators Against Theft") where we actively supported each other in identifying and reporting exploiters. For reference, this 2017 blog post documents the exploit and includes a quote from Simon Linden stating: “We haven't solved all the problems outright, but we're making good strides.” https://nwn.blogs.com/nwn/2017/10/linden-lab-second-life-duplication-bug-sl.html __ Thank you for taking the time to review this request. We all want Second Life to thrive but artist must be protected if that’s to happen. Sincerely, A Concerned Creator

Currently, when I'm busy working on something, such as scripting, and can't respond to IMs, I set myself as "Unavailable". However, people who aren't physically near my avatar don't see this status—it’s only visible locally. As a result, they continue sending IMs and receive no reply, making me appear rude or dismissive. It would be ideal if we had the option to select an "Offline" status, allowing us to appear offline to everyone, including contacts. I know there's the option to disable the global "eye" icon, but this works poorly when you have more than 500 contacts, as it updates each one individually, and some contacts fail to reflect the change. An "Offline" status would be much simpler and would let us focus on our tasks without fear of disappointing friends.

The problem is that terrain blending is currently inconsistent in Second Life causing a lot of grief and even some economic issues as people can't use landscaping products as they expected the land to look the same between viewers and operating systems. Terrain textures in Second Life are historically blended by using a Perlin Noise Generator to create more interesting variation: https://github.com/secondlife/viewer/blob/develop/indra/newview/llvlcomposition.cpp#L535-L554 The Perlin Noise Generator is expected to source the random numbers from a static seed (42) for repeatable noise for stable terrain textures as per: https://github.com/secondlife/viewer/blob/develop/indra/newview/noise.h#L313-L314 However, documented in another viewer source file it is mentioned that you should use a different random number generator if you want stateful random numbers as per: https://github.com/secondlife/viewer/blob/develop/indra/llcommon/llrand.h#L34-L37 This is because the functions used "srand" and "rand" from the c++ standard library are implementation defined and can even change across compiler versions / operating systems, which is why terrain blending can look different even across TPVs even if all the relevant code is unchanged. Therefore, I request that the viewer is updated to use a stateful random number with a fixed seed going forward as it is EXPECTED to work that way, as per the code's own comments left by developers in the past.

At present, lights are clamped to an "imaginary" range of 0 to 1 that have no basis in physical reality. The GLTF spec defines a physically based light falloff and specifies real world radiometric units - which is aligned with most major game engines and 3D modeling applications. This change should apply to all sources of lights - point lights, projectors, and the sun/moon. Sun/moon would be easiest to support first.

Now that we have image thumbnails in the inventory, the next step would be to allow creators to assign images to an unpacked folder! We currently do this with a product box or include images in the folder, but it would be convenient for the customer if we could automatically assign the product image thumbnail to its folder after it's been unpacked (where it lives permanently for most people). We should be able to open a category folder, and see a populated gallery of products after they are unpacked. This would be a scripting function for unpacker scripts; assign a UUID thumbnail to the folder the contents are unpacked to. Thank you for your time!