✨ Feature Requests

Currently, we can attach a maximum of 38 attachments, but since objects attached to the "HUD" position are also counted in the total, it's sometimes impossible to wear more. This phenomenon is particularly noticeable for furry users. After equipping the necessary furry parts, there are often only 5-6 attachment slots left, along with some commonly used HUD adjustments for body or other parts, leaving almost only 1-2 slots, or even none, for clothing. I hope there can be a separate limit on the number of objects attached to the HUD position, independent of the attachment count.

Add the ability to create a Base Outfit, so you can add it to any outfit and put back your huds, jewelry etc.

How about this: on the page to offer partnership to someone ( https://secondlife.com/my/partners.php ) let's add an option to offer to share your last name with your partner. If your partner accepts the proposal, their last name will be replaced with the last name of the offering partner. The partner having their last name replaced will keep this new last name as long as they remain partnered and will have their last name fall back to their previous last name if and when unpartnered. Using this option will add extra cost to the partner offer, about the same as what is paid to change last our own last name. Will be paid by the offering partner. At any time, any partner can decide to break the partnership. The one who does the break will have to pay as much for having their previous last name back or they can select an cheaper option to break the partnership and revert back to a regular Resident last name.

I suggest an enhancement to the Bakes on Mesh (BOM) system by introducing an opacity option for BOM layers. As a designer, the current limitations of BOM force us to add additional mesh layers, particularly for makeup applications. This increases mesh complexity and necessitates the use of complex HUDs. Enabling opacity control on BOM layers could eliminate the need for extra mesh layers, thus optimizing mesh complexity and enhancing overall performance. Additionally, this would allow for greater flexibility and creativity, as BOM makeup layers wouldn’t be limited to one or two mesh layers (depending on the number of mesh layers created by a designer). With the recent introduction of 2k BOM textures, the capability to adjust blend modes directly on BOM layers would be highly beneficial for both designers and users. It would offer more customization options and improve the user experience. It would positively impact the creative community and contribute to a more streamlined and efficient design process.

Change or create a new file type for the application of Alphas to avatars. THE PROBLEM. Classic and Mesh avatars need Alpha clothing to be worn to hide avatar bodies from poking through Clothing attachments. Currently you can do this efficiently with a simple Alpha clothing file thanks to the introduction of BoM. But many mesh avatars still use a very render heavy system of multiple face layers of mesh and use HUDS to 'apply' masking, becasue it's easier and quicker for the user than having to browse through folders full of many Alpha Clothing files. ANSWER Would it be possible instead allow avatar creators the ability apply alphas clothing files efficiently via LSL script instead of creating these HUD systems, reducing the amount of mesh and render costs needed for these quicker easier Masking options? If we can Set a material change, can't we set an Alpha change either by using a UUID of existing alpha file or a new file type? llSetRenderAlpha(AlphaUUID);

I'd love to be able to have the body and my head shapes be separate. Right now the shapes are tied together as one shape. I would love to be able to say, purchase a head shape someone has created and be able to apply it without changing my body shape as well.

Improve the 'show only friends' feature and allow us to see everyone or only friends without having to teleport to see everyone again (previously this was done by changing groups, but it no longer works)

As tittle said "Support Shape Keys or blend Shape from unity" This would give SL sooooooo much potential to express item or avatar. And this will expand SL life spend way further more. You guys even implanted PBR system in SL, why not shape keys?

It would be really nice to be able to scale the our whole avatar with a global scale slider so we can be really big or really small without changing our shape valaues, Idealy this would act much the same as the hover height slider. This would also increase or decrease this scale of hitbox to match the new scale. Additinally it would be great to have a LSL function to control it like llSetAgentScale(float scale_value); or something to that effect that sets the scale of the owner of the object. If a permissions request is required I would be fine with that as well.