No longer can stop, reset, recompile scripts you own?

Has anyone noticed that the option to stop, reset, or recompile scripts on scripts you own (if they are not modifyable) is no longer available via the tools menu??? At least now I can't reset, stop, restart, or recompile scripts unless I the script is modifyable. And I seem to remember being able to do it for people that I had their modify rights as well.

This needs to be restored. I can't count how many times I had a scripted object that I bought where it was damaged due to some server glitch and I had to reset or recompile it for it to work. Now if something goes wrong with a purchased script due to some sort of glitch it will effectively be turned into junk since I can't reset it or recompile it.

This NEEDS to be fixed. I can't imagine how this sliped by in the first place.

-DB

i don't see anything abnormal to that personally, you dont "own" a script, you are merely granted a right to use it when you get an item.

It should allow you to reset any script in any object you own. I've lost count of the poorly scripted objects I've thrown away because I couldn't reset the scripts.

In its current form the usefulness of this implementation is extremely limited to say the least.

If you own a scripted object I can't see a single reason why you shouldn't be able to stop, start and reset it. Regardless of who created it. If you damage an item in this way you void the warranty just like in RL ! But there's no reason why we shouldn't be able to do it.

I don't think it's ever been an option to reset scripts on anything you own, but I might be wrong. And yeah, there are legitimate reasons - say I give away something that has a limited number of uses, or can be used for a limited time, as a demo. Resetting it could well mean that the time or counter resets, and it might not be possible (or might be immensely awkward) to code around that.

Have no fear, Mono is coming Real Soon Now to an SL client near you, right? It will also slice bread and wash your car for you.

Ordinal, I agree that I suppose it could be a problem with a demo item. But there are not that many items around like that. And the simple away around that is to have a one copy item that self destructs after use, so when you get the demo you get say 5 copies (or however many uses you want to give). No need to script around it.

Being able to reset a script is the enlivenment of rebooting your computer. I am sure that if you were not able to reset your computer you would be upset when it crashed and you had to throw it away. Granted not as big a investment, but then again if you buy special hardware to run SL and then can't use scripts you paid for due to a server glitch or such, I suppose you could consider the investment in a lump sum since they are all tied together.

There are also times when you want to turn off the script in a object you own but don't have modify rights to. For example you may have furniture that has some odd script in it that causes you to lag, but you like the furniture. So you just stop the script from running in that piece of furniture.

I have also encounterd times where the script was stoped for some reason and I had to start it. Or that even a reset did not work and the only thing that fixed it was a recompile.

-DB

How do you think an item detects when it's been "used", or self destructs? With a script. And there are items which need time periods and can't work just on a single use (what good is a gun that you can only fire once?) Believe me, it might seem easy but it definitely isn't, even when people can't reset the scripts. Hence the fact that there aren't a lot of demo items out there.

Ok I was thinking of fireworks as my example as that shoots off and self destructs. But here is another example for you. When you "buy" the demo and rezs it for the first time it checks itself it checks the current date and adds this to the description. Then after say 2 days (or how ever long you want the demo to be usable) it self deletes or just refuses to work as the date will now be past its expire point. And how this would work even if the object was reset, is you check the description for a date on reset (or rez). If the description is blank, it adds the current date. If it has a date already it checks, and if it is expired refuses to work or self deletes.

-DB

Gee, I don't own my rental car, but I've still got the right to change a tire or refill it... and if I don't, then it's the rental company's responsibility to get a gas filler or tire changer or script resetter out to me.

Store the counter as a prim attribute. Like, the color of a transparent or black surface.

30 second solution: Impliment the timer by changing the name of a child prim in the object. object name = objectname -1, on a timer. Even if the script is reset, the timer will just resume where it left off. If the timer reaches 0, have the scrpt delete itself.

Damnit Rei. Read the whole thread next time...

Yeah, Argent kinda beat me to it. Slightly different method, but the same basic trick.

Yes just like I said previously the object description will work nicely. And will let people tell at a glance how long till the object "self destructs"

-DB