LSL Wiki : llSetTimerEvent

llSetTimerEvent(float sec)

Sets the timer event to be triggered every sec seconds. Passing 0.0 (or just 0) stops further timer events.

The timer persists over state changes, but gets removed when the script is reset.
It should be noted that, perhaps due to event delay, you can't get more than 25 timer events per second. And so setting the interval lower than 0.04 has no real effect, except filling up the event queue.

default
{
    state_entry()
    {
        llSetTimerEvent(300); // five minutes: 5*60--no need to make LSL do this simple calculation
    }

    timer()
    {
        llOwnerSay("timeout");
//      llSetTimerEvent(0);   (to stop the timer)
    }
}

Calling llSetTimerEvent replaces any existing timer value, and resets the countdown. In other words, if you call llSetTimerEvent(n) every n-1 seconds, the timer() event will never fire.

To stop the timer, call llSetTimerEvent(0.0). It's good practise to do this in the state_exit() event of any state which uses a timer to avoid unintentionally having a timer running in the next state.

This article wasn't helpful for you? Maybe the related article at the LSL Portal is able to bring enlightenment.

functions | events | timer

There's a difference between the minimum "useful" value, and what Zenthere asked, which is the minimum positive number you can give it that llSetTimerEvent() will distinguish from 0.0 (which shuts it off). So Keknehv was right.

-- LexNevaForgotHerPassword (2006-06-04 15:50:35)

Am I correct in assuming that only one llSetTimerEvent can be active in a state at one time? In other words, if I set the timer to 20 seconds in one part of my script, and later decide I want a timer event to be triggered in 1 second, does the second call to llSetTimerEvent replace the previous call, or does it add another one?

-- TexArmistice (2006-08-06 11:39:29)

There seems to be a long standing issue where timers simply stop working for objects left out, usually after a sim restart or crash. Is there any work around for this? Using llSensorRepeat to restart the timer perhaps?

-- HeatherGoodliffe (2006-12-26 11:06:09)

This gets extremely inaccurate for short intervals (.1 sec or so) if there are more than about 4000 or so active scripts in a sim. It seems more of an issue with the number of scripts than how many instructions are being executed. If there are around 10000, it can be off by a factor of 4 or more for .1 second intervals. For intervals around 1 sec, it is much less sensitive, it seems to be an interrupt latency kind of issue.

-- RalphDoctorow (2007-01-06 11:49:25)

I am trying to scale an object at a rapid rate, using the timer event. Even though I set the timer to be 0.022 it still performs the scale every second instead. Is there a reason for this?

-- cpc1-hudd4-0-0-cust709.hudd.cable.ntl.com (2007-03-21 07:53:32)

If I call llSetTimerEvent(60) in my script, and then elsewhere (presumeably later) call llSetTimerEvent(60) again, does it reset the timer or continue with the original?

Meaning can I set a timer for certain events to occur and
A) they DO occur so I - 1-reset the timer, 2-{do other actions} 3-go back to waiting
B) they DO NOT occur so I - 1-do some actions

If I am using llSetTimerEvent(60) and the timer is reset at each call, I am fine, but if the timer does not actually reset there may (read WILL) be a problem. I am currently doing 2 call to reset the timer
{
llSetTimerEvent(0);
llSetTimerEvent(60);
}

but this is so wastefull, if not needed.

-- DavidSoon (2007-06-22 16:24:28)