On_Rez - llResetScript

Hiyas Everyone,

I have been adding the following code to my scripts:

on_rez (integer start_param)
{
llResetScript();
}

Has anything changed to where this would not be necessary anymore?

Thanx!

nothing has changed... A script will not reset unless you tell it to..

It's not ever been really _necessary_...

That said, I do do it frequently on objects that don't have a big start-up cost just because it seems like an easy/cheap way to clean things up and sorta start fresh.

For something that does have a lot of start-up cost, like maybe something that reads in a notecard config or does other asset/database things, I'd think twice before doing that..

The main reason most people include that code in their scripts, is that they want to be able to test the script while working on it but also know that it will work properly for end users.

The problem is that scripts have essentially two "entry points" - state_entry() and on_rez(). When you "save" a script, state_entry() runs, but on_rez() doesn't, and the script starts from a fresh state. When one of your customers rezzes your object, on_rez() runs, but state_entry() doesn't, and the state is not fresh. The code above basically ensures that the script starts from state_entry() in a fresh state no matter which of these happened. It's appropriate for some scripts but not for others (and it wasn't ever a bug, so it isn't likely that "something will change so it won't be necessary".

Okies... thanks everyone. I dunno where I picked it up but I always had the distinct impression that there was a bug and that this was a necessary hack. Fortunately, I do prefer that all (so far) of my scripts start from a refreshed state. Thanx again!

if the script isn't storing any data, or relying on one time defaults in the start up (like llGetOwner) it isn't usually necessary...

if llGetOwner is the only problem, it's easy enough to reset it in the changed event on new owners, or if llGetOwner is being stored, just restore it on owner changed.