|
raks Beginner
Joined: 30 Jan 2002 Posts: 24 Location: USA
|
Posted: Mon Sep 16, 2002 10:50 pm
ARRR!!! help with alarms |
I have read the tatorials for alarms about 50 times and i can't figure out how to get them set the way i want....HELP, PLEASE!
i can't figure out how to set an...
1. an hourly alarm that will go off every hour or so ie every 1 hour it will go off
2. an minute alarm that will go of ever min or so ie one that will go off every 15 minutes.
3. an second alarm that will go off ever sec or so... ie every 35 sec. |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Tue Sep 17, 2002 12:27 am |
quote:
I have read the tatorials for alarms about 50 times and i can't figure out how to get them set the way i want....HELP, PLEASE!
i can't figure out how to set an...
1. an hourly alarm that will go off every hour or so ie every 1 hour it will go off
2. an minute alarm that will go of ever min or so ie one that will go off every 15 minutes.
3. an second alarm that will go off ever sec or so... ie every 35 sec.
#3 is easy enough, but you might need to do something special to get it working properly:
#alarm *@interval {code goes here}
as far as #1 and 2 go, do you want it to trigger on clock time or connect time?
#alarm -*:00:00 {this fires every hour based on the connection timer}
#alarm *:00:00 {this fires every hour based on system time and keeps going when you are offline}
li'l shmoe of Dragon's Gate MUD |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Sep 17, 2002 12:29 am |
For that, you specify the tiem you want the alarm to wait but using an * in front. This specifies that the alarm will fire every x seconds. So, for your three cases:
1. #ALARM {*3600} {do something}
2. #ALARM {*900} {do something}
3. #ALARM {*35} {do something}
Kjata |
|
|
|
raks Beginner
Joined: 30 Jan 2002 Posts: 24 Location: USA
|
Posted: Tue Sep 17, 2002 12:39 am |
What everthing has to be in seconds... blah go much to add up if i want an alarm to go off every 2 hour.....60(sec)*60(min)*2 blah.. my head hurts already... so for min 60(sec)*30(min).. for every 30 min blah... my head hurts again...
|
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Sep 17, 2002 12:58 am |
Click on Start|Programs|Accessories|Calculator...
Now it should be the computer's head that hurts, not yours.
Kjata |
|
|
|
raks Beginner
Joined: 30 Jan 2002 Posts: 24 Location: USA
|
Posted: Tue Sep 17, 2002 2:14 am |
you sure the that is right.... the *x x=number of seconds... just tryed to set a alarm to go off every 20 min which is 1200 seconds right?.... and it seems to go off every 12 seconds.
|
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Tue Sep 17, 2002 2:27 am |
I type in:
#ALARM {*1200} {#SH Testing}
and wait a few minutes and nothing appears on the screen (I'm not going to wait the full 20 minutes, but I'm sure it is not 12 seconds.) You may also check how much time before your alarms fire by entering the #ALARM command in the command line without any parametes.
Kjata |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Tue Sep 17, 2002 2:29 am |
The *xx:xx:xx format works. just put in the time you want.
This format fires based on the Windows timer, and do care whether you are connected or not.
Some examples:
#ALARM {*1:00:00} {#ECHO 1 hour has passed.}
#ALARM {*2:00:00} {#ECHO 2 hours have passed.}
#ALARM {*15:00} {#ECHO Coffee is done get a cup!}
#ALARM {*00:15:01} {#ECHO Haha I drak all the coffee already.}
#ALARM {*35} {#ECHO Are you tired of my silly alarm examples already?!}
#ALARM {*.5} {#ECHO I only work in beta versions. Beta versions are full of bugs guaranteed to warp your mind, rot your soul, and keep your character from gaining the next level.} |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Wed Sep 18, 2002 3:59 am |
You can also do these using just numbers, provided you choose numbers that are factors of 60 for the seconds and minutes. A 35 second interval would be pretty difficult to setup without using the *nn syntax.
1. an hourly alarm that will go off every hour or so ie every 1 hour it will go off
#ALA {00:00} {This will go off every hour, on the hour}
#ALA {37:00} {This will go off every hour, at 37 minutes past the hour}
#ALA {-43:00} {This will go off once an hour for as long as you're connected, starting at 43 minutes after the connection}
2. a minute alarm that will go of ever min or so ie one that will go off every 15 minutes.
{#ALA {7} {This will go off every minute, at 7 seconds past the minute}
#ALA {00|15|30|45}:00 {This will go off every 15 minutes}
3. a second alarm that will go off ever sec or so... ie every 35 sec.
#ALA {35} {This will go off once a minute, at 35 seconds past the minute}
#ALA {05|35} {This will go off twice a minute, at 5 and 35 seconds past}
LightBulb
Senior Member |
|
|
|
Raksasas Novice
Joined: 09 Aug 2001 Posts: 39 Location: USA
|
Posted: Thu Sep 19, 2002 6:10 am |
okay i still am some what lost...
maybe thise will help.. i am used to useing the #wait (#wa) command.. so show me how to replace this witch an alarm
#wa 5000
V6.16 |
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Thu Sep 19, 2002 1:17 pm |
do stuff
do more stuff
#WAIT 5000
do some other stuff
finish doing stuff
gets converted to:
do stuff
do more stuff
#ALARM {+5} {do some other stuff;finish doing stuff}
Kjata |
|
|
|
|
|