Setting Scripts Inactive

Okay, I've got some misc scripts that I want to get out of my inventory, and store in a prim.

I can't see any way to mark them inactive before I do drop them in the prim (my script "storage trunk".

When I plunk them into the prim, some make the prim invisibile, some fire off particles, some turn the prim physical so it starts to fall from my skybox workshop, others then turn it into a bouncing ball so that it bounces around invisibly for days emitting particles, squeaking, and hitting neighbours on the head.

Am I missing something really basic? Please say yes, and say, oh, duh, you just have to do [lah] to make them inactive in your inventory before dropping them into a prim.

no that's about how it works.....

you can either turn them off after you drop them in, or create a new script, set to not running and then paste them in and save...

if you go with the drop method find a sandbox that doesn't run scripts, then drop them in and set them to not running

You can't make them inactive when you place them in an object. What you have to do is set the land to no scripts running and then manuelly set them to not running.

Or, if you have mod perms, simply add llSetScriptState(llGetScriptNamer(),FALSE); in the state_entry() so it automatically shuts off.

>> What you have to do is set the land to no scripts running and then manuelly set them to not running.

ooh i can do that.

but wait, what happens to Tilly (my dog) if i do? grin

If you Ctrl drag the script onto the prim it will be set to not running in the prims inventory. When you take it out of the prim, back into your inventory, I do believe it will be set back to running. I used this method for adding scripts to a supply jar when I was teaching. Just hold down Ctrl when you drag it to the prim and you'll get what you're after.

Tangentially related: Anyone have a hunch about how expensive llSetScriptState() is? Some of my systems need to have a bunch of parallel threads some of the time, but most of the time they're just sitting there in default_state waiting for a link_message, which I know consumes some miniscule amount of sim resources, so I've been debating turning them off when there's nothing for them to do. Just not sure if that's helpful or harmful, on net.

If you drag a folder containg scripts into the contents of a prim, all of the scripts in that folder will be marked 'inactive' in the prim.

Drag while holding down CTRL, the scripts will not be running after copying to the prim.

I'd be curious to have opinions on this, too. I've been turning mine off and on llSetScriptState() on the "assumption" that the background server software has to monitor all running scripts in a sim for possible events to act on, so therefore the fewer running scripts I have in stuff, the more conscientious an SL denizen I am.

But, it wouldn't be the first time in history that an attempt to be conscientious has been misguided, so would be interested in opinion on this.

HAWT! Thanks!!!!!!!!!

at a guess I'd say it'd depend on how often they are stopped/started.... I have a project that uses 2-20 sub scripts and turns off the extras... it runs overall faster, but it doesn't trigger the change in running state more than once in a configuration call, which aren't frequent... it was programatically easier to turn them off than to filter which ones needed to be on....

there's certainly an amount of overhead starting them, and it can take a few sec to start several (especially if you're reseting them too) which will spike both script prefs and time when you call a bunch. a cutoff for best use is beyond me to test (or maybe I'm lazy =)