Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-8180] [Experience Tools] Please include a means of compiling experiences with scripts in the user's inventory. #15803

Closed
sl-service-account opened this issue Jan 7, 2015 · 2 comments

Comments

@sl-service-account
Copy link

Information

At the moment there is no visual means of compiling a script with an experience if the script is in the user's inventory. Saving an experience script while in the user's inventory removes the previously compiled experience.

Please include a means of compiling experiences with scripts in inventory.

Thanks.

Original Jira Fields
Field Value
Issue BUG-8180
Summary [Experience Tools] Please include a means of compiling experiences with scripts in the user's inventory.
Type New Feature Request
Priority Unset
Status Closed
Resolution Expected Behavior
Reporter Lucia Nightfire (lucia.nightfire)
Created at 2015-01-07T02:06:01Z
Updated at 2017-06-16T20:07:35Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2015-01-07T13:14:29.228-0600',
  'How would you like the feature to work?': "At the moment there is no visual means of compiling a script with an experience if the script is in the user's inventory. Saving an experience script while in the user's inventory removes the previously compiled experience.\r\n\r\nPlease include a means of compiling experiences with scripts in inventory.\r\n\r\nThanks.",
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': '?',
}
@sl-service-account
Copy link
Author

Oz Linden commented at 2015-01-07T19:14:29Z

We deliberately chose to ensure that the association between a script and an experience is a property of compiling in an object.

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2017-06-16T20:07:36Z

Comment posyed with permission from [~levio.serenity], who is unable to comment himself.

Tiger (Levio Serenity): This would be a very helpful feature for those of us who build experiences with a team. (I imagine this is more common than experiences all built by a single avatar.) More often than not I have to script objects not owned by me personally. I can't compile/edit experience perms inside these objects, so instead my work flow has to be, 1) rez my own prim, 2) add script, 3) fix issue/exp perms 4) take into inventory 5) delete original script and 6) replace script. If it's somewhere I can't rez, it's even more painful.
I still end up with a script with the experience perms in my inventory either way, so I'm not sure what developement/security issues might be avoided, by not having this. It just makes things harder for your experience developers. - Levio Serenity

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant