Script loads but does not run

Hi,

I created a script using LSL plus a free LSL development environment. The tool lets you enter an extended form of LSL and then it generates a normal LSL script file. Normal in the sense that the extensions are removed.

When i copy the non extended form into my object running in world the code compiles but the events, including the default state events which i have added output messages to, do not get called.

I originally thought that it might be a bug in LSL plus so I stopped using it. However, I have recently had the same thing happen in a script that i built using the client script editor. The solution in both the LSL Plus and the script editor case was to delete the script and then start over entering the exact same code.

Has anyone else seen this behavior? I have looked at the text in another editor that allows a binary view and don't see any odd control codes.

Make sure you're in land where running scripts is allowed. There's a little icon at the top of your screen that appears if it isn't. (Hover your cursor over the icons there to see what each one means.)

Most likely, you're in "no-script" land.

I've noticed lately that at least some script errors will make the script silently stop running, like I think they made it stop spitting out exception info. For example, overflowing an integer. It just silently stops running. If you compile for "LSL" instead of "Mono" does it act the same?

No I have not tried compiling in mono. I am using the release client trying to get something working for production.

And, yes I am running on script enabled land.

Mono compiled scripts run just as well on old viewers.

From the wiki: Mono requires the 1.21 viewer to create Mono scripts. Note that no special viewer is required to run Mono scripts -- that is automatic and handled by the server.

Anyway. Just a stupid thing i've done myself once or twice. Did you remenber to click the 'Running' box.

"Anyway. Just a stupid thing i've done myself once or twice. Did you remenber to click the 'Running' box."

Uh ok. That *did* make it work. But now i'm confused. What is the point of having to explicitly set the script to 'running'? Also, the setting seems to imply 'allow to run' as it looks like it persists between unloads and reloads of the object.

Thanks for pointing me in the right direction.

Setting a script to not running makes it possible to put a bunch of them together in a box which you can then transfer to somebody else for instance.

I'm sure there are more benefits of being able to shut a script off but I can't think of any right now.

One of the big benefits of the "Running" setting is where a syntactically correct script has a logic or run-time error. The minor difficulties like trying to give out non-existent inventory aren't serious, but there's some errors (such as stack/heap collision) where you really want the script shut down until you fix the problem.

And I use it in objects that have a lot of Scripts. A controller runs full time and starts and stops slave scripts as needed to reduce lag.

By default, the Running box is checked. However, it can get unchecked if you're editing a script in an object and you save the script and close the window and it had compile errors. Next time you open it, you'll see the running box unchecked.

Overflowing an integer causes a fault? Overflowing how -- by addition, for example? Eep!

Dangit, I've been confused... Unless I can come back with an example, I take that back

Sorry

Hey, this stuff is all so simple, a moron could do it.

You must not be a moron, that's all.

What development environment tool were you using? I'm interested in extending LSLs.