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 Mar 28, 2024. It is now read-only.
Since it's inception, llGetExperienceDetails() has returned a list of the following 5 elements:
string experience_name
key owner_id
key experience_id
integer state
string state_message
However, the wiki reported that llGetExperienceDetails() should also include group_id. (despite saying there were 5 components when there should have been 6)
After the release of server version 14.09.09.293969, llGetExperienceDetails() now returns a list of the following 5 elements:
string experience_name
key owner_id
key group_id
integer state
string state_message
Essentially group_id has now replaced experience_id instead of being added to the list.
This has broke all my experience applications that reset their scripts on rez or ones that are reset manually as they check if the script is compiled with an experience in state_entry().
A temporary fix for all my experience applications running in multiple regions was to assign a group to my experience. The applications now think the returned group key is an experience key.
No content prior to the change was depending on llGetExperienceDetails() returning group_id as the 3rd element.
The change is breaking existing content with the loss of experience_id.
Proposed Fix
The list returned should be 6 elements formatted as follows:
Update the wiki to state that 6 components instead of 5 are returned with the order as proposed.
group_id will be added at the end of the list as it is a new entry that was previously not returned in the prior 5 entry list.
Broken content will be fixed and newer content can make use of the new list entry.
Original Jira Fields
Field
Value
Issue
BUG-7319
Summary
[Experience Tools] llGetExperienceDetails() now returns wrong data after latest server release.
Type
Bug
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Lucia Nightfire (lucia.nightfire)
Created at
2014-09-19T06:09:40Z
Updated at
2014-09-19T16:47:29Z
{
'Business Unit': ['Platform'],
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': '?',
'What were you doing when it happened?': '?',
'What were you expecting to happen instead?': '?',
}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Information
Since it's inception, llGetExperienceDetails() has returned a list of the following 5 elements:
string experience_name
key owner_id
key experience_id
integer state
string state_message
However, the wiki reported that llGetExperienceDetails() should also include group_id. (despite saying there were 5 components when there should have been 6)
http://wiki.secondlife.com/wiki/LlGetExperienceDetails
BUG-6726 was filed and a fix was released.
After the release of server version 14.09.09.293969, llGetExperienceDetails() now returns a list of the following 5 elements:
string experience_name
key owner_id
key group_id
integer state
string state_message
Essentially group_id has now replaced experience_id instead of being added to the list.
This has broke all my experience applications that reset their scripts on rez or ones that are reset manually as they check if the script is compiled with an experience in state_entry().
A temporary fix for all my experience applications running in multiple regions was to assign a group to my experience. The applications now think the returned group key is an experience key.
No content prior to the change was depending on llGetExperienceDetails() returning group_id as the 3rd element.
The change is breaking existing content with the loss of experience_id.
Proposed Fix
The list returned should be 6 elements formatted as follows:
string experience_name
key owner_id
key experience_id
integer state
string state_message
key group_id
Update the wiki to state that 6 components instead of 5 are returned with the order as proposed.
group_id will be added at the end of the list as it is a new entry that was previously not returned in the prior 5 entry list.
Broken content will be fixed and newer content can make use of the new list entry.
Original Jira Fields
The text was updated successfully, but these errors were encountered: