working scripts that don't work.

How often do you write or paste a working script and then it refuses to work?

Several months ago I made a script that absolutely refused to run even though it was correct. Then when I copied the entire script text and pasted it into a new script, it worked as it was supposed to.

I've never had this happen, tho I'm not a hugely prolific scripter.

Pardon me if this is too simplistic a thought, but might it perhaps be related to persistent data? Scripts don't necessarily reset completely on_rez. Have you ever tried explicitly resetting the script (select object containing script and go to Tools menu)? (Or, if it's your script, hit reset in the script window!). If that's it, just add an llResetScript call to your on_rez function (or wherever appropriate).

Of course, that will lose any persistent data that copy of that script may be accumulating.

I've seen a asset server failure act sort of like a broken script. When you save a script there is the two line confimation:

Compile complete. Saving....
Save complete.

Or something like that. I've seen times when the "Save complete" is not shown and the script is usually left in a non-Running state and any changes you make will have had no effect.

The only workaround I know of for this is to add-a-space, delete-a-space, save again until you see "save complete". I was baffled the first time this happened as it doesn't give much indication that the save failed. Good luck.

This reminds me of a few days when I would open and edit a script while I was "wearing" an item unwear it to find out that when I rezzed it to test the change didnt take effect... even though I saw the "compiled success" message... only to have to wear/edit/unwear again for it to take effect.

FYI, the wearing is to prevent items from "llDie"-ing while you have the item out working on a script. assuming you have a short timer with "lldie" in it.


-Phid

Amiga, I (and some friends) have this problem from time to time, unrelated to save/compile/resetting script/asset server issues, our solution is the same as yours, copy the code and paste into a freshly created script. It is a rare occurrence but a puzzler none the less

I've had this one time only. no explanation.