You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
Please do not triage for two weeks. Give people time to comment. Thanks.
Problem
Most land owners or potential land owners that want to setup an experience based environment cannot do so because of several factors:
Most land owners are not scripters so most are not able to take advantage of what Experiences have to offer.
The script compile design of assigning an experience to content is not third party use friendly. Products must be open source or mod to allow their users to assign their own experiences or users are stuck using the creator's experience.
llSetExperienceKey() currently uses special keys to assign an experience to a script without checking if the script owner is an owner or contributor of the experience being set.
Solution
Repurpose llSetExperienceKey() to function with a new permission, PERMISSION_SET_EXPERIENCE.
PERMISSION_SET_EXPERIENCE must be granted before llSetExperienceKey() can be executed.
llSetExperienceKey() will now only accept actual Experience keys.
The script owner must be an owner or contributor of the Experience being set or a script error will be returned. This is similar to how PERMISSION_TELEPORT operates in a run-time environment which returns a script error if teleports are attempted for anyone other than the script owner.
Once an experience is set, PERMISSION_SET_EXPERIENCE is no longer needed. Experience perms can be requested of agents or KVP functions can be used.
Benefits
Product creators can sell Experience based products to users who can use their own experiences with them.
Additional Information
A set experience is removed if the script is reset or by llSetExperienceKey(NULL_KEY). Currently this is not the case.
PERMISSION_SET_EXPERIENCE is not auto-granted upon attach or sit.
Comments welcome. Thanks in advance for any consideration.
Feature Request - Repurpose llSetExperienceKey() to function with PERMISSION_SET_EXPERIENCE.
Type
New Feature Request
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Lucia Nightfire (lucia.nightfire)
Created at
2016-04-03T09:40:31Z
Updated at
2023-08-16T18:24:59Z
{
'Business Unit': ['Platform'],
'How would you like the feature to work?': "Please do not triage for two weeks. Give people time to comment. Thanks.\r\n\r\n\r\nh1. Problem\r\nMost land owners or potential land owners that want to setup an experience based environment cannot do so because of several factors:\r\n- Most land owners are not scripters. So most are not able to take advantage of what Experiences have to offer.\r\n- The script compile design of assigning an experience to content is not third party use friendly. Products must be open source or mod to allow their users to assign their own experiences or users are stuck using the creator's experience.\r\n- llSetExperienceKey() currently uses special keys to assign an experience to a script without checking if the script owner is an owner or contributor of the experience being set.\r\n\r\nh1. Solution\r\n\r\n- Repurpose llSetExperienceKey() to function with a new permission, PERMISSION_SET_EXPERIENCE.\r\n- PERMISSION_SET_EXPERIENCE must be granted before llSetExperienceKey() can be executed.\r\n- llSetExperienceKey() will now only accept actual Experience keys.\r\n- The script owner must be an owner or contributor of the Experience being set or a script error will be returned. This is similar to how PERMISSION_TELEPORT operates in a run-time environment which returns a script error if teleports are attemtped for anyone other than the script owner.\r\n- Once an experience is set, experience perms can be requested or KVP functions can be used.\r\n\r\nh1. Benefits\r\n\r\n- Product creators can sell Experience based products to users who can use their own experiences with them.\r\n\r\nh1. Additional Information\r\n\r\nPERMISSION_SET_EXPERIENCE is not auto-granted upon attach or sit\r\n\r\n\r\nComments welcome. Thanks in advance for any consideration.",
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': '?',
}
The text was updated successfully, but these errors were encountered:
Please do not triage for two weeks. Give people time to comment. Thanks.
Problem
Most land owners or potential land owners that want to setup an experience based environment cannot do so because of several factors:
Most land owners are not scripters so most are not able to take advantage of what Experiences have to offer.
The script compile design of assigning an experience to content is not third party use friendly. Products must be open source or mod to allow their users to assign their own experiences or users are stuck using the creator's experience.
llSetExperienceKey() currently uses special keys to assign an experience to a script without checking if the script owner is an owner or contributor of the experience being set.
Solution
Repurpose llSetExperienceKey() to function with a new permission, PERMISSION_SET_EXPERIENCE.
PERMISSION_SET_EXPERIENCE must be granted before llSetExperienceKey() can be executed.
llSetExperienceKey() will now only accept actual Experience keys.
The script owner must be an owner or contributor of the Experience being set or a script error will be returned. This is similar to how PERMISSION_TELEPORT operates in a run-time environment which returns a script error if teleports are attempted for anyone other than the script owner.
Once an experience is set, PERMISSION_SET_EXPERIENCE is no longer needed. Experience perms can be requested of agents or KVP functions can be used.
Benefits
Product creators can sell Experience based products to users who can use their own experiences with them.
Additional Information
A set experience is removed if the script is reset or by llSetExperienceKey(NULL_KEY). Currently this is not the case.
PERMISSION_SET_EXPERIENCE is not auto-granted upon attach or sit.
Comments welcome. Thanks in advance for any consideration.
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: