egghelp.org community

[ultralord]

hello

when i put:

timer 1 procname

sometimes doesnt run the proc in 1 minite but 50 seconds

or utimer 100 procname

sometimes runs on 50 seconds can i fix that?

[Sir_Fz]

How do you know that?
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[ultralord]

i see the proc's results.. and some messages

[nml375]

Check to run timers are triggered by the "HOOK_MINUTELY" hook, which will occur whenever the minute-value has changed (usually at 00 seconds), and thus have an inaccuracy of less than a minute. If you need exactly 60 seconds, use utimer instead, as these timers are checked each second.
_________________
NML_375, idling at #eggdrop@IrcNET

[ultralord]

i use utimer.. but sometimes runs proc early.. ;/

[nml375]

utimers have an inaccuracy of less than a second, compared to timers which have an inaccuracy of less than a minute. If an utimer triggers much more early than this, it would usually indicate that the local clock on the system was advanced while the timer was "waiting".
_________________
NML_375, idling at #eggdrop@IrcNET

[rosc2112]

You could always set a var with [unixtime] at the beginning when the utimer is set, then within the proc set a different var with [unixtime] again and then subtract var2 from var1 and "if" it's 60 seconds, execute the rest of the proc, if not, calculate how many seconds remain and set a new utimer to run the proc again (which will calculate the time diff each time, etc.)

[nml375]

That check would be pretty useless, as unixtime relies on the same timesource as HOOK_SECONDLY and timer-tracking. As such, the apparent time passed would always seem to be within one second of the desired time (or possibly longer, but never shorter).

The pretty much only reason why an utimer would start more than a second early, is as stated, that someone is playing around with the system-clock.
_________________
NML_375, idling at #eggdrop@IrcNET

[ultralord]

i have again that problem when i use eggdrop 1.6.9 version.. maybe the old that version have that problem? i want to run somethin on 5 minites and when i user timer 5 sometimes runs on ~3 minites etc.. and if i use utimer 300 (300 seconds) i have again the problem if the seconds is high.. the problem will be fixed if i use new version of eggdrop?


**i Use old version for something else because with new doesnt run if you know about timer tell me thanks

[arfer]

I made a small script as follows to test the accuracy of timers/utimers on my 1.6.19 bot :-

[ultralord]

thnx for that test script my results..

17:10:16] <@Ultralord> !time 1 minute
[17:10:17] <@botnick> Time Started (1 minute test) Sat Jan 10 17:09:25 2009
[17:10:52] <@botnick> Time Ended (1 minute test) Sat Jan 10 17:10:00 2009
[17:11:04] <@Ultralord> !time 1 minute
[17:11:05] <@botnick> Time Started (1 minute test) Sat Jan 10 17:10:13 2009
[17:11:51] <@botnick> Time Ended (1 minute test) Sat Jan 10 17:11:00 2009
[17:12:04] <@Ultralord> !time 1 minute
[17:12:06] <@botnick> Time Started (1 minute test) Sat Jan 10 17:11:14 2009
[17:12:51] <@botnick> Time Ended (1 minute test) Sat Jan 10 17:12:00 2009
[17:13:23] <@botnick> Time Started (5 minute test) Sat Jan 10 17:12:31 2009
[17:17:51] <@botnick> Time Ended (5 minute test) Sat Jan 10 17:17:00 2009
[17:19:19] <@botnick> Time Started (5 minute test) Sat Jan 10 17:18:14 2009
[17:23:51] <@botnick> Time Ended (5 minute test) Sat Jan 10 17:23:00 2009

some tests.. sometimes like 1st bind i have problem.. is it possible the bot have count problem if the bot have lag? but i dont see any problem with any of my scripts and the scripts doesnt lag because i have some spam message and is ok..

thnx

[arfer]

The results shown above using my script would indicate that timer events are working as expected on your bot. ie. triggering to the nearest minute

What I know as lag is generally a time delay in the IRC network connection. This would cause a delay to occur before the channel output is seen, but I would not expect it to affect timer/utimer triggering.

[ultralord]

so how i can fix that to have correct time ? is it possible to fix that problem if i use the latest version of eggdrop ?

[nml375]

As stated earlier, use the proper timer for the proper accuracy. timer gives you an accuracy to the minute, utimer gives you an accuracy to the second.

Also, you cannot script around lag, as that is not within the context of eggdrop scripting but network dependant.

The way I see it, there is nothing to fix (apart from using utimers when you need precision down to the second). Upgrading/downgrading your eggdrop will have no impact whatsoever on this issue.
_________________
NML_375, idling at #eggdrop@IrcNET

[ultralord]

ye i try the before script with 300 seconds and is ok same second.. i am going to user utimer 300 for timer 5 to see if it works better.

thnx