 |
Chessman Newbie
Joined: 11 Mar 2007 Posts: 4
|
Posted: Mon Mar 12, 2007 12:33 am
Help with #Alarm half second trigger |
I've been trying to use #alarm to come up with a way to spam kill "insertenemyhere" for use in PvP or PK. I can get it to once per second easily with #ALARM "killenemy" {*1} {kh} with kh being my alias. I would like to get the alarm to fire every half second as it says is possible in the CMUD help files, but it doesn't say how. I want to be able to do this because once a second isn't quite fast enough to be competitive with manual spamming, with half second it should automatically stack commands which would make it virtually indistinguishable from manual spamming. I have tried *0.5, *1/2 and several other ways for a half second, but none have worked. If anyone knows how to do this, please let me know.
|
|
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Mar 12, 2007 1:04 am |
You don't actually need the * - without it, the alarm will trigger that number of seconds. So you can do this:
#alarm 0.5 boo
or whatever. I've never really understood why the helpfiles tell you to include the star at the beginning - to me that would imply that the alarm would run on the clock, for every time the number of seconds ended in that number (because the star would match any tens digit). You'd end up having an alarm that went off every 10 seconds. |
|
|
|
 |
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Mon Mar 12, 2007 5:05 am |
Fang, that does not work. I've experienced his same quandary. This is what you get if you do what you suggested and type #alarm.
| Code: |
Alarms:
+ 0.5 -> boo [in -912234512 secs]
|
The documentation says.
| Zugg wrote: |
| The smallest period of time that can be matched by an alarm is half a second. |
This is incorrect or at least misleading. An Alarm can handle ANYTHING, well almost, LARGER than .5 this includes micro seconds greater than .5 So this works.
Edit, whoops. that should be.
Side note. If you use the + you can use .5, but if you use * it will not work. What Fang was talking about. Not using the * is interpreted the same as if you had put it there.
So for recurring alarms that you can turn on and off the above applies. |
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram
Last edited by Arminas on Mon Mar 12, 2007 10:31 pm; edited 1 time in total |
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Mar 12, 2007 8:36 am |
How bizarre. It works with +0.5, I assumed it would work without since every other number does.
|
|
|
|
 |
chris-74269 Magician
Joined: 23 Nov 2004 Posts: 364
|
Posted: Tue Mar 13, 2007 10:34 pm |
i use alarms with +.01 all the time.
|
|
|
|
 |
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Wed Mar 14, 2007 2:24 am |
This error is with the *. I really don't know what sort of limits apply to the +. Alarms where you do not put a + are automatically made into alarms with the * even if you do not explicitly use it.
|
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
 |
|
|
|