Zugg Software :: View topic

Novice Joined: 26 Dec 2002 Posts: 33 Location: USA

I have two alarms set, one is *:00:00, the other is 00:01:00, both firing an alias that reports experience gained that hour (or day), cash earned, etc. In 6.16, they worked fine, but since upgrading to 6.4, they will occasionally fire twice, usually if I'm active in the MUD.

As the clock rolls over:
2517hp/2728hp/92% 1868m/2325m 2520mv/2520mv Enemy: 100% -156align 3391exp Dbl: 10 0qtime
gt @RLast hour@C: @G14321@WEXP @G126040@W$$ @G403@WEXP@C/@Wmob@w
gt @RLast hour@C: @G0@WEXP @G0@W$$ @G0@WEXP@C/@Wmob@w

You parry a green dragon's attack.

(Group) Bremen: Last hour: 14321EXP 126040$$ 403EXP/mob
2305hp/2728hp/84% 1940m/2325m 2520mv/2520mv Enemy: 93% -156align 3391exp Dbl: 9 0qtime
(Group) Bremen: Last hour: 0EXP 0$$ 0EXP/mob

(The alias resets the variables involved, so the second one is at least accurate for the new hour, heh).

I don't think any settings are doubled up since the upgrade, it's just a plain alarm trigger, and it occasionally fires correctly (just once), so the only thing I could think of was the state going from 0 back to 0 quickly enough or something else making it get checked twice in the same second.

Any light anyone can shed, I'd appreciate it. I can easily create a workaround (variables to check, etc), but I'd rather it just work correctly.
--Bremen, WinME (hooray), zMUD 6.40.

Novice Joined: 26 Dec 2002 Posts: 33 Location: USA

I added an #echo %time to the trigger, and the results were:

Worked fine (fired once) at 9pm, 10pm, then:

gt @RLast hour@C: @G7350@WEXP @G71996@W$$ @G350@WEXP@C/@Wmob@w
Wednesday December 25, 2002 10:59:59 pm
(Group) Bremen: Last hour: 7350EXP 71996$$ 350EXP/mob

1479hp/2841hp/52% 2370m/2407m 2609mv/2609mv Enemy: 30% 151align 1528exp 23qtime
gt @RLast hour@C: @G0@WEXP @G0@W$$ @G0@WEXP@C/@Wmob@w
Wednesday December 25, 2002 11:00:00 pm
(Group) Bremen: Last hour: 0EXP 0$$ 0EXP/mob

gt @RLast hour@C: @G7475@WEXP @G58615@W$$ @G287@WEXP@C/@Wmob@w
Wednesday December 25, 2002 11:59:58 pm
...
gt @RLast hour@C: @G0@WEXP @G0@W$$ @G0@WEXP@C/@Wmob@w
Thursday December 26, 2002 12:00:00 am

Well, I'm confused, guess it is being checked twice..sometimes.

--Bremen, WinME (Hooray!), zMUD 6.40.

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Why do you have two alarms doing the same thing?

Kjata

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

This one: *:00:00 should go off at the beginning of every hour, including midnight.
This one: 00:01:00 should go off once per day, at 1 minute after midnight.

According to your post, they go off when they're supposed to, once per hour and twice at midnight.

LightBulb
Senior Member

Novice Joined: 26 Dec 2002 Posts: 33 Location: USA

Lightbulb's correct in why I have two, but they are not firing correctly. Notice the hourly one firing at both 10:59:59 and 11:00:00. The first trigger sometimes fires once per hour, and sometimes fires twice per hour. The second trigger tends to fire twice in a row at 12:01am, too.

quote:

This one: *:00:00 should go off at the beginning of every hour, including midnight.
This one: 00:01:00 should go off once per day, at 1 minute after midnight.

According to your post, they go off when they're supposed to, once per hour and twice at midnight.

--Bremen, WinME (Hooray!), zMUD 6.40.

Novice Joined: 26 Dec 2002 Posts: 33 Location: USA

LightBulb, could you (or another guru) take another look at this? As I showed above, it fired more than once at 11pm, so it's not always firing correctly, just sometimes. Sorry for the repost, just seems like everyone's moved on since you declared it already working.

--Bremen, WinME (Hooray!), zMUD 6.40.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Well, I opened a blank window and wrote three alarms:
#ALARM *:00:00 {This is the first alarm;#ECHO %time}
#ALARM 19:01:00 {This is the second alarm;#ECHO %time}
#ALARM 19:02 {This is the third alarm;#ECHO %time}
Then went and watched TV for awhile. Here's the results:
This is the first alarm
Saturday December 28, 2002 7:00:02 pm
This is the second alarm
Saturday December 28, 2002 7:01:00 pm
This is the third alarm
Saturday December 28, 2002 7:02:00 pm
This is the first alarm
Saturday December 28, 2002 8:00:00 pm
This is the first alarm
Saturday December 28, 2002 8:59:59 pm
This is the first alarm
Saturday December 28, 2002 9:00:00 pm
This is the first alarm
Saturday December 28, 2002 10:00:00 pm
This is the first alarm
Saturday December 28, 2002 10:59:59 pm
This is the first alarm
Saturday December 28, 2002 11:00:00 pm

Duplication occurred at 8:59:59/9:00:00 and again at 10:59:59/11:00:00. Send Zugg a bugreport. So far, duplication has occurred if and only if the alarm fired early.

LightBulb
Senior Member

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

As a workaround, you could try having the alarm disable itself for a brief period.
#ALA *:00:00 {#IF (@alarm1 = 1) {#VAR alarm1 0;YourAlias;#ECHO %time;#ALA +30 {#VAR alarm1 1}}}

LightBulb
Senior Member