[BUG-41011] Scripts Hybernate

[sl-service-account]

How would you like the feature to work?

When script memory in a region is overloaded, scripts are turned off. This includes No-Mod scripts. We all know, some people have left Second Life. Some of those No-Mod scripts are No Copy created by those who may no longer be on SL. This could be a problem. Many times, not being able to turn the scripts back on is a problem (Destroys them). Why not make it where scripts in the region reaches the threshold, instead of turning off the scripts, it puts them into a hibernation mode. This way, to the region, the scripts look as if they were off. To the hud, they are still turned on. This way, nothing is turned off due to overloading and saves lots of headaches... Not to mention, if the agent has tons of huds on, saves them hours of headaches trying to replace each one and relink them to their outfits. The only other option that I could see that would accomplish the same thing is create a button under the other options in the pull down menus that say turn on all attached scripts (this would include no mod/no copy scripts).

Why is this feature important to you? How would it benefit the community?

I have had huds/attachments destroyed from script killers... I had this happen two nights ago at Sandbox Island TG matter of speaking. It takes hours replacing tons of huds and attachments that have scripts in them. Sometimes the attachments are irreplaceable due to the creator leaving SL. That is a huge inconvenient. This would circumvent the situation for me and anyone else in this boat.

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-41011 | | Summary | Scripts Hybernate | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Created at | 2016-12-07T22:10:27Z | | Updated at | 2018-08-06T15:29:58Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2016-12-07T18:27:33.187-0600', 'How would you like the feature to work?': 'When script memory in a region is overloaded, scripts are turned off. This includes No-Mod scripts. We all know, some people have left Second Life. Some of those No-Mod scripts are No Copy created by those who may no longer be on SL. This could be a problem. Many times, not being able to turn the scripts back on is a problem (Destroys them). Why not make it where scripts in the region reaches the threshold, instead of turning off the scripts, it puts them into a hibernation mode. This way, to the region, the scripts look as if they were off. To the hud, they are still turned on. This way, nothing is turned off due to overloading and saves lots of headaches... Not to mention, if the agent has tons of huds on, saves them hours of headaches trying to replace each one and relink them to their outfits. The only other option that I could see that would accomplish the same thing is create a button under the other options in the pull down menus that say turn on all attached scripts (this would include no mod/no copy scripts).', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': 'I have had huds/attachments destroyed from script killers... I had this happen two nights ago at Sandbox Island TG matter of speaking. It takes hours replacing tons of huds and attachments that have scripts in them. Sometimes the attachments are irreplaceable due to the creator leaving SL. That is a huge inconvenient. This would circumvent the situation for me and anyone else in this boat.', } ```

[sl-service-account]

Lucia Nightfire commented at 2016-12-08T00:27:33Z

It would be better if public scripts had a total events per second cap as well as a cap on script count at a land owned percentage in the region.

No single public object owner should be able to consume all script timing, memory or count in the region.

[sl-service-account]

kpolke commented at 2016-12-08T07:13:13Z

That too would work

[sl-service-account]

Whirly Fizzle commented at 2016-12-08T18:45:51Z

When script memory in a region is overloaded, scripts are turned off.

Wait - is this supposed to happen? If by "turned off" you mean the script is set to not running, I really hope not - this would lead to a lot of content breakage if the script is no mod and it cannot be set back to running. If setting scripts to not running is a "feature" when script memory on the region is overloaded, that's a really bad idea.

A region can get into a certain state because of griefer objects on it which causes all scripts in attachments worn by any avatar who enters the region to be set to not running, thus permanently breaking any attachments where the scripts are no modify. Maestro saw this happen on Bug island - see BUG-2364

There is also the case where an EO/EM can disable a script in Top Scripts - see SVC-4143 This will also permanently break any no mod script, but at least only the EO & EM's have this power.

[sl-service-account]

kpolke commented at 2016-12-10T02:22:37Z

Yes. That's exactly what happens. The scripts in the sim overload the script's ability to run more scripts. In essence, it then causes all scripts in the region to turn off (running unchecked). Yes. It does cause problems. especially when the scripts are no mod. And worse, no mod and no copy. And even worse, No mod, No Copy, and the seller is no longer on SL. Yes, I could see Bug Island. Two things come to mind when it comes to Bug Island. 1) Greifers tend to hang there (not as much lately as they have migrated to another region 2) Bug Island is considered a testing sandbox. Almost anything goes. A few days ago at Sandbox Island TG, one of my avatars had to replace ALL of her huds due to a script killer. I have had to do the same thing on here about 4 or 5 times since my rez date on this avi. Script killers are a huge problem when it comes to keeping huds in good-working-order.

[sl-service-account]

Whirly Fizzle commented at 2016-12-10T15:21:13Z

Do you have a repro object that will reproduce all scripts in the region being set to a not running state that you could give to LL? I really don't think this is supposed to happen.

[sl-service-account]

kpolke commented at 2016-12-11T03:04:19Z

No. I was under the assumption that they already knew of the problem. I will ask someone that I know when I see her online to see if she still has her dead scripts

[sl-service-account]

kpolke commented at 2016-12-11T17:11:53Z

She still has one of her destroyed HUDs. However, she also said that it was no Transfer (and I think that she said no copy). She was at the same attack that I was that destroyed my last set of Huds the other day.

[sl-service-account]

Phantom Ninetails commented at 2016-12-12T02:55:09Z

All you have to do, to cause content loss to other people who enter the region, is insert a sufficient amount of scripts into the region. It is actively exploited in sandboxes and linden telehubs. People have been doing this for at least a year. Wear about 45,000 scripts in objects. Any scripts entering the region afterwards (such as attached to another resident) will be set not-running, permanently.