Detecting NoScript Land.

I'm working on a jetpack. It's a pretty simply item really, but I'd like to make the special FX work in no-script zones. Why? well the reason may not be as obvious as you think.

When you're flying around, a jetpack has flames and lights and sounds and all that, and when you land.. all of that is supposed to turn off. But if you land in a no-script area (or worse, teleport into one)... your flames and smoke and all that are going to be going and going until you either unwear the thing, or fly up 45 m and fall down.

Now, I know that you can use TakeControls to sneak in "under the radar".. and that's really not terribly inappropriate in this case. But a lot of my effects use subscripts in certain prims in the linkset.. because using SetLinkPrimitiveParams can be.. well.. sluggish.

So I've written my script to use llMessageLinked... but of course, the subscripts in the linkset can't run unless they ALSO llTakeControls. So the idea came to me, that if I could just somehow detect in the core script, if scripts were disabled.. then I could use SetLinkPrimitiveParams... and if scripts were fine, I could use llLinkMessage.

BUT.. llScriptDanger is the only thing I can find for "getting an idea" if scripts are disabled. Is there some magic that can be done, to determine JUST if SCRIPTS are disabled? I'm getting a LOT of false positives with llScriptDanger.

llGetParcelFlags, perhaps?

I agree, and some sources suggest that llScriptDanger is semi-deprecated in favor of llGetParcelFlags anyway.

Thinking out of the box a bit, another way might be to implement some sort of "dead man's switch" where a timed script sends keepalive messages indicating all is well with script functionality; when these messages fail one assumes that scripting is disabled and falls back on SetLinkPrimitiveParams.

Probably a silly idea unless llGetParcelFlags turns out to be expensive in some way (I have no idea if there's a delay built into it, for example), but there it is.

Have you tried something like "llTakeControls(0, FALSE, TRUE);' in the helper scripts to see if that gives you the loophole without interfering with other control scripts?

That does survive no script land, but each child prim set up that way puts up a permissions dialog.

'zactly!

It looks like llGetParcelFlags is the key, along with a test for the difference between current height and llGround. *more than 45m above the ground, and I can use llMessageLinked again.

The biggest complaint I have at this point, is the lack of a llSetLinkPrimitiveParticles.

Oh well. LSL is about compromise.

In an attachment? Really? Because they are in child prims or something?

Yup, only the root prim gets the no dialog magic, all the others have to ask.

Not sure how it helps with the particles, though. Is there some magic for turning off particles in child prims from a script in the root?

I was thinking along the same lines as Anti... a timer with some pings, no pings over the timer event range and there's you're no script land.


http://www.secondscripter.com/