✨ Feature Requests

  • Search existing ideas before submitting- Use support.secondlife.com for customer support issues- Keep posts on-topicThank you for your ideas!
Reselect Previous Object Selection
When a user has selected multiple objects and accidentally deselects them, provide a command and/or keyboard shortcut to restore the immediately previous selection. The viewer could retain the UUIDs of the previous selection until a new selection is made. Why this would be useful: A lot of the time, when moving store content around or building, it is very easy to lose your selection of objects. You can then spend quite a bit of time having to manually re-select everything. It can also happen when moving parts of a build. Sometimes, due to lag, moving something too quickly, or other unexpected behavior, the entire selection can become deselected. If you were working with a large number of objects, you then have to go back and find and select everything again. A “Reselect Previous Selection” option would make building, organizing, and moving content significantly faster and less frustrating. I know you can drag a selection box around objects to select multiple items more quickly, but this isn't always practical. On regions with dense builds, dragging a selection box can select all kinds of unrelated objects. You then have to manually deselect the things you don't want and reselect anything that was missed. Having the ability to simply restore the previous selection would avoid all of this. For example: Select 30 objects > accidentally deselect > press a keyboard shortcut > the same 30 objects are selected again. Even keeping the last 3 selections in a small selection history would be extremely useful for builders, content creators, and residents. Thanks
1
·
Content Creation
Separate Offline Message Limits for Instant Messages and Group Notices
Currently, there is a single cap that applies to both private instant messages and group notices received while offline. This can create a significant problem for users who belong to many groups, especially when those groups send a large number of notices. Because both types of messages count toward the same limit, group notices can quickly fill the offline message queue. When we log back in, we may receive a large number of group notices until the delivery limit is reached, with no way of knowing whether important private instant messages were prevented from being delivered. In some cases, we don't find out that someone sent us an offline message until hours later, when that person asks why we never responded. I'd like to propose separate offline delivery limits for private instant messages and group notices. For example, as a Premium Plus member, my current limit is 240 messages total. Because I receive a lot of group notices, I frequently hit that limit while offline. I've had people become upset with me for not responding to messages that I never actually received because the cap had already been reached. Under this proposal, instead of having a single limit of 240 messages for everything, Premium Plus members could receive up to 240 offline instant messages and up to 240 offline group notices separately. Users on other membership tiers could retain their existing limits, but those limits would also be separated between instant messages and group notices. Separating these limits would greatly reduce the chances of important personal messages being lost simply because a user's offline queue was filled with group notices.
3
·
Communication
·
tracked
Load More