Forums Bug Reports /timer

I get odd results too at random times. The command

//.timertrivia_0 1 1 echo -at ONE | .timertrivia_1_1 1 2 echo -at TWO | .timertrivia_1 1 3 echo -at THREE | .timertrivia_2 1 4 echo -at FOUR | .timertrivia_3 1 5 echo -at FIVE

sometimes echoes two words simultaneously, usually TWO with THREE, so it's usually like

ONE
<interval>
TWO
<no interval>
THREE
<interval>
FOUR
<interval>
FIVE

Then I added in $!ticks and things got even weirder:

//.timertrivia_0 1 1 echo -a $!ticks ONE | .timertrivia_1_1 1 2 echo -a $!ticks TWO | .timertrivia_1 1 3 echo -a $!ticks THREE | .timertrivia_2 1 4 echo -a $!ticks FOUR | .timertrivia_3 1 5 echo -a $!ticks FIVE

the results I got:

74713656 ONE
74714656 TWO
74715656 THREE
74716656 FOUR
74717656 FIVE

75724656 ONE
75725656 TWO
75725656 THREE
75726656 FOUR
75727656 FIVE

75868656 ONE
75869656 TWO
75870656 THREE
75871656 FOUR
75872656 FIVE

75910656 ONE
75911656 TWO
75912656 THREE
75912656 FOUR
75913656 FIVE

75953656 ONE
75954656 TWO
75955656 THREE
75956656 FOUR
75957656 FIVE

75975656 ONE
75976656 TWO
75977656 THREE
75978656 FOUR
75979656 FIVE

76113656 ONE
76114656 TWO
76115656 THREE
76116656 FOUR
76116656 FIVE

Notice that the ticks numbers always end in 656 (awfully close to 666, that might explain things!). This happens every time I test it.

CPU load and/or process priority don't seem to affect the bug. I changed mirc.exe's priority to Highest and I got the same results.