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. So if you change to a state that has a timer() event, with the timer still running, it will fire in the new state.
• Setting a new timer replaces the old timer, and if called faster than the timer can ever trigger will result in no timer event ever firing.

All Issues ~ Search JIRA for related Bugs

Examples

<lsl> // default of counter is 0 upon script load integer counter; float gap = 2.0;

default {

   state_entry()
   {
       llSetTimerEvent(gap);
   }

   touch_start(integer total_number)
   {
       llSay(0, "The timer stops.");
       llSetTimerEvent(0.0);
       counter = 0;
   }

   timer()
   {
       ++counter; 
       llSay(0,
           (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> <lsl> // The timer event will never fire. default {

   state_entry()
   {
       llSetTimerEvent(5.0);
       // Sensor every 2.5 seconds
       llSensorRepeat("", NULL_KEY, FALSE, 0.0, 0.0, 2.5);
   }

   no_sensor()
   {
       llSetTimerEvent(5.0);
   }
   
   timer()
   {
       llSay(0, "I will never happen.");
       llSay(0, "Well, unless llSensorRepeat() magically finds something,"+
                   "or maybe there's 2.5+ seconds of lag and the timer()"+
                   "event queues.");
   }

}

</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

Signature
function void llSetTimerEvent( float sec );