My problem is quite simple. I do some minor scripting with vb on triggers and such, but when I make a call to enable a timer (world.enabletimer "timername", true), it fires the timer immediatly. Is there any way to fix this? I have tried an offset, but that didn't work.
/world.enabletimer
Posted by Essidus on Mon 16 May 2005 10:48 PM — 6 posts, 24,799 views.
You'll need to reset the timer too (ResetTimer "timername").
I tried that, but it didn't seem to stop the timer from firing imediatly when my alias enabled it.
Can you paste your alias (and the timer) here (paste button to copy the whole thing, not the individual fields)?
Try resetting the timer just after you enable it, doesn't seem to work the other way around.
Resetting timers is skipped for disabled ones. Thus you must enable it first. Also I have been notified of a problem with timers which fire "at" a time being wrong by hours.
This turns out to be a problem introduced with the sub-second interval timers a few versions back. Timers are currently firing "at" a time which is UTC time, not local time. This will be fixed in version 3.67.
This turns out to be a problem introduced with the sub-second interval timers a few versions back. Timers are currently firing "at" a time which is UTC time, not local time. This will be fixed in version 3.67.