[#SVC-2721] llSetScriptState should always reset a script on stopping it

2. Second Life Service - SVC

llSetScriptState should always reset a script on stopping it

Created: 31/Jul/08 12:23 AM Updated: 13/Jul/09 12:00 PM

Return to search

Component/s:

Scripts

Affects Version/s:

1.22.4 Server

Fix Version/s:

None

Environment:

n/a server side issue

Issue Links:

Parent/Child

This issue child of:

SVC-1853 State of not-running scripts is not preserved over a region restart

Description

« Hide

Refer to SVC-1853 for background.

If a script is stopped and restarted with llSetScriptState it wil restart with all saved state, permissions and context intact.

EXCEPT when the region has restarted whilst the script was not running. If this has happened, the script will be reset and in virgin state.

Therefore, it cannot be relied upon that a script may be stopped and restarted with all state intact.

If SVC-1853 is not going to be resolved, llSetScriptState should be changed so that stopping a script always resets it, so establishing clear, 100% predictable behaviour.

If SVC-1853 is queued for real resolution, this issue should be cancelled since fixing SVC-1853 would also make llSetScriptState consistent (and in the vastly better scenario where data is preserved all of the time)

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

chorazin allen added a comment - 31/Jul/08 12:24 AM

This is complementary to SVC-1853. Either that should be fixed, or this should be.

[ Permlink | « Hide ]

EddyFragment Robonaught added a comment - 07/Apr/09 09:11 PM

Absolutlely no way should this come to pass. Ever. The whole point of llResetScript and llResetOtherScript does not need to be echoed with another function that has a different job to do if it is ever resolved (by resolved I mean fixed not shoved under the carpet).

Nobody in their right mind should vote for this.

Honestly it should be closed LL.

[ Permlink | « Hide ]

chorazin allen added a comment - 07/Apr/09 11:53 PM

As the commentary above indicates this (which is indeed a backward step in my view) is only relevant if there is no plan to fix SVC-1853, meaning that the behaviour of llSetScriptState is not predictable - sometimes the script will restart from exactly where and how it was, other times it will be completely virgin with no state, variables or permissions. Since there's no reliable way to determine which is the case, the only answer is to always reset the script. Again - assuming SVC-1853 is not addressed.

[ Permlink | « Hide ]

Strife Onizuka added a comment - 22/May/09 01:54 AM

This is asking for a change of behavior, thus it is not a bug report.

While I agree with EddyFragment, I wish it hadn't been stated so forcefully.

[ Permlink | « Hide ]

EddyFragment Robonaught added a comment - 22/May/09 11:17 AM - edited

/me gulps. I was young and hot headed. lolz. Learning to play nice now. If LL are going to make the effort to change the code or whatever it is they do to mend bugs, then there would be no point fixing this in such a way as to make it less useful than it should be. If they were to take the time to fix it then making it reliably retain variables and lists etc is surely the best way to mend it. I think that suggesting that any change is a good change is what got me so riled. For that I apologize. However.... (whispers) Don't give LL an option that they just might take that isn't a step in the right direction coughs and looks around furtively. Lets hope for a proper fix before they fully restrict active script quantities.