✨ Feature Requests

Homestead islands cost around half the amount of a full region. Full regions allow for up to 110 concurrent users while Homestead islands offer a meager 20 visitors. And 5 extra ones which have to be premium. This often causes frustration with Homestead island owners as these people pay a hefty amount for their tier per month but when they have a party or event their friends often cannot teleport to their land. The proposal would be to increase user concurrency on a Homestead island to 40 avatars at the same time instead of the 20 or 25 and get rid of the 5 premium visitor rule. However there would be a hard limit for scripted agents of 5 or 10 on the region to avoid abuse or exploits of region resources. I think profit margins on Homestead islands are plenty for Linden Lab to offer people this increase in concurrency for their islands. Second Life is a social platform but if Linden Lab makes it so hard for people to have an event or party on their Homestead this doesn't help much to build up a community. Linden Lab always seem to be giving more group slots etc... I think the big paying customers who have a Homestead should get more concurrency so they can have a party or event. I get complaints from people they are not pleased their friends cannot attend their parties and I don't think this should be the case in this day and age. Especially for a platform that needs to keep its users. Thank you

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.

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)

Summary: I would like to request that Second Life expand the existing partnership system to support multiple partner slots — similar to a “Top 5” or customizable partnership list. Reasoning: The current single-partner limitation does not reflect how most residents use Second Life socially. Many users maintain complex relationship networks that include romantic partners, long-term friends, creative collaborators, D/s partners, polyamorous families, or other meaningful connections that cannot be represented within a single partnership slot. Benefits: • More accurate social representation: A multi-partner system would better reflect the diverse types of relationships that residents maintain. • Reduced platform workarounds: Users currently rely on profile picks, alts, or group titles to represent partnerships, which is inefficient and inconsistent. • Support for polyamorous and multi-role connections: Many residents participate in consensually non-monogamous or multi-partner structures, which currently have no formal representation in the viewer’s social tools. • Enhanced community engagement: Offering additional partner slots encourages deeper in-world social bonding and adds flexibility for roleplay communities, families, and collaborative teams. • Optional participation: Residents who prefer a single partner could keep the system as-is, while those who need multiple slots could opt-in to additional partner spaces. Suggestion: Introduce a system such as: • Multiple partner slots (e.g., 3–5) • Optional labels or categories for each slot (e.g., Romantic Partner, Best Friend, Creative Partner, Poly Partner, D/s Partner, etc.) • Flexible settings for privacy and visibility • Backwards compatibility for users who prefer one partner only Conclusion: Expanding partnership options would modernize Second Life’s social tools and reflect the platform’s long-standing diversity in romantic, social, and creative relationships. Implementing a multi-partner system would improve accuracy, reduce confusion, and better support the realities of resident social life in Second Life.

Often when looking at snapshots, especially around Halloween or similar times when residents wear avatars that might differ from their normal look, but also just with older snapshots in general after people have changed their appearance, it is often not obvious who is visible in a snapshot. At the time the snapshot is taken the viewer has the information who is on screen so it should be possible to add IPTC image region "Person shown" and possibly also the location where the image was taken if the person taking the snapshot opts into that. This might also allow SL specific third party sites like Primfeed to link automatically to the profiles of the relevant avatars.

Due to bodies and heads now being split into separate items by different creators across Second Life, newer Residents are finding things more of a challenge when it comes to their base needs, such as skins and shapes. More documentation needs to be provided when it comes to the Welcome Pack and the Senra and library assets to communicate that there are different UVs being used. We are seeing a lot of new users with the wrong skins on mesh or having difficulties with shapes and content also sold on marketplace that is much older and will not work with any of the library/welcome pack assets. This can lead to frustration as well as wasted purchases because the items do not work with what they need them to work with. More documentation as well as perhaps information on how to join the groups/support of those items directly could help new users, and by having assistance from the stores involved, could lead to loyalty and the desire to stay in world. This was discussed at the latest CCUG meeting

I like to have the privacy of keeping me age confidential. Just like in RL. Age should not matter. I think I speak for many.

I'd like to request a special type of BOM layer which in itself is a container, a set, of BOM layers laid out in a specific order for easy and reliable inclusion in outfits. Of course the ordering is still subject to the layer ordering rules, such as a skin layer being forced to the bottom. When editing this layer, you drag and drop the layers, and then reorder them as needed. When done, you can wear and unwear the set like any other layer, the order of the layers included in the set is kept relative to each other within the set, layers not part of the set can fall in between them when worn, due to the ordering rules. This is perhaps a variant of the idea laid out in https://feedback.secondlife.com/feature-requests/p/ability-to-combine-group-bom-layers

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.

When your viewer crashes (which seems very common these days especially when teleporting) all attachments revert back to a state when attached or logged in (if attached when logged out). This is a pain for upgrades etc as you may have paid for them & the upgrade is lost. An Avatar menu item to checkpoint attachments (i.e. saving script states, attachment positional information etc) would be most useful saving the need to log out & back in. What would, for me (scripter), be even more useful is to allow this through a LSL function (with the obvious ownership checks etc). So an upgrader which the customer has rezzed checkpoints having upgraded the scripts etc.