Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD General Discussion
TonDiening
GURU


Joined: 26 Jul 2001
Posts: 1958
Location: Canada

PostPosted: Mon Aug 11, 2008 6:53 pm   

[2.35] #ALARM firing first time wrong and subsequent times ok
 
Into command line:

#ALARM *3:00:00 {#ALARM}
#ALARM
*3:00:00 -> test [in 02:29:30]
#alarm *1:01:00 {#ALARM}
#ALARM
*1:01:00 -> test [in 28:41]
#alarm *60:00 {#ALARM}
#alarm
*60:00 -> test [in 27:16]
#alarm *10:00 {#ALARM}
#alarm
*10:00 -> test [in 6:56]

Once they fire, they reset to the proper time

ie when *10:00 fires all is now fine:
*10:00 -> #alarm (disabled)
#alarm
*10:00 -> #alarm [in 9:56]
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23377
Location: Colorado, USA

PostPosted: Tue Aug 12, 2008 4:38 pm   
 
No, this is actually correct. The syntax you are creating sets up an absolute alarm time, not a relative time. In other words,

#ALARM *1:00:00 {#ALARM}

means to fire the alarm at the next hour. So if the current time is 10:35, the alarm will show a time remaining of 25:00 (firing at 11:00:00). From the help file for #alarm:
Quote:
You can also use the special wildcard *value which will match when the time MOD the value is zero. E.g. *10 matches 10, 20, 30, etc.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD General Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net