Zugg Software :: View topic

Adept Joined: 20 Jul 2004 Posts: 268

Not sure why this is happening, but sometimes my hourly exp alarm goes off twice in a row. I did a search in the settings for exphour (the alias for it) and the two commands are the only ones that show and are the only ones that SHOULD show.

#ALIAS exphour {
gt ~@GLast hour~@R: ~@w@expperhour~@RXP ~@w@cashperhour~@R$~@w
expperhour="0"
cashperhour="0"
} "Char Status"
#ALARM "Alarm0" {*:00:00} {exphour} "Char Status"

Yet, i get 2 outputs. One with the info and the 2nd zero'd out.

gt @GLast hour@R: @w107@RXP @w14231@R$@w
gt @GLast hour@R: @w0@RXP @w0@R$@w

To check i've taken to typing #alarm at least once every hour to see if there is something else going in there, but the only output is the correct one:
+ Char Status: *:00:00 -> exphour [in 50:54]

But it randomly happens. One day at 10am, another at 11am then again sometime during the day...nothing that I have been able to pin down as all the time on this specific day of the week...

Any idea about this? I can live with it if there's no other choice, but damn it's annoying :-)
Used Pretty Print
Syntax Colourizer

Apprentice Joined: 10 Feb 2005 Posts: 158

Hmm, looks simple enough. I can see where that would be annoying. Since I cant see anything wrong script wise the only thing I can think to do is get rid of the obviously wrong output until a possible cause is found... not ideal I know.

#TRIGGER {^gt ~@GLast hour~@R: ~@w0@RXP ~@w0@R~$~@w$} {#gag}

Adept Joined: 20 Jul 2004 Posts: 268

Just a small bump in hopes that maybe someone knows what the heck is going on?...

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

I ran this and had no problem, time and time again it came back with just the one. Look to make sure you did not make a duplicate of it any where or inherited it from something else you did.

also try it in another character window to see if your still having the same problem.

If all fails to remedy the problem you could just always add #gag to your alias and that would knock out the last part.

Adept Joined: 20 Jul 2004 Posts: 268

typing #alarm would give me each instance of it.
There is no duplicate of it.
And it only happens occasionally.
Not every time at 10am, not every time at 11am etc.
Sometimes it even goes off at *:59 rather than *:00
But that *:59 is like a second to 5 seconds before the *:00.
The #gag is the way to go, but it just points to a weird flaw i think in #alarm.
Aw well :(

Adept Joined: 14 Jun 2003 Posts: 222 Location: Chile

I dont think this will work
but ever tryed it like

#ALARM "Alarm0" {*3600} {exphour} "Char Status"

Adept Joined: 20 Jul 2004 Posts: 268

i'll give it a shot DeReP.
Can't be any worse than it is now. Tho I prolly won't see any results for a while. Like I said it's rare that it happens, but annoying :-)
BTW, dunno if i said it before, and haven't had enuf coffee yet to scroll up and look, but out of the 5 alarms that I have for various ongoing things, THIS one is the only one that does it.

Adept Joined: 20 Jul 2004 Posts: 268

*grumble*
gt @GLast hour@R: @w992@RXP @w16783@R$$@w
gt @GLast hour@R: @w0@RXP @w0@R$$@w

so much for *3600 :-)

Posted: Thu Jul 07, 2005 8:08 pm

well, thought that Maelstrom might hit the nail in the head for this one with his naming alarm idea.

#ALIAS exphour {
gt ~@GLast hour~@R: ~@w@expperhour~@RXP ~@w@cashperhour~@R$$~@w
#T- exphour
expperhour="0"
cashperhour="0"
} "Char Status"

#ALARM "Alarm0" {*:00:00} {
#T+ exphour
#ALARM expshower {+.5} {exphour}
} "Char Status"

(Group) Vitae: 'Last hour: 4XP 816$'
(Group) Vitae: 'Last hour: 0XP 0$'

*mutter*
The doubling of this is never trackable for me. won't happen at same times consistently, so i can't say "Well, at 11AM EST it does it."
It does is whenever the heck it wants.

Beginner Joined: 27 Feb 2005 Posts: 24

The same thing happens to me, and to my spouse with this trigger.
It only triggers occasionally with us as well.
Sofar i've not been able to track it down either.

Posted: Wed Jul 20, 2005 1:12 pm

Changed this:

Posted: Wed Jul 20, 2005 2:07 pm

Changed this:

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

I posted this back on Christmas '02.
http://forums.zuggsoft.com/phpbb/viewtopic.php?t=9662

I communicated with Zugg directly about it and he wasn't able to reproduce it, but I hope he doesn't think I'm insane any more now that others are running into it.

I think it just has to do with how quickly alarms are checked, sometimes it happens to check twice during the second of the new hour so it fires twice. You figured out the only real way to prevent it.