secondlife / secondlife/viewer

Feature Request: Automatic Group Switch Based on Land Parcel

Open
#4,145 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team:viewer
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Summary:

A viewer-side function that automatically switches the active group to match the group assigned to the parcel the avatar is currently on — especially when attempting to rez an object or run a script.

Detailed Description:

When a user attempts to rez an object or use a script that requires land group permissions, the viewer should automatically switch the user's active group to the group assigned to the parcel (if the user is a member of that group). This would streamline the workflow for creators, shop owners, and land managers who regularly work across multiple group-owned parcels.

Suggested Behavior:

•	When the avatar enters a parcel or attempts to rez an object or run a script:

◦	The viewer checks if the active group matches the parcel's group.

◦	If not, and if the user is a member of the required group, the viewer automatically switches to that group.

◦	Alternatively, a prompt could ask the user if they want to switch to the correct group before proceeding.

Benefits:

•	Reduces failed object rezzing due to incorrect active group.

•	Enhances user experience, especially for those managing multiple parcels.

•	Prevents errors and confusion for less experienced users.

•	Streamlines content creation and land interaction workflows.

Optional settings:

•	Ability to enable or disable the feature in the viewer preferences.

•	Option for a confirmation prompt before switching groups.

•	Whitelist or blacklist for specific groups or parcels.

https://secondlife.canny.io/admin/board/feature-requests/p/feature-request-automatic-group-switch-based-on-land-parcel

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the viewer flows for parcel group permissions, active-group changes, object rezzing, and scripts, then determine how membership checks and optional prompts or preferences fit together. Done means the agreed behavior switches or prompts for the parcel group without disrupting users who are not members.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.