• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-1115
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Argent Stonecutter
Votes: 14
Watchers: 6
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

General "attributes" for accounts

Created: 26/Dec/07 02:49 PM   Updated: 21/Aug/09 07:24 AM
Return to search
Component/s: Scripts, Search, Simulation
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates

Sub-Tasks  All   Open   
 Sub-Task Progress: 

 Description  « Hide
Allow users to set some moderate number of name/value attributes on their account. These attributes could be used internally by SL (for example, for the non-group titles in VWR-2212, or even to take over some of the existing Profile elements), displayed on a page in your profile, and queried and possibly even set by LSL scripts.

Attributes could be shared read-write or read-only, and shared with anyone, friends, or members of a group. For example:

pub/description - used by text-mode clients for "look" actions.
pub/title - title for "none" group (VWR-2212).
friends/aim - share your AIM only with your friends.
grp/Elfland/title - third level title for the Elfland group, for example role-playing character name.
public/species - a role-playing attribute, not specified by Linden Labs.
grp/Kombat/level (rw) - a role-playing combat attribute, not specified by Linden Labs, readable by group members, writable by group members who have the 'write attributes' ability.

Attributes that are read-only could still be set by you by LSL calls.

Sharing should include sharing by some LSL API, so that role-playing tools could use attributes... but because they're only used by such tools they wouldn't need to even be known to the sim. Eg:

key dataserver_id = llRequestAttribute(agent_key, "grp/Kombat/*"); // request names of attributes for the Kombat group (eg "level/title/hitpoints").
key dataserver_id = llRequestAttribute(llGetOwner(),"pub/species"); // request species attribute (eg 'elf').

llSetUserAttribute(llGetOwner,"species","elf"); // set in some attachment for the 'elf' avatar.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Argent Stonecutter added a comment - 26/Dec/07 02:54 PM
Link to SVC-701 because both serve similar purposes for different applications, and possibly could be merged, at least in API.

TigroSpottystripes Katsu added a comment - 26/Feb/08 05:03 AM
it would be good if there was a permission that one must grant a script so it can modify one of those user fields to prevent unwanted overwriting of stuff

Argent Stonecutter added a comment - 26/Feb/08 09:08 AM
So long as it's automatically granted to attachments. I get real tired of having dialog boxes show up when I change avatars.

Strife Onizuka added a comment - 10/Mar/08 01:16 AM
I don't see a reason why it can't be auto-grant for attachments.

Siann Beck added a comment - 12/Mar/09 04:27 AM
This was the general idea behind DataBot (http://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=357740), and while the project has never taken off, I still think there are some useful ideas in the specification. Having something like this built in would be even better, as it would save an attachment point!

Ezian Ecksol added a comment - 21/Aug/09 07:24 AM
I would appreciate this idea rather than introducing a llGetGender ..