LlSetTimerEvent

Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

SetTimerEvent

llSetTimerEvent

Summary

Function: llSetTimerEvent( float sec );

107	Function ID
0.0	Forced Delay
10.0	Energy

Cause the timer event to be triggered a maximum of once every sec seconds. Passing in 0.0 stops further timer events.

• float

sec

–

Any positive non-zero value to enable, zero (0.0) to disable.

Caveats

• The time between timer events can be longer, this is caused by:
  • Time dilation - See llGetRegionTimeDilation for more information.
  • Default event delay - Only so many events can be triggered per second.
  • Event Execution - If the execution of an event takes too long.
• The timer persists across state changes, but gets removed when the script is reset

All Issues ~ Search JIRA for related Bugs

Examples

Important: Timers inside Second Life are either running, when you set the time inside the llSetTimerEvent function call to a positive float, or they are not running, when you set the time inside the llSetTimerEvent function call to 0.0. Each state in your script only has one timer, and timers keep running even when switching states. For the sake of readability I personally tend to write llSetTimerEvent( (float)FALSE ); when stopping a timer, because I read it as "stop timer". Other scripters will argue though, that 0.0 is just fine and I'm crazy. Please take care when using something like llSetTimerEvent(llFrand(5.0)) in your code. There's a slight chance of llFrand returning 0.0 and that would stop your timer. Instead write llSetTimerEvent(1.0 + llFrand(4.0)) to get a random somewhere in [1.0, 5.0).

<lsl> // default of counter is 0 upon script load integer counter;

default {

   state_entry()
   {
       // llResetTime();

       llSetTimerEvent(2.0);
   }

   touch_start(integer total_number)
   {
       // PUBLIC_CHANNEL has the integer value 0
       llSay(PUBLIC_CHANNEL, "The timer stops.");

       llSetTimerEvent(0.0);
       counter = 0;
   }

   timer()
   {
       ++counter; 
       llSay(PUBLIC_CHANNEL,
           (string)counter+" ticks have passed in " + (string)llGetTime() 
           + " script seconds.\nEstimated elapsed time: " + (string)(counter * gap));
   }

} </lsl> <lsl> // random period in between (+15.0, +30.0] // which means the resulting float could be 30.0 but not 15.0

   llSetTimerEvent( 30.0 - llFrand(15.0) );

// same results for: // llSetTimerEvent( 30.0 + llFrand(-15.0) );

</lsl>

Notes

• Notes on minimum practical llSetTimerEvent values, Second Life forum, 2011-03-21

See Also

Events

•

timer

Functions

•	llSensorRepeat
•	llGetRegionTimeDilation
•	llGetTime

Deep Notes

Search JIRA for related Issues

Footnotes

1. ^ The ranges in this article are written in Interval Notation.

Signature
function void llSetTimerEvent( float sec );