 |
misterbalrog
Apprentice
Joined: 26 Oct 2004
Posts: 108
|
 Posted: Sun Feb 27, 2005 11:01 pm
Buggy #suspend...
|
| #alarm gives/ wrote: |
Alarms:
+ CleanTwist: -24:00 -> #10 {at %random(1,100).twisted get twist;eat twist} [in 22:21] |
It worked once before to do ...
#suspend {CleanTwist}
... in order to stop it. But now it has stopped working to stop the alarm.
I've tried these:
#suspend CleanTwist
#suspend "CleanTwist"
#suspend {CleanTwist}
And the wizard creates the {CleanTwist} version.
Anyone got a solution? |
|
|
|
|
nexela
Wizard
Joined: 15 Jan 2002
Posts: 1644
Location: USA
|
Posted: Mon Feb 28, 2005 3:03 am
|
#SUSPEND works you just need to give your alarms an ID (its on the options tab for the alarm or use command line syntax)
#ALARM "ID_GOES_HERE" {-24:00} {do whatever}
#SUSPEND "ID_GOES_HERE"
Alternativly you can use the pattern
#SUSPEND -24:00 |
|
|
|
|
misterbalrog
Apprentice
Joined: 26 Oct 2004
Posts: 108
|
Posted: Mon Feb 28, 2005 8:21 am
|
The alarm shown above was not something I did during this session but was reinitiated when I restarted zMUD. Apparently it lost it's ID since it was unable to use the ID again as I had used it before.
The way #alarm displays it is that it didn't show ID at all, regardless if it had one or not.
| Quote: |
| + -24:00 -> #10 {at %random(1,100).twisted get twist;eat twist} [in 23:58] |
So the "CleanTwist" which was on the one before was in fact the Class name. I had totally forgotten that these were triggers so I just went into the trigger editor and gave back the ID to the alarm. However I use #T- instead to turn it off now since using #suspend seems very buggy.
Oh and coincidentally, that #suspend -24:00 didn't work either. Not with brackets or quotes. So the alarm was quite literally out of reach for the #suspend command.
Problem solved by using the trigger editor. |
|
|
|
|
|
|
|
